CtrlK
BlogDocsLog inGet started
Tessl Logo

research

Deep research on an idea before writing a PRD. Explores existing solutions via web search, analyzes competitors, assesses technical feasibility, and optionally explores the codebase. Use when asked to "research this idea", "investigate this feature", "what already exists for X", "explore solutions for X", "do research before the PRD", "look into X", or /research. Outputs a structured research document at docs/research/{name}.md. Suggests running /prd-designer as the next step. Dependencies: WebSearch (optional).

73

Quality

90%

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

85%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, actionable research workflow with clear sequencing and clean progressive disclosure. The relative lows are conciseness (mild Edge Cases redundancy) and actionability (no search-query templates), both at 4.

Suggestions

Trim the Edge Cases section to only cases not already covered by the Phase 2 degradation rules (e.g., 'file path doesn't exist', 'codebase search returns nothing') to remove redundancy and tighten conciseness.

Add 1–2 example WebSearch query templates per web dimension to make the existing-solutions and competitor searches more directly executable.

DimensionReasoningScore

Conciseness

The four-phase structure is lean and assumes Claude's competence, but the Edge Cases section largely restates already-given degradation rules (WebSearch unavailable, no codebase, vague idea), a minor instance of content that could be trimmed.

4 / 5

Actionability

Names concrete tools (WebSearch, Glob, Grep, Read), quotes exact prompts, and specifies output formats (comparison table with name/description/pros/cons/relevance), but lacks example search-query templates, leaving a minor gap.

4 / 5

Workflow Clarity

Clear Intake → Research → Synthesis → Handoff sequence with explicit validation checkpoints (confirm understanding, clarifying-question gate, Phase 4 review) and degradation rules acting as error-recovery feedback loops.

5 / 5

Progressive Disclosure

The body is a clear overview pointing to two well-signaled one-level-deep references (references/research-template.md, references/dimensions.md), both verified to exist, with detail appropriately split into those files.

5 / 5

Total

18

/

20

Passed

Description

96%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, specific description with excellent trigger-term coverage and explicit what/when guidance. The only soft spot is mild overlap risk from broad research verbs, which keeps distinctiveness at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Explores existing solutions via web search, analyzes competitors, assesses technical feasibility, and optionally explores the codebase' — plus a concrete output ('structured research document at docs/research/{name}.md'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (research actions and output artifact) and when ('Use when asked to …') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural phrasings — 'research this idea', 'investigate this feature', 'what already exists for X', 'explore solutions for X', 'do research before the PRD', 'look into X', and /research — cover synonyms and variations a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The pre-PRD framing, /research command, and /prd-designer handoff carve a clear niche, but broad verbs like 'look into X' and 'investigate this feature' carry minor overlap with general investigative skills, so it sits below the minimal-conflict anchor.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MrToxy/claude-skills
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.