CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator

Use when creating or updating a Codex skill package with focused triggers, progressive disclosure, evals, evidence, or tool integration.

Quality

72%

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 ./skills-system/skill-creator/SKILL.md
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 strong, executable creation workflow with explicit validation and feedback loops, and its bundle references are real, one level deep, and well signaled. Main weaknesses are redundant validation/forward-testing guidance that inflates token cost and minor command gaps in the SDK pipeline section.

Suggestions

Merge the 'Protect Validation Integrity' section with the 'Forward-testing' section (or cross-link them) to eliminate the duplicated leaked-context guidance and cut tokens.

Move the 11-step SDK pipeline detail into a reference file and keep a short summary plus the entry-point command in SKILL.md, completing the ellipsized './bin/ask sdk eval run ...' command.

Link the existing references/evals.yaml and references/skill-factory/ files from the relevant workflow steps so all bundled references are discoverable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly imperative and example-driven, but the leaked-context guidance is stated twice ('Protect Validation Integrity' and 'Forward-testing' repeat 'pass raw artifacts, not your conclusions' / 'avoid showing expected answers'), and padded or broken lines ('The context window is a public good...', 'User testing often this happens right after...', 'modifictions') could be trimmed or fixed.

3 / 5

Actionability

Core workflows give copy-paste-ready commands (init_skill.py with concrete examples, quick_validate.py, generate_openai_yaml.py) and concrete forward-test prompt examples, but the SDK pipeline includes ellipsized commands ('./bin/ask sdk eval run ...') and steps given only as prose ('Strict audit and package verify'), leaving minor gaps.

4 / 5

Workflow Clarity

The six-step creation process is clearly sequenced with an explicit validation checkpoint ('run quick_validate.py ... If validation fails, fix the reported issues and run the command again'), feedback loops for error recovery, an iterate workflow, and explicit decision rules for risky forward-testing.

5 / 5

Progressive Disclosure

All paths cited in the body exist in the bundle and are one level deep and clearly signaled ('See references/openai_yaml.md for field definitions and examples'), but the 11-step SDK pipeline is inlined rather than split into a reference, and bundled files like references/evals.yaml and references/skill-factory/ are not navigable from SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

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

The description has an explicit, natural trigger clause and a distinct niche, but it is a single 'Use when' sentence that never states what the skill does, leaving both the capability list and the 'what' under-specified. Adding a leading capability statement would lift completeness and specificity substantially.

Suggestions

Prepend a concrete 'what' statement before the 'Use when' clause, e.g., 'Guides creation and maintenance of Codex skill packages: designing triggers, structuring progressive disclosure, writing evals, and packaging evidence.'

List several specific concrete actions (e.g., 'generates skill scaffolding via init_skill.py, validates packages, writes SKILL.md frontmatter, generates agents/openai.yaml') to raise specificity beyond the generic create/update pair.

Add natural synonym trigger terms users would actually say, such as 'build a skill', 'author a skill', 'make a SKILL.md', or 'skill template'.

DimensionReasoningScore

Specificity

The description names the domain ('creating or updating a Codex skill package') and one to two actions, but 'creating or updating' are generic actions and the trailing aspect list ('focused triggers, progressive disclosure, evals, evidence, or tool integration') enumerates attributes rather than concrete actions, so coverage is not comprehensive.

3 / 5

Completeness

An explicit 'Use when...' clause answers 'when' clearly, but the 'what' is only weakly implied by the when-clause — the description never states what the skill actually does (e.g., guides skill creation), matching the anchor for a clear trigger with a missing or implied 'what'.

3 / 5

Trigger Term Quality

Natural phrases users would say ('creating or updating', 'skill package', 'evals', 'tool integration') are present with good keyword coverage, but common variations like 'build a skill', 'author', or 'SKILL.md' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'Codex skill package' niche with evals and evidence focus is mostly distinct with targeted triggers; minor overlap risk remains with adjacent meta-authoring or documentation workflows.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

jscraik/Agent-Skills

Path

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