CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator

Guide for creating effective skills. Use this skill when users need to create a new skill or reshape a draft skill package before hardening, benchmarking, or distribution.

Quality

73%

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 ./Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/scaffolding_templates/scaffolding_templates/skill-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized, route-focused overview with a clear when-to-use boundary, but its core execution guidance is abstract: it never names the validation commands, the required canonical files, or the scripts in its own bundle. Roughly half the bundle is unnavigable from SKILL.md.

Suggestions

Name the concrete validation commands in the workflow (e.g. "python scripts/quick_validate.py <skill_path>") and add a fix-and-re-validate checkpoint so step 5 is executable with an explicit feedback loop.

List the required canonical files (SKILL.md, references/, agents/openai.yaml) explicitly in workflow step 3 instead of the unspecified "required files with canonical names".

Add Read-when signposts for the remaining bundle content — scripts/ (init_skill.py, generate_openai_yaml.py, render_handoff_package_template.py) and the unrouted reference files (contract.yaml, evals.yaml, task-profile.json, creation-playbook.md, prompt-injection-patterns.json) — so the whole package is navigable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean with terse bullets and no explanations of known concepts, but the relocate-detail-to-references policy is restated three times ("Core Philosophy", workflow step 4, and "Progressive disclosure policy") and the opening line duplicates the frontmatter description, so it falls just short of 'every token earns its place'.

4 / 5

Actionability

The output contract enumerates concrete fields and the Read-when routes name specific files, but "Run baseline validation commands" and "Create/update required files with canonical names" never name the actual commands (e.g. scripts/quick_validate.py) or the required files, leaving key execution details missing.

3 / 5

Workflow Clarity

The five-step workflow is clearly sequenced with validation as the final step, but there is no error-recovery checkpoint or feedback loop and the validation step itself is unspecified, matching 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The Read-when section gives clear one-level signposts, but only 3 of the 10 reference files are routed from the body, the scripts/ directory is entirely unreachable, and the cited references are stubs that chain to another path, so navigation gaps go beyond the 'minor organization gaps' of the anchor above.

3 / 5

Total

13

/

20

Passed

Description

78%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 with an explicit what-plus-when structure and natural trigger phrasing. Its main weakness is moderate action specificity and unlisted synonyms for how users might ask for skill creation.

DimensionReasoningScore

Specificity

"create a new skill or reshape a draft skill package" names the domain and about two concrete actions, but does not enumerate several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

It explicitly answers what ("Guide for creating effective skills") and when ("Use this skill when users need to create a new skill or reshape a draft skill package") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"create a new skill" and "reshape a draft skill package" are natural user phrases with good coverage, but common variations like "make/build/write a skill" or "SKILL.md" are missing, so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The lifecycle delimiter "before hardening, benchmarking, or distribution" carves a distinct pre-hardening niche from related skills like skill-builder, but the description alone leaves minor overlap risk with closely related skill-management skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/skill-factory/fixtures/budget-archive/2026-04-19/skills/scaffolding_templates/scaffolding_templates/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.