CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-research-process

Builds comprehensive Claude Code skills using parallel research agents — categorization, parallel documentation gathering, anti-hallucination checkpoints, and final validation. Use when building a skill from official docs, when "research for skill" or "create comprehensive skill" is requested, or when extensive multi-source documentation gathering is needed before skill creation.

67

Quality

81%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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 process skill with excellent workflow clarity—the three-stage pipeline with quality gates and error recovery is its strongest feature. However, its actionability is limited by heavy reliance on external reference files that aren't provided in the bundle, and the content could be tightened by moving the Agent Team Alternative section to a reference file and eliminating the redundant Key Principles table.

Suggestions

Include the bundle files (agent-prompts.md, mcp-tools.md) or inline the most critical agent prompt templates so the skill is actionable without external dependencies.

Move the 'Agent Team Alternative for Stage 2' section to a reference file (e.g., references/agent-teams-alternative.md) and link to it from the main body to improve conciseness and progressive disclosure.

Remove or consolidate the 'Key Principles' table, which largely restates rules already covered in the quality gates and workflow sections.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and avoids explaining concepts Claude already knows, but it's somewhat verbose for what it conveys. The 'Agent Team Alternative' section at the end adds significant length with criteria that could be more tightly expressed, and some tables restate what's already covered in the workflow. The 'Key Principles' table largely duplicates information from the body.

2 / 3

Actionability

The skill provides concrete steps with specific commands (init_skill.py, package_skill.py) and clear agent launch patterns, but many critical details are deferred to reference files (agent-prompts.md, mcp-tools.md) that aren't provided in the bundle. The agent prompt templates—arguably the most actionable part—are entirely external. The citation format example and Task call patterns are helpful but incomplete without the referenced materials.

2 / 3

Workflow Clarity

The three-stage workflow with explicit quality gates between each stage is exemplary. Each gate has specific verification checklists, there are clear feedback loops (e.g., 'If categories overlap: merge before Stage 2', 'If citation missing: add source or mark NOT_VERIFIED'), and the error recovery section provides concrete fallback strategies. The ASCII flow diagram at the top provides excellent orientation.

3 / 3

Progressive Disclosure

The skill demonstrates good intent with references to agent-prompts.md, mcp-tools.md, and gaps-analysis.md, and the SKILL.md body stays at an overview level. However, no bundle files were provided, so the referenced files may not exist. The Agent Teams reference uses a deeply nested relative path (./../../../plugins/...) which is fragile. The inline content is well-structured but the 'Agent Team Alternative' section feels like it belongs in a separate reference file rather than inline.

2 / 3

Total

9

/

12

Passed

Description

100%

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 strong description that clearly communicates what the skill does (builds skills using a multi-step parallel research pipeline) and when to use it (with explicit trigger phrases). It uses third-person voice, includes natural trigger terms, and occupies a distinct niche that minimizes conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'categorization, parallel documentation gathering, anti-hallucination checkpoints, and final validation.' Also specifies the use of 'parallel research agents' as a method, giving a clear picture of the workflow.

3 / 3

Completeness

Clearly answers both 'what' (builds comprehensive Claude Code skills using parallel research agents with categorization, documentation gathering, anti-hallucination checkpoints, and validation) and 'when' (explicit 'Use when...' clause with three distinct trigger scenarios).

3 / 3

Trigger Term Quality

Includes natural trigger terms users would say: 'research for skill', 'create comprehensive skill', 'building a skill from official docs', 'multi-source documentation gathering', and 'skill creation'. These cover likely user phrasings well.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — the combination of 'Claude Code skills', 'parallel research agents', 'anti-hallucination checkpoints', and 'official docs' creates a very specific niche that is unlikely to conflict with generic coding or documentation skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
Jamie-BitFlight/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.