CtrlK
BlogDocsLog inGet started
Tessl Logo

deep-research

Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.

59

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/public/deep-research/SKILL.md
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.

The content delivers a clearly sequenced, validated research workflow with genuinely actionable query patterns and temporal guidance. Its main weaknesses are redundancy across the four sections that restate the sufficiency criteria and the absence of any progressive-disclosure offloading in a fairly long single file.

Suggestions

Merge "Quality Bar", "Common Mistakes to Avoid", and "Output" into the Phase 4 synthesis checklist — they restate the same sufficiency criteria three times and could be cut to one section.

Move the temporal-precision table and query-pattern catalogs into a reference file (e.g. references/query-patterns.md) and keep SKILL.md as a lean overview of the four phases, bringing the body closer to a progressive-disclosure ideal.

DimensionReasoningScore

Conciseness

The body is mostly efficient methodology guidance, but the same completeness criteria are restated across "Phase 4: Synthesis Check", "Quality Bar", "Common Mistakes to Avoid", and "Output", and emphasis lines like "A single search query is NEVER enough" and "Never generate content based solely on general knowledge" repeat the core principle already stated. This matches anchor 3 ("mostly efficient but could be tightened"), not 4, since whole sections could be merged.

3 / 5

Actionability

Concrete, immediately usable guidance throughout: example search sets for "AI in healthcare", ❌/✅ query patterns, a table of information types with example searches, and a temporal-precision table mapping user intent to query format. Not 5 because some guidance remains advisory ("Follow References", "Identify gaps") without worked examples, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 4-phase sequence (Broad Exploration → Deep Dive → Diversity & Validation → Synthesis Check) culminating in an explicit validation checklist with a feedback loop: "If any answer is NO, continue researching before generating content." The "Iterative Refinement" section adds the review → gap-identify → retry loop, matching anchor 5 exactly.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers, a navigable flow, and no nested references (no bundle files exist). Not 5 because at ~190 lines all content is inline — the temporal-awareness table and query-pattern catalogs are natural candidates for a reference file that would keep SKILL.md a leaner overview.

4 / 5

Total

16

/

20

Passed

Description

62%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.

The description has strong, explicit trigger guidance with natural user phrasing, and both what and when are present. Its weaknesses are an abstract "what" and an unbounded scope ("ANY question requiring web research") that creates high conflict risk with other lookup-style skills.

Suggestions

Replace the abstract capability statement with 2-3 concrete actions, e.g. "Fans out parallel web searches across a topic's dimensions, fetches full sources, and cross-checks claims before synthesizing an answer."

Narrow the unbounded "ANY question requiring web research" scope to cases where a single search is insufficient (e.g. "Use when a question needs multi-angle, current information beyond a single search"), reducing conflict with simple lookup skills.

Add missing natural trigger synonyms such as "investigate", "look up", or "find out about" to round out keyword coverage.

DimensionReasoningScore

Specificity

"Provides systematic multi-angle research methodology instead of single superficial searches" names the domain (web research) and one capability, but the action described is abstract — no concrete actions like fan-out searches, source fetching, or claim verification are listed. It sits between anchor 2 (generic action) and anchor 4 (several specific actions), so 3 is the best fit.

3 / 5

Completeness

Explicitly answers "when" with concrete trigger phrases ("Trigger on queries like...", "Use this proactively when the user's question needs online information") and states a "what". Not 5 because the "what" ("systematic multi-angle research methodology") is abstract rather than concrete capabilities, matching anchor 4's "when could be more explicit or what could be more concrete" profile.

4 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "what is X", "explain X", "compare X and Y", "research X" — plus "web research" and "content generation tasks". Not 5 because common variations like "look up", "investigate", "find out about", or "news" are missing.

4 / 5

Distinctiveness Conflict Risk

The claim "Use this skill instead of WebSearch for ANY question requiring web research" is very broad and would capture nearly any question involving online information, creating high overlap risk with any other research, news, or fact-checking skill. It matches anchor 2 ("Very broad; high overlap risk with many similar skills") rather than 3, since the scope is explicitly unlimited ("ANY question").

2 / 5

Total

13

/

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
bytedance/deer-flow
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.