CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator

Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 delivers concrete, executable guidance through a clearly sequenced six-step workflow with checklists and script examples, and it appropriately keeps all instructional content in SKILL.md per its own progressive-disclosure philosophy. Its main weaknesses are significant repetition of the same placement/testing rules across sections and an orphaned bundled script (package_skill.py) that the body never mentions.

Suggestions

Consolidate the repeated resource-placement rules into a single section: the '>500 lines for references' and 'default everything to SKILL.md' guidance currently appears five or more times across the structure spec, planning checklist, examples, editing guidelines, and best-practices sections.

Add a brief Usage section for the bundled scripts/package_skill.py (e.g., when and how to package a skill for distribution), since it ships in scripts/ but is never referenced in the body.

Strengthen the validation checkpoint in Step 5 by removing the 'optional' framing or adding an explicit fix-and-revalidate loop (run quick_validate.py, fix reported issues, re-run until clean), and provide exact commands for the install workflow's fetch/extract steps.

DimensionReasoningScore

Conciseness

The body is mostly high-signal, non-obvious procedural guidance (COW workspace paths, metadata.requires, env_config, script conventions) and avoids explaining concepts Claude already knows, but core rules are repeated heavily: the 'references only if >500 lines / default everything to SKILL.md' guidance appears at least five times (structure spec, planning checklist, examples, editing guidelines, best practices) and 'test scripts before including' appears three times. This fits 'mostly efficient but could be tightened'; it is not a 2 because the repetition is re-contextualized for skimming rather than padded filler explaining known concepts.

3 / 5

Actionability

Guidance is largely copy-paste executable: "scripts/init_skill.py <skill-name> --path <output-directory> [--resources scripts,references,assets] [--examples]" with three concrete invocations, "scripts/quick_validate.py <path/to/skill-folder>", complete YAML metadata blocks, and a ready bash API-key guard. It stops short of a 5 because the installation workflow's table gives only high-level actions ("Fetch content via curl or web_fetch") without exact commands, and no complete worked example of a finished small SKILL.md is shown.

4 / 5

Workflow Clarity

The six-step creation process (Understand, Plan, Initialize, Edit, Validate, Iterate) is clearly sequenced with per-step skip conditions, a planning checklist, and an iterate-for-improvement feedback loop, matching 'clear sequence with most checkpoints present'. It is not a 5 because validation is explicitly marked '(optional)' and 'optional in COW' with no fix-and-revalidate error-recovery loop at that step, which weakens the checkpoint.

4 / 5

Progressive Disclosure

The body is well-sectioned with headers, stays under its own 500-line guidance, and clearly navigates to the bundled scripts init_skill.py and quick_validate.py with usage syntax and examples. It is not a 5 because the bundled scripts/package_skill.py is never referenced anywhere in the body, leaving it undiscoverable — a minor organization gap consistent with the 'good structure; minor organization gaps' anchor.

4 / 5

Total

15

/

20

Passed

Description

87%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 description that clearly states what the skill does and when to use it, with concrete numbered triggers and an explicit always-use directive. Trigger terms are natural but could add synonyms like 'make' or 'build a skill', and naming more supported sub-actions would round out coverage.

DimensionReasoningScore

Specificity

The description lists three concrete actions ("Create, install, or update skills in the workspace") plus three enumerated trigger scenarios, matching the 'several specific actions; minor gaps in coverage' anchor. It is not a 5 because sub-capabilities the skill actually supports (validating, packaging skills) are not named, and the verbs remain fairly high-level.

4 / 5

Completeness

It explicitly answers both questions: 'what' via "Create, install, or update skills in the workspace" and 'when' via the numbered "Use when (1)... (2)... (3)" clause reinforced by "Always use this skill for any skill installation or creation task". This matches the anchor-5 example pattern of concrete what + explicit trigger phrases, so a 4 (weaker 'when') does not fit.

5 / 5

Trigger Term Quality

Triggers use natural user phrasing like "installing a skill from a URL", "creating a new skill from scratch", and "updating or restructuring existing skills". It falls short of the comprehensive anchor because common synonyms such as 'make', 'build', 'add', or 'download a skill' are missing, though coverage is otherwise good.

4 / 5

Distinctiveness Conflict Risk

Skill creation/installation is a clear meta-niche with distinct triggers ("from a URL", "from scratch", "restructuring") that ordinary task skills would not match, giving minimal conflict risk. The decisive "Always use this skill for any skill installation or creation task" statement further cements the niche rather than broadening it into overlap.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

15

/

16

Passed

Repository

zhayujie/CowAgent

Path

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.