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

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A thorough, well-structured architect guide with actionable templates, hard rules, explicit phase exit criteria, and clean progressive disclosure into real reference and script files. The main weakness is mild verbosity in the persona/philosophy framing that could be trimmed for token economy.

Suggestions

Trim the Core Philosophy section and the consultant persona framing in the opening paragraph; keep only the directives that change agent behavior.

Collapse the "Important Boundaries" and "Conversation Style" sections into tighter bullet directives to reduce prose overhead.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain methodology, but the opening persona framing ("Think of yourself as a consultant") and the five-principle Core Philosophy section contain commentary Claude does not strictly need and could be tightened; not a wall of concept-explanation, so above 1.

2 / 3

Actionability

As an instruction-only skill it supplies concrete, copy-paste-ready templates (frontmatter, use-case, folder structure, instruction outline), hard rules with exact thresholds, and decision-criteria tables — specific and actionable rather than vague.

3 / 3

Workflow Clarity

A clear DISCOVERY → ARCHITECTURE → CRAFT → VALIDATE → DELIVER sequence with explicit per-phase exit-criteria checklists and a dedicated Validate phase providing feedback loops ("If issues exist, fix them before delivery").

3 / 3

Progressive Disclosure

SKILL.md is an overview pointing to one-level-deep, clearly-signaled bundle files (references/patterns.md, examples.md, quality-checklist.md, scripts/validate_skill.py), each with an explicit load condition; all referenced files exist and content is appropriately split out.

3 / 3

Total

11

/

12

Passed

Description

90%

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 well-constructed description that pairs a clear capability statement with abundant natural trigger phrases and explicit negative triggers scoping it against sibling skills. Its only weakness is that the stated actions are abstract (designing/building/guiding) rather than a concrete enumerated action list.

DimensionReasoningScore

Specificity

It names the domain ("designing and building high-quality skills") and notes scope ("Covers standalone skills and MCP-enhanced workflows"), but the actions are abstract consulting verbs rather than a list of multiple concrete operations as the 3-anchor expects.

2 / 3

Completeness

It states what ("Expert guide for designing and building high-quality skills") and explicit when clauses ("Use when someone wants to create a new skill...") plus a not-when ("Do NOT use for creating subagents..."), clearly answering both what and when.

3 / 3

Trigger Term Quality

Strong coverage of natural phrases users would say — "turn this into a skill", "I want to automate this workflow", "how do I teach my Agent to do X", "create a new skill", "creating SKILL.md files" — matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

A clear niche (skill creation) with explicit negative triggers naming sibling skills ("use subagent-creator", "use create-technical-design-doc"), making conflict with other skills unlikely; uses third-person voice with no first/second-person penalty.

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