CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deep-research

Run a disciplined, multi-source research investigation for a high-stakes question or decision — fan-out web search across many channels, parallel sub-agents, source triangulation (each claim backed by ≥3 independent sources), an adversarial review pass, and every source saved to its own file with verbatim quotes for reuse. Use when a low-quality answer is expensive: strategy work, comparing N products/methods/markets, validating a hypothesis with external data, or mapping how a field works. NOT for quick fact-checks (answer directly), structured 12-dimension competitor scoring (use competitive-teardown), or fast topic overviews where the decision risk is low (use the research router instead).

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, disciplined methodology document with a clearly sequenced pipeline, explicit validation and feedback loops, and concrete artifacts and thresholds. Its main weakness is navigation: the bundled catalog reference is never surfaced from the body, and key operational details (self-critique questions, sub-agent prompts, channel list) are deferred without in-skill pointers.

Suggestions

Explicitly link references/full-catalog.md from the body (e.g., in Phase 3.5 Capability discovery: 'see [full-catalog.md](references/full-catalog.md) for the 29 channels and 39 validated APIs') so the sourcing surface is discoverable from SKILL.md alone.

Specify the 4 self-critique questions and a compact template for sources/NN_slug.md (metadata fields, quote format, Credibility/Recency/Bias scale) so Phases 4–6 are executable without inventing details.

Fold the 'How it differs from a quick research router' section into the Cross-References entry to remove the triple-stated router distinction and reclaim tokens.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with no concept-explaining padding, but the router distinction is stated three times (intro 'it is not a fast overview', the dedicated 'How it differs from a quick research router' section, and the Cross-References entry) — trimmable redundancy that keeps it just below the lean/every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete file formats (plan.md, sources/NN_slug.md, refresh_targets.md, sources.csv), explicit thresholds (≥3 independent sources, 2–4 falsifiable hypotheses, 4 self-critique questions, Credibility/Recency/Bias scoring), and a per-phase pipeline give mostly executable guidance; the gaps — the 4 self-critique questions themselves, sub-agent prompts, and a source-file template — are more than trivial but not disqualifying, fitting 'mostly executable guidance with minor gaps' over the incomplete-guidance anchor.

4 / 5

Workflow Clarity

The 9 phases are clearly sequenced in an ordered table with depth gating; validation is explicit (Phase 6.5 'lightweight citation check before closing', Phase 5 'insufficient evidence' flagging, hypothesis confirm/refute); Phase 4's 're-evaluate between rounds' is a feedback loop with error handling ('An empty fetch produces an empty claim, never a fabricated citation'); and the Anti-Patterns section serves as a failure-mode checklist — all top-anchor elements are present.

5 / 5

Progressive Disclosure

The bundle contains references/full-catalog.md holding the entire sourcing surface (29 channels, 39 APIs, 103 blocks), yet the body never mentions or links it — 'references present but not clearly signaled' — and the catalog file itself points to an external GitHub repo, adding a second hop to the actual content. The body's own structure is well organized, so this sits at the some-structure anchor rather than lower.

3 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capability list, explicit use-when triggers with concrete scenarios, and explicit negative boundaries that route to sibling skills. The only weakness is a handful of missing natural synonyms a user might say when reaching for deep research.

DimensionReasoningScore

Specificity

The description lists five concrete, specific actions — 'fan-out web search across many channels, parallel sub-agents, source triangulation (each claim backed by ≥3 independent sources), an adversarial review pass, and every source saved to its own file with verbatim quotes' — with comprehensive coverage and no gaps, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

It explicitly answers what ('Run a disciplined, multi-source research investigation...') and when ('Use when a low-quality answer is expensive: strategy work, comparing N products/methods/markets, validating a hypothesis with external data, or mapping how a field works') with concrete trigger phrases, plus explicit NOT-for boundaries — clearly the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered ('strategy work', 'comparing N products/methods/markets', 'validating a hypothesis', 'mapping how a field works', 'quick fact-checks', 'topic overviews'), but a few natural synonyms users would say ('due diligence', 'deep dive', 'in-depth investigation', 'research report') are missing, fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Explicit negative boundary clauses — 'NOT for quick fact-checks (answer directly), structured 12-dimension competitor scoring (use competitive-teardown), or fast topic overviews... (use the research router instead)' — actively route away from sibling skills, giving a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

research/deep-research/skills/deep-research/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.