CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

86

2.05x
Quality

Does it follow best practices?

Impact

80%

2.05x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-sequenced and actionable with concrete commands and validation steps, but it is padded by a large generic report template and makes no use of progressive disclosure to offload that template to a reference file.

Suggestions

Replace the ~70-line Phase 4 report template with a concise required-structure summary, or move it to a referenced REPORT_TEMPLATE.md, since Claude already knows standard report sections.

Trim 'Quality Standards' and 'Special Considerations' to only the non-obvious rules (e.g., the 12-month currency rule, CVE checks for security topics) to reduce token overhead.

Split the bulky report template into a one-level-deep reference file and link to it from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The search-strategy guidance is lean and valuable, but the ~70-line Phase 4 report template (e.g., "## Executive Summary [2-3 paragraph overview]", "### A. Glossary [Technical terms and definitions]") restates generic report structure Claude already knows, so it could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance such as `gemini -m gemini-3-preview-p "..."` with a 10-minute timeout, a WebSearch fallback, the `docs-seeker` skill, exact output paths, and a max-5-call limit.

3 / 3

Workflow Clarity

A clearly sequenced four-phase process with an explicit Cross-Reference Validation step ("Verify information across multiple independent sources", "Check publication dates") and a Quality Standards checklist acting as a process gate.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single >50-line monolithic document; the bulky report template is inline content that could be split into a clearly signaled one-level reference rather than living in SKILL.md.

2 / 3

Total

10

/

12

Passed

Description

92%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong and specific, clearly stating capabilities, actions, and an explicit "Use when" trigger clause. Its main weakness is the broad "research" framing, which risks overlap with other research or planning skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("research, analyze, evaluate, compare, recommend technical solutions") and specific capabilities ("technology evaluation, architecture analysis, trade-off assessment, solution design"), matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (phases, capabilities, actions) and when via a present "Use when:" clause, satisfying the explicit-trigger requirement that prevents a cap at 2.

3 / 3

Trigger Term Quality

The "Use when" clause supplies natural phrases users would actually say ("researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Although narrowed to technical research, the skill name "research" and broad triggers like "best practices" and "compare solutions" could overlap with general research, planning, or web-search skills, so it is not a clearly conflict-free niche.

2 / 3

Total

11

/

12

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
majiayu000/claude-skill-registry
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.