CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-architect

Expert guide for designing and building high-quality skills from scratch through structured conversation. Use when someone wants to create a new skill, build a skill, design a skill, or asks for help making Agents do something consistently. Also use when someone says "turn this into a skill", "I want to automate this workflow", "how do I teach my Agent to do X", or mentions creating SKILL.md files. Covers standalone skills and MCP-enhanced workflows. Do NOT use for creating subagents (use subagent-creator) or technical design documents (use create-technical-design-doc).

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exemplary instruction-only skill body: a clearly sequenced five-phase workflow with per-phase exit checklists, concrete copy-paste templates, and well-signaled one-level-deep references to real bundle files. The only weakness is mild verbosity in the philosophical/rationale sections that could be tightened without losing instruction value.

DimensionReasoningScore

Conciseness

The ~376-line body is efficient: it uses tables, templates, and checklists instead of prose, assumes Claude's competence (no explanation of what a skill or MCP is), and stays under its own 500-line budget. Minor instances of over-explanation could be trimmed (e.g., the five-point Core Philosophy section and the 'Why' commentary on progressive disclosure restate what the phase guidance already shows), matching 'Efficient; minor instances of over-explanation that could be trimmed'. Not a 5 because some philosophical framing and repeated rationale paragraphs do not directly instruct.

4 / 5

Actionability

Fully concrete, copy-paste-ready guidance throughout: an exact use-case capture template, a folder-structure plan with decision criteria, a complete YAML frontmatter template with hard rules, a full SKILL.md skeleton, an anti-pattern list with examples, and a runnable validation script (scripts/validate_skill.py, verified to exist). Per the rubric's code_vs_instruction note, this instruction-only skill's guidance is highly actionable — 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

Five phases are explicitly sequenced (DISCOVERY → ARCHITECTURE → CRAFT → VALIDATE → DELIVER) with an exit-criteria checklist per phase, an explicit 'Never skip Discovery' rule, and a dedicated validation phase with structural checks, trigger testing, instruction review, and feedback loops ('If the description is too broad or too narrow, refine it now'; 'If issues exist, fix them before delivery'). This matches 'clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'.

5 / 5

Progressive Disclosure

Content is appropriately split: the body holds the core workflow while deep material lives in references/patterns.md (317 lines), references/examples.md (256 lines), references/quality-checklist.md (70 lines), and scripts/validate_skill.py (539 lines) — all verified to exist. Every reference is one level deep and clearly signaled with a load condition ('consult references/patterns.md for detailed pattern guidance', 'Run the full checklist from references/quality-checklist.md and execute scripts/validate_skill.py'), matching 'well-signaled one-level-deep references; easy navigation'.

5 / 5

Total

19

/

20

Passed

Description

86%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 excellent natural trigger phrases, explicit when/when-not guidance, and third-person voice. Its main weaknesses are a high-level 'what' that lists few concrete capabilities, and an unaddressed overlap risk with the closely related skill-creator skill.

Suggestions

Enumerate 2-3 more concrete capabilities in the 'what' clause (e.g., 'drafts frontmatter descriptions, plans folder structure, and validates skills with a checklist') to raise specificity beyond design/build generalities.

Add a negative trigger distinguishing this skill from skill-creator (e.g., 'Do NOT use for improving or evaluating existing skills — use skill-creator'), mirroring the boundary already stated in the body.

Trim the 'asks for help making Agents do something consistently' clause, which is the vaguest trigger and adds overlap risk with general automation requests.

DimensionReasoningScore

Specificity

The description names the domain ('designing and building high-quality skills') with 1-2 concrete actions (design, build, 'through structured conversation'), but does not enumerate multiple specific capabilities — matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is above a 2 because the actions are concrete rather than generic ('Processes PDF files'), and below a 4 because there is no list of several distinct specific actions.

3 / 5

Completeness

Explicitly answers both 'what' ('Expert guide for designing and building high-quality skills from scratch through structured conversation') and 'when' ('Use when someone wants to create a new skill...'), plus a scope statement ('Covers standalone skills and MCP-enhanced workflows') and explicit negative triggers ('Do NOT use for creating subagents...'). Both what and when are present with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases with synonyms: 'create a new skill, build a skill, design a skill', 'turn this into a skill', 'I want to automate this workflow', 'how do I teach my Agent to do X', 'creating SKILL.md files'. These are exactly the phrases a user would naturally say, matching the top anchor including synonyms and file-name variants.

5 / 5

Distinctiveness Conflict Risk

The description carves a clear niche and explicitly disambiguates from 'subagent-creator' and 'create-technical-design-doc' with negative triggers, but it does not address overlap with the closely related 'skill-creator' skill (which the body itself acknowledges handles improving/evaluating existing skills) — 'mostly distinct; minor overlap risk with closely related skills'. It is above a 3 because two of the nearest neighbors are explicitly excluded, and below a 5 because one plausible conflict is left unaddressed.

4 / 5

Total

17

/

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
tech-leads-club/agent-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.