Generate format-controlled research reports with evidence tracking, citations, and iterative review. This skill should be used when users request a research report, literature review, market or industry analysis, competitive landscape, policy or technical brief, or require a strict report template and section formatting that a single deepresearch pass cannot reliably enforce.
Install with Tessl CLI
npx tessl i github:daymade/claude-code-skills --skill deep-researchOverall
score
98%
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities (format-controlled reports, evidence tracking, citations, iterative review), provides excellent trigger term coverage across multiple document types, and explicitly states when to use it versus alternatives. The description effectively differentiates itself from simpler research tools by emphasizing strict formatting requirements.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'format-controlled research reports', 'evidence tracking', 'citations', and 'iterative review'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (generate format-controlled research reports with evidence tracking, citations, iterative review) AND when (explicit 'should be used when' clause listing specific document types and the distinguishing condition about strict formatting that deepresearch cannot enforce). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'research report', 'literature review', 'market or industry analysis', 'competitive landscape', 'policy or technical brief', 'report template', 'section formatting'. These are terms users naturally use when requesting such work. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishes itself from general research skills by emphasizing 'format-controlled', 'strict report template', and explicitly noting when to use this over 'a single deepresearch pass'. The specific document types and formatting focus create a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates best practices across all dimensions. It provides a comprehensive yet concise workflow for complex research report generation, with clear validation checkpoints, explicit file organization patterns, and well-organized references to supporting materials. The anti-patterns section adds valuable guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence throughout. No unnecessary explanations of basic concepts; every section provides actionable guidance without padding. | 3 / 3 |
Actionability | Provides concrete, executable guidance with specific file structures, implementation patterns, checklist formats, and exact column requirements for evidence tables. The Task tool usage pattern is copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with 9 clearly sequenced steps, explicit validation checkpoints (Steps 7-8), a trackable progress checklist, and clear feedback loops for human review and iteration. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear one-level-deep references to 5 supporting files. The reference table clearly signals when to load each file, and content is appropriately split between the main skill and reference materials. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Table of Contents
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.