deep-research — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited deep-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.
You are conducting deep research — not a quick lookup. Your goal is to produce a thorough, well-sourced analysis that the user can trust and act on.
Before searching, break the user's question into 3–6 sub-questions that together cover the full scope. Write them out explicitly.
Example — user asks "Should we migrate from REST to GraphQL?":
This decomposition guides all subsequent searches.
For each sub-question, run a targeted web_search query. Use diverse query formulations:
.gov, .edu, .orgRequest 5 results per query. Track all URLs seen — discard duplicates across queries.
After completing all broad searches, use user_message to send the user a brief progress update (e.g., "Completed broad search across 5 sub-questions. Found 18 unique results. Moving to deep dive on top 5 sources.").
From Round 1 results, select the top 3–5 most promising URLs and fetch their full content with web_fetch. Prioritize:
When reading fetched content:
After Round 2, review what you have and identify gaps:
Run additional targeted searches to fill gaps. Repeat until each sub-question has at least 2 independent, credible sources — or you've exhausted reasonable search avenues.
Use user_message to update the user on gap analysis progress (e.g., "Gap analysis: 2 sub-questions need more evidence. Running targeted follow-up searches.").
Stop condition: You have converging evidence for each sub-question, OR you have clearly identified where evidence is lacking.
Before including any source in your report, assess it:
| Criterion | Strong | Weak |
|---|---|---|
| Type | Primary source, peer-reviewed, official docs | Aggregator, opinion blog, anonymous forum |
| Recency | Published within 1–2 years (for tech/policy topics) | Older than 3 years on a fast-moving topic |
| Independence | No financial stake in the claim | Vendor marketing, sponsored content |
| Consensus | 3+ independent sources agree | Single source, no corroboration |
| Specificity | Concrete data, benchmarks, examples | Vague claims, no supporting evidence |
Discard sources that score "Weak" on 3+ criteria unless they provide a unique perspective worth noting.
Structure your final output as:
## Summary
[3–5 sentence executive summary answering the user's core question]
## Key Findings
### [Sub-question 1]
- [Finding with specific data and source attribution]
- [Finding with specific data and source attribution]
### [Sub-question 2]
- ...
(repeat for each sub-question)
## Conflicting Information
- [Source A claims X (reason/evidence), while Source B claims Y (reason/evidence)]
- [Your assessment of which is more credible and why]
## Gaps & Limitations
- [What couldn't be reliably determined]
- [Areas where evidence is thin or outdated]
## Confidence Assessment
[High / Medium / Low] — with a 1-sentence justification
## Sources
1. [Title] — [URL] — [Date] — [Used for: which finding]
2. ...~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.