CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deep-research

Creates reusable, source-traced research reports and coordinates provider/mode lanes with original exports. Use for 深度研究, 调研报告, literature reviews, market or company research, and ChatGPT/Kimi/UniFuncs research routes. Technology choice uses tech-selection; competitor code uses competitors-analysis.

Quality

76%

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 ./deep-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 rigorously structured research pipeline with concrete scripts, explicit validation phases, and a well-signaled one-level-deep reference bundle. Its main problems are redundancy — the enterprise dimensions and E3-E7 workflow each appear multiple times — and long inlined contract paragraphs that duplicate reference files and inflate the always-loaded body.

Suggestions

State the six enterprise dimensions once (keep the E1-E7 checklist) and have 'Enterprise Research Integration', 'Six-Dimension Collection', and the duplicate 'E3-E7' section point to enterprise_research_methodology.md instead of re-listing them.

Compress the 'Run and asset contract' and P1 continuation paragraphs into a short mandate plus pointers to research-asset-contract.md and provider-run-contract.md, which already contain the detailed rules.

Use the full references/ path consistently (e.g. replace bare 'enterprise_quality_checklist.md' citations) so every reference resolves unambiguously.

DimensionReasoningScore

Conciseness

The six enterprise dimensions are listed three times ("Enterprise Workflow Overview" D1-D6, "Enterprise Research Integration" Tasks A-F, and "Six-Dimension Collection"), E3-E5 are described twice in conflicting sections ("E3: Select Analysis Frameworks Only When Useful" vs. the later "E3-E7" block), and the dense "Run and asset contract" paragraphs restate rules that live in research-asset-contract.md and provider-run-contract.md. This is noticeably verbose with several duplicated/padded sections, though it avoids explaining concepts Claude already knows (so not 1).

2 / 5

Actionability

Concrete commands appear throughout: "run `provider_runs.py plan`", "run `provider_runs.py validate`, `research_assets.py check`, and register the study", exact status formats ("[P0 complete] Subagent: {yes/no}. Mode: {standard/lightweight}. AS_OF: {YYYY-MM-DD}."), and a full registry output template. Not 5 because script invocations lack complete argument examples and some guidance stays abstract ("Assign one owner per control surface and serialize that owner's UI actions"); not 3 because the guidance is mostly concrete and directly executable.

4 / 5

Workflow Clarity

The P0-P7 pipeline is clearly sequenced with per-phase status reports, an explicit mandatory validation phase ("P6: Counter-Review (Mandatory)" with the five opposite-view checks), L1/L2/L3 quality gates, and a final verification checklist in P7. Not 5 because the enterprise path is presented twice with overlapping and differently-framed E3-E7 sections, which muddies the sequence a reader should follow; not 3 because validation checkpoints are explicit and plentiful, not merely implicit.

4 / 5

Progressive Disclosure

Reference tables with "When to Load" columns clearly signal all 18 reference files and 3 scripts (each verified to exist in the bundle), and references are one level deep. Not 5 because the body inlines substantial contract detail that duplicates the references (the asset/provider-run paragraphs) and two citations use a bare filename without the references/ path ("see enterprise_quality_checklist.md"); not 3 because most content is appropriately placed with explicit load triggers.

4 / 5

Total

14

/

20

Passed

Description

82%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 with an explicit 'Use for' trigger list, bilingual keywords, and active disambiguation against neighboring skills. The main weakness is specificity: the capability statement leans on internal jargon ("provider/mode lanes with original exports") instead of enumerating concrete actions.

Suggestions

Replace or unpack the jargon phrase "coordinates provider/mode lanes with original exports" with 1-2 concrete actions a user would recognize, e.g. "orchestrates parallel ChatGPT/Kimi research runs and verifies every claim against original sources".

Add the natural English trigger phrase "deep research" alongside 深度研究 to catch users who type the English term.

DimensionReasoningScore

Specificity

"Creates reusable, source-traced research reports and coordinates provider/mode lanes with original exports" names the domain and two actions, but "coordinates provider/mode lanes with original exports" is internal jargon rather than a concrete user-facing capability, and no further specific actions are enumerated. It is above level 2 (it does more than name the domain) but below level 4, which expects several specific concrete actions listed.

3 / 5

Completeness

The description explicitly answers both: what — "Creates reusable, source-traced research reports and coordinates provider/mode lanes"; when — "Use for 深度研究, 调研报告, literature reviews, market or company research..." with concrete trigger phrases. It matches the level-5 anchor exactly; level 4 would require the 'when' to be less explicit than the direct 'Use for' clause with enumerated triggers.

5 / 5

Trigger Term Quality

"深度研究, 调研报告, literature reviews, market or company research, and ChatGPT/Kimi/UniFuncs research routes" gives good natural keyword coverage including Chinese synonyms and named provider routes. Not 5 because common English variations such as "deep research" or "research report" itself are missing; not 3 because coverage clearly exceeds "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

"Technology choice uses tech-selection; competitor code uses competitors-analysis" actively routes adjacent use cases to other skills, and the bilingual provider-specific triggers define a clear niche. Minimal conflict risk; not 4 because the description does more than merely avoid overlap — it explicitly disambiguates boundary cases.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (602 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

daymade/claude-code-skills

Path

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.