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).

69

Quality

84%

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

73%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, highly actionable meta-skill with a clear phased workflow and strong validation checkpoints. The main weakness is mild verbosity in the philosophy and conversational-style sections, and reference load conditions could be more explicitly conditional.

Suggestions

Tighten the "Core Philosophy" and "Conversation Style" sections to directive bullets, cutting rationale prose that an LLM can infer, to improve token efficiency.

Convert reference pointers into explicit conditional load language (e.g. "If the user's workflow spans multiple services, read references/patterns.md section 2") so the agent knows precisely when to incur the file read.

Consider moving the category/pattern reference tables or the full anti-pattern list fully out of the body into the referenced files to reduce body length and reinforce progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient instructional content, but the "Core Philosophy" and "Conversation Style" sections add rationale prose that could be tightened; does not heavily explain concepts Claude already knows.

3 / 5

Actionability

Provides concrete templates (YAML frontmatter, folder structure), decision-criteria tables, hard rules, and checklists, plus a runnable validate_skill.py script; mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

Clear five-phase sequence (Discovery -> Architecture -> Craft -> Validate -> Deliver) with explicit exit-criteria checklists per phase and a dedicated Validate phase providing feedback loops and checkpoints.

5 / 5

Progressive Disclosure

References real one-level-deep bundle files (patterns.md, examples.md, quality-checklist.md, validate_skill.py) signaled with step context; minor gap is that load conditions are not always framed as crisp conditionals.

4 / 5

Total

16

/

20

Passed

Description

95%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, third-person description that clearly states what the skill does, when to use it with abundant natural trigger phrases, and what to avoid via explicit negative triggers. The only minor weakness is that the capability description is slightly abstract relative to listing concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete action areas ("designing and building high-quality skills from scratch through structured conversation", "Covers standalone skills and MCP-enhanced workflows"); minor gaps in coverage keep it just below comprehensive.

4 / 5

Completeness

Explicitly answers both what ("Expert guide for designing and building high-quality skills...") and when ("Use when someone wants to create a new skill...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and paraphrases: "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".

5 / 5

Distinctiveness Conflict Risk

Clear niche with explicit negative triggers ("Do NOT use for creating subagents (use subagent-creator) or technical design documents (use create-technical-design-doc)") minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 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.