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.
85
Quality
84%
Does it follow best practices?
Impact
80%
2.05xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a well-structured description that clearly articulates capabilities, actions, and trigger conditions. The explicit 'Use when:' clause and comprehensive keyword list are strengths. The main weakness is potential overlap with general development or architecture skills due to broad terms like 'solution design' and 'technical analysis.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions including 'technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design' and explicit action verbs 'research, analyze, evaluate, compare, recommend technical solutions.' | 3 / 3 |
Completeness | Clearly answers both what (phases, capabilities, actions) AND when with explicit 'Use when:' clause covering 'researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.' | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study.' | 3 / 3 |
Distinctiveness Conflict Risk | While it has specific technical research focus, terms like 'architecture analysis,' 'solution design,' and 'best practices' could overlap with general coding/development skills. The YAGNI/KISS/DRY principles help distinguish it somewhat, but 'technical analysis' is fairly broad. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured research methodology skill with strong actionability and clear workflow phases. The main weaknesses are moderate verbosity (instructional phrasing like 'You will...') and the inline report template that could be externalized. The skill provides practical, executable guidance with specific tools and constraints.
Suggestions
Extract the report template to a separate REPORT_TEMPLATE.md file and reference it, reducing the main skill's length
Remove instructional phrasing ('You will...', 'Your final report must...') in favor of direct imperatives to improve conciseness
Trim the 'Remember' paragraph at the end - Claude doesn't need motivational framing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity (e.g., 'You will ensure all research meets these criteria', 'Remember: You are not just collecting information') and could be tightened. The report template is comprehensive but lengthy, though much of it serves as a structural reference. | 2 / 3 |
Actionability | Provides concrete, executable guidance including specific bash commands (`gemini -m gemini-3-preview-p`), file paths, tool names, and a complete markdown report template. The search strategy and tool usage are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-phase workflow with explicit sequencing (Scope Definition → Information Gathering → Analysis → Report Generation). Includes validation through cross-reference verification and specific constraints (max 5 tool calls). Fallback paths are defined (gemini → WebSearch). | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the full report template is inline rather than referenced externally. The skill is somewhat monolithic at ~120 lines when the template could be a separate reference file. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- majiayu000/claude-skill-registry
- Commit
6213d1a
- 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.