CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-creator

Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".

64

Quality

78%

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 ./src/opensquilla/skills/bundled/skill-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-sequenced, largely actionable skill-creation guide with real bundled scripts and a packaging validation loop, undermined by conceptual padding in its intro sections and a concrete progressive-disclosure defect: it points to two reference files that are not present in the bundle.

Suggestions

Trim the 'About Skills', 'What Skills Provide', and degrees-of-freedom bridge/field metaphor sections — assume Claude already knows what skills are and keep only non-obvious procedural guidance to improve token efficiency.

Resolve the dead references: either add references/workflows.md and references/output-patterns.md to the bundle, or remove the 'See references/workflows.md' / 'See references/output-patterns.md' pointers in the 'Learn Proven Design Patterns' section.

Strengthen Step 4's body-authoring guidance with a concrete SKILL.md template or checklist, since 'Write instructions for using the skill and its bundled resources' is currently high-level.

DimensionReasoningScore

Conciseness

The actionable core (Steps 1-6, anatomy reference, commands) is efficient, but conceptual sections like 'About Skills', 'What Skills Provide', and the degrees-of-freedom bridge/field metaphor explain ideas Claude already knows and could be trimmed.

3 / 5

Actionability

Provides copy-paste-ready, executable commands for the real bundled scripts ('scripts/init_skill.py my-skill --path skills --resources ...', 'scripts/package_skill.py <path/to/skill-folder> ./dist') plus concrete planning examples, with minor gaps in the high-level body-authoring guidance of Step 4.

4 / 5

Workflow Clarity

The 6-step creation process is clearly sequenced with explicit validation and a feedback loop in Step 5 ('If validation fails... Fix any validation errors and run the packaging command again') and Step 6 iteration, but lacks explicit checklists and leaves Step 4 testing somewhat loose ('a representative sample').

4 / 5

Progressive Disclosure

Structure and the bundled scripts are well-organized and one level deep, but the body directs Claude to consult 'references/workflows.md' and 'references/output-patterns.md' for established best practices, and the references/ directory does not exist in the bundle — dead references that break navigation.

3 / 5

Total

14

/

20

Passed

Description

92%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, exemplar-style description that clearly states capabilities and explicit trigger conditions with natural phrasing and synonyms. Its only weakness is mild verbosity — the trigger phrases are enumerated twice (in the 'Use when' clause and again in the 'Triggers on phrases like' list).

DimensionReasoningScore

Specificity

Lists multiple concrete actions spanning the full lifecycle — 'Create, edit, improve, or audit AgentSkills' plus 'moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ('Create, edit, improve, or audit AgentSkills') and when ('Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage with synonyms ('create a skill'/'author a skill', 'tidy up'/'clean up'), but a few common variations a user might say ('make/build/write a skill', 'update/fix the skill') are missing, so it stops short of fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear meta-niche (skill authoring) with triggers tied specifically to 'skill'/'SKILL.md'/'skill directory', keeping conflict risk with domain or code-review skills minimal.

5 / 5

Total

19

/

20

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: 6 missing

Warning

referenced_paths_exist

Referenced path issues: 14 missing

Warning

Total

13

/

16

Passed

Repository
TokenRhythm/opensquilla
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.