CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-creator

Create or update Claude skills. Use for new skills, skill references, skill scripts, optimizing existing skills, extending Claude's capabilities.

59

Quality

70%

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
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with concrete commands and examples and a well-organized real bundle, but it is overlong with duplicated content, has a step-numbering error, and keeps too much detail inline rather than in references.

Suggestions

Deduplicate the 150-line rule and .env precedence order into a single statement and move the full .env order into a references file, cutting the body toward its 150-line target.

Fix the duplicate 'Step 5' heading (Edit vs Packaging) and add explicit validation checkpoints after the planning and editing steps.

Move the 'About Skills' / anatomy and detailed requirements sections into a references file, leaving SKILL.md as a lean overview that points to them.

DimensionReasoningScore

Conciseness

The ~300-line body exceeds its own 150-line budget and repeats the 150-line rule ~5 times and the .env precedence order 3 times; it is mostly practical but contains clear duplication that could be tightened.

2 / 3

Actionability

It provides concrete executable script invocations with exact arguments (init_skill.py, package_skill.py) and specific worked examples mapping task types to bundle resources, which are copy-paste ready.

3 / 3

Workflow Clarity

A clear 6-step sequence exists with an explicit validate->fix->retry loop in packaging, but two steps are both labeled 'Step 5' and most creation steps lack explicit validation checkpoints.

2 / 3

Progressive Disclosure

References and scripts are real, clearly signaled, and one level deep with easy navigation, but SKILL.md is a dense ~300-line overview with inline content (anatomy, .env orders) that its own guidance says belongs in reference files.

2 / 3

Total

9

/

12

Passed

Description

75%

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 answers both what and when with an explicit trigger clause and occupies a clearly distinct niche, but its action verbs are somewhat abstract and its trigger-term coverage is narrow.

Suggestions

Replace abstract verbs with concrete capabilities, e.g. 'Create SKILL.md files, scaffold scripts/references/assets bundles, package and validate skills for distribution'.

Broaden natural trigger terms to include phrasing users actually say, such as 'make a skill', 'build a skill', 'write a skill', 'scaffold a skill'.

DimensionReasoningScore

Specificity

It lists several actions ('Create or update', 'optimizing', 'extending') but they are abstract high-level verbs rather than concrete capabilities, so it names the domain and some actions without being comprehensive.

2 / 3

Completeness

It clearly states what the skill does ('Create or update Claude skills') and provides an explicit 'Use for ...' trigger clause listing multiple scenarios, satisfying both what and when.

3 / 3

Trigger Term Quality

Terms like 'new skills', 'skill references', 'skill scripts' are natural but coverage is narrow and centered on the word 'skill', missing common phrasing variations like 'make' or 'build a skill'.

2 / 3

Distinctiveness Conflict Risk

Skill authoring is a distinct meta-level niche with triggers ('create a skill', 'optimize existing skills') unlikely to conflict with normal task skills.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

13

/

16

Passed

Repository
mrgoonie/claudekit-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.