CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

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 ./.claude/skills/skill-creator/SKILL.md

The canonical home for this skill is skill-creator in chrisboden/cursor-skills

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 clear, well-sequenced creation workflow with executable script references and a validation loop in the packaging step. Its main weakness is conciseness, as it explains skill fundamentals Claude already knows rather than staying purely procedural.

Suggestions

Trim the 'About Skills' / 'What Skills Provide' / anatomy exposition, which restates concepts Claude already knows; keep only the non-obvious procedural guidance.

Pull the detailed directory-anatomy diagram into a references file and link to it from SKILL.md so the overview stays lean.

Add an explicit validation/checklist checkpoint after Step 4 (editing SKILL.md) rather than relying solely on the packaging script to catch issues.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural guidance, but the 'About Skills' section spends lines explaining what skills are and the 'onboarding guides' metaphor, which Claude already understands and could be trimmed.

3 / 5

Actionability

It gives concrete, executable commands (e.g., `scripts/init_skill.py <skill-name> --path <output-directory>` and `scripts/package_skill.py <path/to/skill-folder>`) with worked examples, though a few sections rely on high-level directives like 'analyze each example'.

4 / 5

Workflow Clarity

The six-step Skill Creation Process is clearly sequenced with skip-condition guidance, and Step 5 includes an explicit validate-then-fix-then-rerun loop, but validation checkpoints are concentrated in packaging rather than spread across fragile steps.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections and references real one-level-deep bundle scripts (init_skill.py, package_skill.py), but the body inlines conceptual material that could be referenced rather than explaining the full skill anatomy inline.

4 / 5

Total

15

/

20

Passed

Description

83%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 is clear, well-structured, and explicitly answers both what the skill does and when to use it in third-person voice. It is slightly held back by abstract phrasing in the extension clause and a few missing natural synonyms.

Suggestions

Add concrete output actions (e.g., 'scaffold, write, validate, and package a skill') to lift specificity from abstract extension language.

Include common synonyms users say, such as 'build' or 'make a skill', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions ('create a new skill', 'update an existing skill', extending with 'specialized knowledge, workflows, or tool integrations'), but the extension clause stays somewhat abstract rather than enumerating concrete outputs.

4 / 5

Completeness

It explicitly states both what it does ('Guide for creating effective skills') and when to use it ('This skill should be used when users want to create a new skill (or update an existing skill)') with concrete trigger phrases, in proper third-person voice.

5 / 5

Trigger Term Quality

It includes natural phrases users would say ('create a new skill', 'update an existing skill') plus 'skills', 'workflows', and 'tool integrations', though synonyms like 'build' or 'make a skill' are missing.

4 / 5

Distinctiveness Conflict Risk

Skill creation is a clear, distinct niche with specific triggers, but the broad framing around 'specialized knowledge, workflows, or tool integrations' leaves minor overlap risk with general coding or authoring skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

15

/

16

Passed

Repository
SynkraAI/aiox-core
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.