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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/skill-creator/SKILL.md

Quality

Content

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

A strong, well-structured meta-skill: the six-step creation process is clearly sequenced with validation built in, and both referenced scripts exist in the bundle. The main improvements are surfacing the unused quick_validate.py script with a runnable command and trimming a few redundant benefit/best-practice passages.

Dimension	Reasoning	Score
Conciseness	The body is procedural and focused on skill-creation specifics Claude would not know, with only minor over-explanation (repeated 'Benefits' bullets and some overlap between the references best-practices and progressive-disclosure sections) that could be trimmed.	4 / 5
Actionability	It gives executable commands (`scripts/init_skill.py <skill-name> --path <output-directory>`, `scripts/package_skill.py <path/to/skill-folder> ./dist`) plus concrete worked examples, but validation is described only as something the packaging script does, and `scripts/quick_validate.py` is never surfaced with a runnable command.	4 / 5
Workflow Clarity	The six-step process is clearly sequenced with explicit skip conditions, and packaging includes a 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.'	5 / 5
Progressive Disclosure	Structure is good with clear headers and one-level-deep script references that resolve to real files (`scripts/init_skill.py`, `scripts/package_skill.py`), but `scripts/quick_validate.py` exists in the bundle without being referenced or linked from SKILL.md, a minor navigation gap.	4 / 5
	Total	17 / 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.

A solid, third-person description with an explicit when-to-use clause and distinct triggers. Its main weakness is a thin what-clause: it names the domain and two actions but no concrete capability detail, leaving it slightly generic on specificity.

Suggestions

Add 1-2 concrete capabilities to the what-clause, e.g. 'Writes SKILL.md frontmatter and instructions, scaffolds bundled scripts/references/assets directories, and validates and packages skills for distribution.'

Broaden trigger coverage with natural synonyms users say, such as 'build a skill', 'make a skill', or 'turn this workflow into a skill'.

State the concrete outputs of the guide (skill structure, packaging to a distributable zip) so the what-clause answers what the skill produces, not just its topic.

Dimension	Reasoning	Score
Specificity	The description names the domain ('creating effective skills') and states two actions ('create a new skill (or update an existing skill)'), but offers no further concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both are present: the what ('Guide for creating effective skills') and an explicit when clause ('This skill should be used when users want to create a new skill (or update an existing skill)...'). The what is thinner than the anchor-5 example, so it sits at the 'when could be more specific / what could be richer' level.	4 / 5
Trigger Term Quality	'create a new skill' and 'update an existing skill' are natural phrases users would say, giving good keyword coverage, but common synonyms such as 'build' or 'make a skill' are missing.	4 / 5
Distinctiveness Conflict Risk	Skill creation is a clear niche with distinct triggers ('new skill', 'update an existing skill'), so the risk of triggering for unrelated skills is minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	15 / 16 Passed

Repository: cteyton/packmind
Path: .github/skills/skill-creator/SKILL.md
Commit: e198635

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.