CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

Deep research into technical solutions by searching the web, examining GitHub repos, and gathering evidence. Use when the user explicitly says "use the research skill", "use a research agent", or asks for deep/thorough research into implementation options or technologies.

76

2.00x
Quality

80%

Does it follow best practices?

Impact

62%

2.00x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/toolkit/skills/research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a well-structured, actionable research workflow with concrete commands, an explicit evidence-quality gate, error-recovery paths, and a defined output format. It scores solidly across dimensions but leaves minor room to trim redundant lists and tighten guidance.

Suggestions

Trim lists that restate Claude's existing knowledge (e.g., "Look for: README documentation, Code examples, Architecture patterns") to improve conciseness.

Replace the placeholder clone URL with a realistic example and specify what a repo summary in ./scratch/research/ should contain to make guidance fully copy-paste ready.

Merge or shorten the Example Usage section, which partially repeats the Research Process steps.

DimensionReasoningScore

Conciseness

The body is efficient with concrete commands and templates throughout, but a few lists tell Claude things it already knows ("Look for: README documentation, Code examples, Architecture patterns"), fitting anchor 4 (efficient, minor instances that could be trimmed) rather than the every-token-earns-its-place level of 5.

4 / 5

Actionability

Provides mostly executable guidance — copy-paste bash commands (git clone, mkdir), a complete output-format template, and a fully worked example — with minor gaps such as the placeholder owner/repo and no concrete structure for repo summaries, matching anchor 4.

4 / 5

Workflow Clarity

Five clearly sequenced steps with an explicit evidence gate ("Minimum 2-3 datapoints required") and fallback paths (blocked content → ask user; insufficient evidence → ask guidance). The checkpoints are present but slightly softer than the explicit validate/fix/re-validate rigor of anchor 5.

4 / 5

Progressive Disclosure

A single well-organized self-contained file with clear section headers and no nested or buried references. At ~100 lines it sits above the simple-skill threshold where organization alone earns a 5, so anchor 4 (good structure, minor organization gaps) is the best fit.

4 / 5

Total

16

/

20

Passed

Description

78%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 third-person capability statement and a concrete "Use when..." trigger clause. Its main weakness is moderate specificity — one of its three named actions ("gathering evidence") is generic, and common trigger synonyms are absent.

DimensionReasoningScore

Specificity

The description names the domain ("Deep research into technical solutions") and two concrete actions ("searching the web", "examining GitHub repos"), but "gathering evidence" is generic and overall coverage is not comprehensive, matching anchor 3 rather than the several-distinct-actions level of anchor 4.

3 / 5

Completeness

It clearly answers both questions: a third-person "what" (web search, GitHub repo examination, evidence gathering) and an explicit "Use when..." clause with concrete trigger phrases, exactly matching anchor 5.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("deep/thorough research", "implementation options or technologies", "use the research skill") but misses common synonyms like "investigate", "compare", or "evaluate", fitting anchor 4 (good coverage, a few natural terms missing).

4 / 5

Distinctiveness Conflict Risk

The deep-research/evidence-gathering niche has distinct triggers and is clearly distinguishable, with only minor overlap risk against generic web-search or code-exploration capabilities, matching anchor 4.

4 / 5

Total

16

/

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

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

dwmkerr/claude-toolkit

Path

plugins/toolkit/skills/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.