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

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 a well-sequenced six-step workflow with an explicit validation feedback loop and concrete, executable commands backed by real bundle files. Main weaknesses are moderate verbosity in promotional asides and a minor organization gap where the bundled quick_validate.py script is never mentioned.

Suggestions

Trim promotional filler (e.g., 'conveniently generates... much more efficient and reliable') and collapse the repeated 'Benefits' bullets under each resource type into a single shared rationale.

Reference scripts/quick_validate.py in the workflow (e.g., as a fast pre-packaging check) so all bundled scripts are discoverable from SKILL.md.

Consider moving the detailed 'Anatomy of a Skill' and bundled-resource guidance to a references file, keeping SKILL.md to the essential creation workflow.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-scoped sections, but contains noticeably padded promotional language ("conveniently generates... making the skill creation process much more efficient and reliable") and repetitive rationale bullets ("Benefits" lists under each resource type) that could be trimmed. It is not a 4 because multiple sentences are filler rather than isolated minor instances, and not a 2 because the core structure and examples are genuinely useful.

3 / 5

Actionability

Provides copy-paste-ready commands for both bundled scripts ('scripts/init_skill.py <skill-name> --path <output-directory>' and 'scripts/package_skill.py <path/to/skill-folder>'), plus three worked analysis examples (pdf-editor, frontend-webapp-builder, big-query). It is not a 5 because Step 4's question list and Step 6's iteration guidance are abstract ("Implement changes and test again") rather than executable, leaving minor gaps.

4 / 5

Workflow Clarity

The six-step creation process is clearly sequenced with explicit skip conditions per step, and packaging includes a full validation feedback loop: "If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again." This matches the anchor with explicit validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

A single well-organized SKILL.md (~1,660 words, under the 5k budget) with clean one-level-deep references to real bundled scripts (init_skill.py, package_skill.py both verified to exist). It is not a 5 because the bundled scripts/quick_validate.py is never referenced or surfaced, and the lengthy 'Anatomy of a Skill' teaching section could arguably move to a references file.

4 / 5

Total

16

/

20

Passed

Description

82%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 explicitly answers both 'what' and 'when' in third person with concrete trigger phrases and minimal conflict risk. Its only weakness is that the action list is thin — it names create/update but omits the planning, packaging, and iteration capabilities the skill actually provides.

DimensionReasoningScore

Specificity

The description names the domain ("creating effective skills") and two concrete actions ("create a new skill", "update an existing skill"), which matches the anchor for 1-2 concrete actions that are not comprehensive. It is not a 4 because it does not list several specific actions (e.g., planning, packaging, iterating on skills) that the skill actually covers.

3 / 5

Completeness

It clearly 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)...") with concrete trigger phrases. It is not a 4 because the 'when' clause is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Natural user phrases like "create a new skill" and "update an existing skill" are present and would be said verbatim by users. It is not a 5 because common synonyms such as "build a skill", "make a skill", "write a skill", or "package a skill" are missing.

4 / 5

Distinctiveness Conflict Risk

The skill-authoring niche is distinct and unlikely to trigger for unrelated skills; the trigger conditions are narrowly scoped to creating or updating skills. No neighboring anchor fits better.

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

15

/

16

Passed

Repository

cteyton/packmind

Path

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