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

81%

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

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.

The body delivers an unusually clear, well-sequenced iterative workflow with concrete commands, templates, and validation/feedback checkpoints. Its weaknesses are significant conversational padding and repetition (~505 lines where its own guidance says <500), and four referenced files (agents/*.md, eval-viewer/generate_review.py) that are missing from the bundle, which breaks navigation at the skill's most-emphasized steps.

Suggestions

Remove conversational filler and repetition — the "Cool? Cool." asides, the jargon-familiarity riff about plumbers/grandparents, the "billions a year in economic value" line, and the end-of-file restatement of the core loop — which would reclaim a large share of the 505-line body without losing any actionable guidance.

Fix the dangling references: bundle `agents/grader.md`, `agents/comparator.md`, `agents/analyzer.md`, and `eval-viewer/generate_review.py`, or repoint the instructions at files that actually ship in scripts/ (e.g., generate_report.py), since the grader and viewer steps reference them repeatedly and currently dead-end.

Move the claude.ai-specific, Cowork-specific, and Description Optimization sections into references/ files with one-line pointers, both to get under the 500-line budget the skill itself prescribes and to keep the main body a lean overview of the core create→test→review→improve loop.

DimensionReasoningScore

Conciseness

The ~505-line body contains several padded, conversational sections that earn no tokens: "Cool? Cool.", the riff about plumbers and grandparents googling "how to install npm", "we are trying to create billions a year in economic value here!", "Sorry in advance but I'm gonna go all caps here", and a full restatement of the core loop at the end ("Repeating one more time the core loop here for emphasis"). It is above the 1 anchor because the verbosity is mostly conversational padding and repetition of its own original workflow content rather than explaining concepts Claude already knows, but well below the 3 anchor since multiple sections could simply be deleted with no loss of guidance.

2 / 5

Actionability

The guidance is highly concrete: exact subagent prompt templates, JSON structures for eval_metadata.json/timing.json/feedback.json, exact commands (`python -m scripts.aggregate_benchmark <workspace>/iteration-N --skill-name <name>`, the nohup generate_review.py invocation, `python -m scripts.run_loop`), and a labeled bad-vs-good example for eval queries. It falls short of fully copy-paste-ready (5) because the most-repeated command, `eval-viewer/generate_review.py`, does not exist in the bundled scripts/ directory, and the grader flow points to `agents/grader.md`, which is also missing — a user following the central review step literally hits a gap.

4 / 5

Workflow Clarity

The multi-step process is explicitly sequenced with validation checkpoints throughout: a 5-step eval procedure with numbered steps ("This section is one continuous sequence — don't stop partway through"), immediate timing capture ("Process each notification as it arrives"), assertion grading before aggregation, an analyst pass, a user-review gate ("When you're done, come back here and let me know"), and an explicit iterate-until-done loop with stopping conditions ("The user says they're happy / The feedback is all empty / You're not making meaningful progress"). This matches the 5 anchor: clear sequence, explicit validation steps, and feedback loops for error recovery.

5 / 5

Progressive Disclosure

Structure is genuinely present — a dedicated "Reference files" section, pointers like "See `references/schemas.md` for the full schema", and domain-organized scripts invoked via `python -m` — but scored against the actual bundle it has real navigation failures: `agents/grader.md`, `agents/comparator.md`, `agents/analyzer.md`, and `eval-viewer/generate_review.py` are referenced from the body but absent from the bundle (verified against the file listing; only references/schemas.md, assets/eval_review.html, and the scripts/ package exist). Additionally the body itself runs ~505 lines, past the <500-line budget the skill prescribes, with sizable platform-variant sections (claude.ai-specific, Cowork-specific, Description Optimization) that its own guidance would put in reference files. It is not a 4 because dangling references that break at read time are more than "minor organization gaps", but not a 2 because the references that do exist are clearly signaled and one level deep.

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 description in third-person voice that clearly states what the skill does and when to use it, with concrete, natural trigger phrasing. The only weakness is modest synonym coverage (e.g., "build"/"write"/"update a skill").

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Create new skills, modify and improve existing skills, and measure skill performance", plus "run evals", "benchmark skill performance with variance analysis", and "optimize a skill's description for better triggering accuracy" — which comprehensively covers the skill's domain. It sits at the 5 anchor rather than 4 because the action list is broad and specific (creation, editing, evaluation, benchmarking, description tuning) rather than leaving coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" ("Create new skills, modify and improve existing skills, and measure skill performance") and the "when" ("Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill..."). This matches the 5 anchor exactly — clear what and when with concrete trigger phrases — so no cap applies.

5 / 5

Trigger Term Quality

Phrases like "create a skill from scratch", "edit, or optimize an existing skill", "run evals", and "benchmark skill performance" are natural things a user needing this skill would say. It falls short of the 5 anchor because common phrasings such as "build", "make", "write", or "update a skill" are absent, so a few natural synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The skill-authoring niche is clearly carved out and every trigger is anchored to the word "skill" ("a skill from scratch", "run evals to test a skill", "a skill's description"), giving it distinct triggers with minimal conflict risk against other skills. It is not a 4 because the triggering language consistently scopes to skill creation/improvement rather than overlapping with generic eval or file tools.

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 (511 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

coinbase/cds

Path

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