CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.

Quality

77%

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

Quality

Content

63%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 methodology with genuinely concrete tooling guidance (gemini/WebSearch commands, paths, call limits) and a clear phase sequence. Its main weaknesses are an oversized inlined report template that inflates token cost and belongs in a references/ file, plus abstract directives and motivational padding that could be trimmed.

Suggestions

Move the full report structure template to references/report-template.md and keep only a short outline in SKILL.md, restoring progressive disclosure and cutting ~70 lines of body tokens.

Trim motivational/padded lines ("Remember: You are not just collecting information...", "[Comprehensive description of the technology/topic]") and merge the overlapping Quality Standards and Special Considerations sections into one concise list.

Add explicit validation checkpoints: verify the report file was written to the correct path, and specify what to do when searches return conflicting or empty results (a fix-and-retry feedback loop for the search phase).

DimensionReasoningScore

Conciseness

Mostly efficient — no explaining of concepts Claude already knows — but the ~70-line report template includes self-evident placeholders ("[Forums, Discord servers, Stack Overflow tags]"), motivational padding ("Remember: You are not just collecting information..."), and partially redundant Quality Standards vs Special Considerations sections. Not a 4 because the tightening opportunities are more than minor.

3 / 5

Actionability

Mostly executable guidance: a concrete command with model flag and timeout ("gemini -m gemini-2.5-flash -p '...' bash command (timeout: 10 minutes)"), a WebSearch fallback, exact save paths ("./plans/<plan-name>/reports/YYMMDD-<your-research-topic>.md"), and a hard 5-tool-call limit. Held back from 5 by abstract Phase 1/3 directives ("Identifying key terms", "Evaluating pros and cons") that Claude would do unprompted.

4 / 5

Workflow Clarity

Clear Phase 1→4 sequence with a fallback chain (gemini → WebSearch), explicit constraints (max 5 tool calls), and a clarifying instruction to ask for a plan name. Not a 5 because there are no explicit output validation or error-recovery checkpoints (e.g., verifying the report was saved or handling empty search results); not a 3 because the sequence and fallbacks cover most checkpoints.

4 / 5

Progressive Disclosure

The body is well-sectioned with headers, but it is a single monolithic file with no bundle files, and the large report template inlined in SKILL.md clearly belongs in a separate references file. This matches the anchor "Some structure but could be better organized; content that should be separate is inline" — the sub-50-line exception does not apply at ~160 lines.

3 / 5

Total

14

/

20

Passed

Description

80%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, explicit description that clearly answers both what the skill does and when to use it, with good natural trigger phrases. Its weaknesses are moderate: keyword-stuffed jargon (YAGNI/KISS/DRY) that users would not naturally say, and broad categorical actions that raise conflict risk with other research/analysis skills.

DimensionReasoningScore

Specificity

Lists several concrete verb+object actions ("research, analyze, evaluate, compare, recommend technical solutions"; "technology evaluation, architecture analysis, trade-off assessment, solution design") with only minor gaps. Falls short of a 5 because several entries are broad categories rather than the crisp, fully concrete actions of the top anchor.

4 / 5

Completeness

Explicitly answers both questions: the "what" via Phases/Capabilities/Actions lists and the "when" via an explicit "Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems" clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("researching technologies", "comparing solutions", "evaluating architectures", "best practices", "feasibility study") with synonyms, but jargon terms like "YAGNI, KISS, DRY" are not phrases users naturally say when they need this skill, and a few common variations are missing.

4 / 5

Distinctiveness Conflict Risk

Anchored to a technical-research niche by the YAGNI/KISS/DRY framing, but broad terms like "research", "analyze", "evaluate", "best practices", and "competitive analysis" create real overlap risk with generic research and analysis skills. Not a 4 because the differentiation relies more on jargon labels than distinct triggers.

3 / 5

Total

16

/

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

samhvw8/dot-claude

Path

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.