CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator

Create, edit, evaluate, and optimize skills, including benchmarking and description tuning for better triggering.

Quality

70%

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

Quality

Content

62%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 richly actionable, well-sequenced workflow document with excellent templates, commands, and feedback loops. Its weaknesses are stylistic padding that inflates token cost, a body at/over its own length guidance, and references to bundled files (agents/*.md, eval-viewer/generate_review.py) that are missing from the actual bundle.

Suggestions

Trim the chatty asides ("Cool? Cool.", the plumber/grandparent digression, "billions a year in economic value", the all-caps apology) and drop the verbatim closing recap of the core loop — the numbered workflow already conveys it.

Consolidate the environment-specific sections (Cherry Studio, Claude.ai, Cowork) and the Description Optimization detail into reference files (e.g. references/environments.md, references/trigger-optimization.md) linked from the body, bringing the body well under 500 lines.

Either ship the referenced files (agents/grader.md, agents/comparator.md, agents/analyzer.md, eval-viewer/generate_review.py) in the bundle or inline/remove the instructions that depend on them, so no referenced path is a dead end.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with padded asides ("Cool? Cool.", the plumbers/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"), repeats the core loop verbatim in a closing recap, and carries three overlapping environment-specific sections (Claude.ai, Cowork, Cherry Studio). This matches anchor 2 ('several unnecessary explanations or padded sections') rather than anchor 1, since it never explains concepts Claude already knows — the padding is stylistic, not tutorial.

2 / 5

Actionability

Guidance is mostly copy-paste ready: exact subagent prompt templates, exact JSON structures for eval_metadata.json/timing.json/feedback.json, and exact commands ("python -m scripts.aggregate_benchmark <workspace>/iteration-N --skill-name <name>", the nohup generate_review.py invocation, the run_loop command). It falls short of anchor 5 because several referenced executable resources — agents/grader.md, agents/comparator.md, agents/analyzer.md, and eval-viewer/generate_review.py — are absent from the bundle, so a reader following the instructions hits missing files.

4 / 5

Workflow Clarity

The eval loop is sequenced as explicit numbered Steps 1–5 (spawn runs, draft assertions in parallel, capture timing per notification, grade/aggregate/analyze/launch viewer, read feedback) with explicit validation checkpoints (assertion grading, analyst pass, benchmark deltas), a feedback loop (feedback.json → improve → rerun into iteration-N+1), and explicit stopping criteria ("user says happy / feedback all empty / not making meaningful progress"). This matches anchor 5 ('clear sequence with explicit validation steps; feedback loops'), and there are no destructive or batch operations that would cap it.

5 / 5

Progressive Disclosure

References are clearly signaled (a dedicated "Reference files" section with when-to-read guidance, schemas offloaded to references/schemas.md, scripts invoked with exact commands), but four referenced paths (agents/grader.md, agents/comparator.md, agents/analyzer.md, eval-viewer/generate_review.py) do not exist in the actual bundle, and the ~512-line body exceeds its own stated 500-line guidance with inlinable content (description-optimization detail, viewer UX walkthrough, per-environment sections). Anchor 3 ('content that should be separate is inline') fits better than anchor 4, whose 'minor organization gaps' a bundle with dangling references does not meet.

3 / 5

Total

14

/

20

Passed

Description

66%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, moderately specific description that names the skill's main functions in one compact sentence. Its main weakness is the complete absence of 'when to use' trigger guidance, which caps completeness and limits natural-phrase coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to create, build, or improve a skill, turn a workflow into a skill, write or edit SKILL.md files, or optimize skill descriptions/triggering."

Include natural user phrasings as trigger terms ("make a skill", "build a skill", "improve this skill", "turn this into a skill", "skill isn't triggering") so queries match without keyword guessing.

Mention the bundling/packaging capability (e.g. ".skill packaging") to round out coverage of what the skill does.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Create, edit, evaluate, and optimize skills, including benchmarking and description tuning for better triggering") including two named sub-activities (benchmarking, description tuning). It falls short of anchor 5 because coverage has gaps — packaging, test-case drafting, and interviewing are unmentioned, and "evaluate"/"optimize" remain abstract — but it clearly exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is clear (create, edit, evaluate, optimize skills with benchmarking and description tuning), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which the judging guidelines state caps completeness at 3. It matches anchor 3 ('clear what but when is missing') exactly, and cannot be anchor 4 without a when-clause.

3 / 5

Trigger Term Quality

Terms like "create", "edit", "evaluate", "optimize", "benchmarking", and "triggering" give good keyword coverage for the domain, but common natural variations users would actually say are missing ("make/build a skill", "improve a skill", "turn this into a skill", "SKILL.md"). This fits anchor 4 ('good keyword coverage; a few natural terms missing') better than anchor 3, which requires only 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Skill-creation tooling is a distinct niche, and the description stays on-domain ("...and optimize skills, including benchmarking and description tuning for better triggering"). Minor overlap risk remains with generic evaluation/benchmarking or prompt-engineering skills since "evaluate" and "benchmarking" appear without qualifiers, so anchor 4 fits better than anchor 5's 'minimal conflict risk'.

4 / 5

Total

15

/

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

skill_md_line_count

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

CherryHQ/cherry-studio

Path

resources/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.