CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 exceptionally concrete, executable guidance with a well-sequenced eval-and-iterate workflow and a genuine feedback loop. Its weaknesses are conversational padding and duplicate statements of the core loop, and — more seriously — references to files (agents/*.md, eval-viewer/generate_review.py) that are missing from the bundle, which undermines both navigation and the workflow steps that depend on them.

Suggestions

Ship the missing referenced files (agents/grader.md, agents/comparator.md, agents/analyzer.md, agents/openai.yaml, eval-viewer/generate_review.py) or rewrite the workflow steps to not depend on them — the grade/aggregate/viewer steps currently point to nonexistent paths.

Trim the chatty asides and remove the duplicated core-loop summary at the end; the body exceeds its own 500-line guidance largely due to filler and repetition.

Move the long Description Optimization details into a reference file, and add a table of contents to references/schemas.md (431 lines) as the skill's own guidance requires.

DimensionReasoningScore

Conciseness

The body is mostly efficient, concrete instruction, but contains noticeable padding: chatty asides ('Cool? Cool.', the plumbers-and-grandparents riff, 'we are trying to create billions a year in economic value here!', 'Sorry in advance but I'm gonna go all caps here'), and the core loop is stated twice ('Repeating one more time the core loop here for emphasis'). It does not reach the score-2 anchor's 'several unnecessary explanations' of concepts Claude already knows, but the redundant repetition and conversational filler go beyond the score-4 anchor's 'minor instances of over-explanation'.

3 / 5

Actionability

The guidance is copy-paste ready throughout: exact subagent task prompts, exact commands ('python -m scripts.aggregate_benchmark <workspace>/iteration-N --skill-name <name>', the full run_loop invocation with flags), concrete JSON templates for evals.json/eval_metadata.json/timing.json/feedback.json, and precise field-name requirements ('text', 'passed', 'evidence'). This matches the score-5 anchor (fully executable, covers common cases); the score-4 anchor's 'minor gaps' does not apply.

5 / 5

Workflow Clarity

The eval workflow is a clearly numbered 5-step sequence with checkpoints (grade → aggregate → analyst pass → viewer → user feedback) and an explicit improvement loop with stop criteria ('The user says they're happy', 'feedback is all empty'). It falls short of the score-5 anchor because key steps depend on files absent from the bundle ('agents/grader.md', 'eval-viewer/generate_review.py'), leaving a gap in executing the validate/grade feedback loop as written.

4 / 5

Progressive Disclosure

Structure is present — references are signaled with when-to-read guidance ('See references/schemas.md for the full schema', 'Read agents/grader.md...') and are one level deep — but the body cites five files that do not exist in the bundle (agents/grader.md, agents/comparator.md, agents/analyzer.md, agents/openai.yaml, eval-viewer/generate_review.py), so navigation breaks at exactly the points the workflow depends on. Additionally, the ~535-line body exceeds the skill's own <500-line guidance with the long Description Optimization section inlined, and references/schemas.md (431 lines) lacks the table of contents the skill itself prescribes for >300-line references. This sits between the score-3 and score-4 anchors: better organized than score 3, but the broken references are more than the 'minor organization gaps' of score 4.

3 / 5

Total

15

/

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 description that comprehensively covers what the skill does and when to use it, with an explicit 'Use when' clause and concrete capability verbs. The only gap is modest synonym coverage of casual trigger phrasings like 'build' or 'make a skill'.

Suggestions

Add natural synonyms for skill creation such as 'build', 'make', or 'set up a skill' to the 'Use when' clause to broaden casual-phrase trigger coverage.

Consider mentioning who the skill is for (e.g., skill authors) to further sharpen distinctiveness against general coding-assistant requests.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Create new skills, modify and improve existing skills, and measure skill performance', 'run evals to test a skill, benchmark skill performance with variance analysis', and 'optimize a skill's description for better triggering accuracy' — giving comprehensive coverage of the skill's capabilities. It matches the score-5 anchor (multiple specific concrete actions, comprehensive) and exceeds the score-4 anchor, which allows minor gaps in coverage.

5 / 5

Completeness

It explicitly answers both questions: 'what' (create/modify/improve/measure skills, run evals, benchmark, optimize descriptions) and 'when' via an explicit 'Use when users want to...' clause enumerating concrete triggering scenarios. This mirrors the score-5 anchor example's structure; the score-4 anchor's caveat ('when' could be more explicit) does not apply since the when-clause lists five distinct trigger scenarios.

5 / 5

Trigger Term Quality

Trigger phrases like 'create a skill from scratch', 'edit, or optimize an existing skill', 'run evals', and 'benchmark skill performance' are natural things users would say, giving good keyword coverage. A few natural variants are missing (e.g., 'build a skill', 'make a skill', 'improve my skill'), keeping it just below the score-5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The skill-creation niche is clear and its triggers (creating, editing, evaluating, benchmarking, or optimizing other skills) are distinct from any domain skill, minimizing wrong-skill triggering. Even adjacent meta-requests like 'write better docs' would not match these triggers, fitting the score-5 anchor (clear niche with distinct triggers, minimal conflict risk).

5 / 5

Total

19

/

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

skill_md_line_count

SKILL.md is long (541 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

openakita/openakita

Path

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.