conducting-research — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited conducting-research (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Guide systematic research: frame the question, find and judge sources, gather and synthesise, stop at the right point, present findings with confidence levels. This is process guidance, not domain expertise — findings are only as good as the sources available.
Skip when a single lookup or a straightforward answer from existing knowledge suffices.
Before searching, establish (ask the user if unclear):
Aim for at least 3 high-quality sources before concluding anything.
Source hierarchy — start at the top, expand downward as needed:
Judge each source on: authority (who wrote it; official or third-party), recency (still current? prioritise recent sources in fast-moving fields), accuracy (cites reliable sources; key claims verifiable elsewhere), bias (conflicts of interest; promotion disguised as neutral content), relevance (addresses the question in a context like yours).
Deprioritise sources with: no author attribution, promotional language, outdated information, no citations, claims conflicting with multiple reliable sources, or strong opinion without evidence.
By research type: technology evaluation — official docs first, then neutral benchmarks and production experience reports; concept understanding — authoritative introductions, cross-referencing multiple explanations; current events — sources from the last 6–12 months, verified across several; troubleshooting — official docs, then GitHub issues and dated Stack Overflow answers.
Default to hybrid exploration: breadth-first to map the territory and identify 2–4 key areas, then depth-first on each, returning to breadth if gaps appear. Keep structured notes as you go: findings with their sources, open questions, and contradictions between sources.
Build a mental model: core concepts, how they connect, where sources agree and where they debate. Before concluding:
Stop when the original question has a clear answer, key claims are verified by multiple reliable sources, understanding suffices for the stated purpose, and further searching shows diminishing returns.
Keep going when core concepts remain confusing, contradictions are unresolved, key claims rest on low-quality sources, or critical assumptions are untested.
If time runs out first: state what wasn't covered, separate what you know / think / don't know, and flag where the gaps carry risk.
Adapt format to purpose — a quick investigation may need only a summary. For substantial research include: executive summary (core answer plus key takeaways), scope and constraints, findings organised by theme or sub-question with evidence, source quality and confidence levels, implications or recommendation, open questions. Cite sources for quotes and key claims: [claim] (Source: name, URL).
Watch for these while working:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.