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

82%

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

70%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, highly actionable meta-workflow whose main weaknesses are verbosity (conversational padding, duplicated core-loop recap, overlapping environment-specific sections, 613 lines vs. its own 500-line limit) and bundle hygiene (four referenced paths — three agents/*.md files and the eval-viewer script — are missing, and the 439-line schemas.md lacks the table of contents the skill itself prescribes). The workflow logic itself, including validation and feedback loops, is excellent.

Suggestions

Add the missing referenced files (agents/grader.md, agents/comparator.md, agents/analyzer.md, eval-viewer/generate_review.py) or repoint those references to files that actually exist in the bundle (e.g., scripts/generate_report.py) so the grading and viewer steps are executable as written.

Cut conversational padding and redundancy — remove the closing "Repeating one more time the core loop" recap (it duplicates the opening overview), trim asides like the "just vibe with me" flexibility note, and merge the overlapping Claude.ai and Cowork sections — to bring the body under the 500-line limit the skill itself sets.

Add a table of contents to references/schemas.md (439 lines), matching the skill's own rule that reference files over 300 lines include one.

DimensionReasoningScore

Conciseness

Mostly efficient — the core instructions (host.skills API, eval workflow, kernel plugin rules) are dense and non-obvious — but there is real padding that could be trimmed: conversational asides like "if the user is like 'I don't need to run a bunch of evaluations, just vibe with me'", "This task is pretty important... take your time and really mull things over", "Repeating one more time the core loop here for emphasis" (the loop is stated twice), and the substantially overlapping Claude.ai and Cowork sections. It does not reach level 2 because there is no explanation of concepts Claude already knows, and most sections earn their tokens.

3 / 5

Actionability

The body is largely copy-paste executable: exact host.skills API calls, JSON templates for evals.json/eval_metadata.json/timing.json, ready-to-spawn subagent prompts, and exact bash commands ("python -m scripts.aggregate_benchmark <workspace>/iteration-N --skill-name <name>", the run_loop invocation with all flags). It falls short of level 5 because some concrete commands point at paths that don't resolve in the bundle ("eval-viewer/generate_review.py", "agents/grader.md"), leaving minor gaps a user would hit at execution time.

4 / 5

Workflow Clarity

The multi-step process is explicitly sequenced (Capture Intent → Interview → Write SKILL.md → Test Cases → Steps 1–5 of running/evaluating → feedback → improve → iterate) with genuine validation checkpoints and feedback loops: draft expectations while runs are in progress, grade against expectations, an analyst pass, user review via the viewer, and explicit termination criteria ("Keep going until: The user says they're happy / The feedback is all empty / You're not making meaningful progress"). This matches the level-5 anchor including error-recovery guidance (e.g., sidecar gate rejects surfacing immediately for iteration).

5 / 5

Progressive Disclosure

Structure exists — a dedicated "Reference files" section, one-level-deep references, and clearly signaled pointers like "See `references/schemas.md` for the full schema" — but scored against the actual bundle it has real problems: `agents/grader.md`, `agents/comparator.md`, `agents/analyzer.md`, and `eval-viewer/generate_review.py` are referenced repeatedly yet do not exist in the bundle; the body runs 613 lines, violating its own "Keep SKILL.md under 500 lines" rule; and references/schemas.md (439 lines) has no table of contents despite the skill's own guidance for files over 300 lines. This is between anchors 3 and 4, but the broken reference paths push it to 3 rather than 4.

3 / 5

Total

15

/

20

Passed

Description

88%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 explicitly states both capabilities and trigger conditions in third-person voice, with concrete trigger phrasings that mirror what users would naturally type. The only gap is modest synonym coverage (e.g., "build/make a skill") and slight overlap risk with generic eval/benchmarking skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete, comprehensive actions for the skill-creation domain: "Create new skills, modify and improve existing skills, and measure skill performance", including specialized operations like "benchmark skill performance with variance analysis" and "optimize a skill's description for better triggering accuracy". Coverage spans the full workflow (create, edit, optimize, test, benchmark) with no gaps, matching the level-5 anchor; it is not a level-4 case because there is no missing capability area.

5 / 5

Completeness

Both questions are answered explicitly: the "what" ("Create new skills, modify and improve existing skills, and measure skill performance") and the "when" with concrete trigger phrases ("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..."). This matches the level-5 anchor exactly; a missing or implicit when-clause would cap it at 3, which is not the case.

5 / 5

Trigger Term Quality

The trigger clause covers good natural phrasing users would actually say: "create a skill from scratch", "edit, or optimize an existing skill", "run evals to test a skill", "benchmark skill performance". It falls short of the level-5 anchor because common synonyms like "build a skill", "make a skill", or "iterate on a skill" are absent, but it is well above level 3 since multiple phrasings and casual variants of the intent are present.

4 / 5

Distinctiveness Conflict Risk

The skill-creation/optimization niche is clear and mostly distinct — few skills would compete for "create a skill from scratch" or "optimize a skill's description for better triggering accuracy". It is not level 5 because phrases like "run evals" and "benchmark skill performance with variance analysis" could overlap with general testing/evaluation skills, but the overlap risk is minor, matching the level-4 anchor.

4 / 5

Total

18

/

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

Warning

Total

15

/

16

Passed

Repository

UnicomAI/wanwu

Path

configs/microservice/bff-service/configs/agent-skills/claude-science/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.