CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./examples/officeqa/.claude/skills/skill-creator/SKILL.md

The canonical home for this skill is skill-creator in sentient-agi/EvoSkill

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured, actionable meta-guide with a clear sequenced workflow and properly signaled bundle references, weakened mainly by conceptual padding that assumes too little of Claude.

Suggestions

Trim the "About Skills" and "What Skills Provide" sections and the bridge/open-field analogy; assume Claude knows what skills are.

Make validation gates explicit (e.g. "Only proceed to packaging after scripts pass tests") rather than leaving checkpoints implicit.

Consider moving the three full progressive-disclosure pattern examples into a reference file, keeping only the principle and a pointer in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient procedural guidance, but sections like "About Skills", "What Skills Provide", and the bridge/open-field analogy explain concepts Claude already knows and could be tightened.

3 / 5

Actionability

Provides concrete, copy-pasteable commands (init_skill.py, package_skill.py with full usage) and concrete worked examples, with only minor high-level gaps in the "Understand" and "Edit" steps.

4 / 5

Workflow Clarity

A clear 6-step sequence (Understand → Plan → Initialize → Edit → Package → Iterate) with validation checkpoints (test scripts, automatic packaging validation with fix-and-retry), though some checkpoints are implicit rather than explicitly gated.

4 / 5

Progressive Disclosure

References real one-level-deep bundle files (references/workflows.md, references/output-patterns.md) with clear signaling, but the lengthy inlined progressive-disclosure pattern examples represent a minor organization gap that could partly live in references.

4 / 5

Total

15

/

20

Passed

Description

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

The description cleanly states a distinct purpose with an explicit trigger clause and natural keywords, but the "what" portion stays generic rather than enumerating concrete capabilities.

Suggestions

Replace the generic "Guide for creating effective skills" with concrete actions, e.g. "Scaffold, draft, validate, and package skills...".

Add a few natural trigger synonyms (e.g. "make a skill", "build a skill") to broaden keyword coverage.

Mention the bundled scripts (init, package, validate) in the description to make capabilities more tangible.

DimensionReasoningScore

Specificity

Names the skill-creation domain with 1-2 concrete actions ("create a new skill (or update an existing skill)") but offers no comprehensive list of capabilities, matching the anchor for naming domain plus a couple actions.

3 / 5

Completeness

Explicitly answers both what ("Guide for creating effective skills") and when ("This skill should be used when users want to create a new skill (or update an existing skill)"), but the "what" is somewhat generic compared to the fully concrete anchor 5 example.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ("create a new skill", "update an existing skill") with good coverage, though a few common synonyms like "make" or "build a skill" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (skill creation/updating) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

14

/

16

Passed

Repository

sentient-agi/EvoSkill

Path

examples/officeqa/.claude/skills/skill-creator/SKILL.md

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.