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).

68

Quality

86%

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

The canonical home for this skill is deep-research in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

73%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-engineered orchestration skill: a clearly sequenced 9-phase pipeline with explicit verification checkpoints, feedback loops, concrete file artifacts and thresholds, and a strong anti-patterns checklist. Its main weaknesses are redundant restatement of the router comparison and core mechanisms (each appears 2–3 times), and key executable details (self-critique questions, scoring scales) that are referenced but never specified.

Suggestions

Consolidate the router-vs-deep-research distinction into one place — it is currently stated in the intro paragraph, the two-paragraph 'How it differs from a quick research router' section, and implicitly in 'When to use' — and let core mechanisms live in either the phase table or 'Core mechanisms' but not both plus 'Anti-Patterns'.

Specify the '4 self-critique questions' and the Credibility/Recency/Bias scoring scale (e.g., 1–5 anchors or criteria), or move them into a one-level-deep reference file so Phase 6 and Phase 5 are executable as written.

Define the report genres' building blocks (qa / explainer / decision / landscape / validation / custom) at least briefly, since Phase 2 and Phase 6 both depend on them but only the genre names are given.

DimensionReasoningScore

Conciseness

Everything is task-specific with no generic concept padding, but there is genuine repetition that could be tightened: the 'not a fast overview / router tradeoff' point appears in the intro, again across the two-paragraph 'How it differs from a quick research router' section, and the core mechanisms (triangulation, parallel sub-agents, refresh protocol) are each restated in the phase table, 'Core mechanisms', and 'Anti-Patterns'.

3 / 5

Actionability

Concrete artifacts and thresholds throughout — plan.md, sources/NN_slug.md, refresh_targets.md, '≥3 independent, differently-typed sources per thesis', '2–4 falsifiable hypotheses', an exact output tree, and Credibility/Recency/Bias scoring. Not a 5 because key executable details are unspecified: the '4 self-critique questions' are never listed, no scoring scale is defined, and genre building blocks are only named.

4 / 5

Workflow Clarity

The 9-phase table gives a clear sequence with explicit validation checkpoints — Phase 4 're-evaluate between rounds', Phase 5 flagging claims as 'insufficient evidence', Phase 6.5 'Verify — lightweight citation check', Phases 5–6 confirming or refuting each hypothesis — and the anti-patterns act as an error-recovery checklist ('An empty fetch produces an empty claim, never a fabricated citation').

5 / 5

Progressive Disclosure

No bundle files exist and the ~85-line body is a well-organized self-contained overview with clearly signaled cross-references to sibling skills; however, detail such as the source-scoring rubric, the 4 self-critique questions, and genre block definitions is omitted rather than split into a one-level-deep reference file, leaving minor organization gaps.

4 / 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: it names concrete mechanics (fan-out search, parallel sub-agents, ≥3-source triangulation, adversarial pass, per-source files), gives explicit 'Use when' triggers tied to decision risk, and cleanly routes away rival skills. The only gap is a few missing natural synonyms for the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete 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 of the workflow, in third person.

5 / 5

Completeness

Explicitly answers what ('Run a disciplined, multi-source research investigation... fan-out web search... adversarial review pass... every source saved to its own file') 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 NOT-for boundaries.

5 / 5

Trigger Term Quality

Natural phrases like 'strategy work', 'comparing N products/methods/markets', 'validating a hypothesis', 'mapping how a field works', and 'quick fact-checks' match what users would actually say, but common synonyms such as 'deep dive', 'due diligence', or 'investigate' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Explicit disambiguation — '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)' — establishes 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

.gemini/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.