CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

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

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.

A thorough, well-sequenced skill with excellent workflow structure and concrete executable guidance, undermined by conversational padding and a bundle that is missing every referenced file the body tells Claude to read or run. Tightening the prose and shipping the referenced resources would lift it significantly.

Suggestions

Trim conversational padding ("Cool? Cool.", the plumbers/grandparents tangent, the all-caps Cowork apology, "billions a year in economic value", the repeated core-loop emphasis) — these add tokens without instructional value and push the body near its own 500-line limit.

Move the lengthy Claude.ai-specific, Cowork-specific, and Description Optimization sections into reference files so SKILL.md stays a lean overview that points to detail, matching the progressive-disclosure pattern the skill itself advocates.

Bundle the referenced resources the body depends on (scripts/aggregate_benchmark.py, scripts/run_loop.py, scripts/package_skill.py, eval-viewer/generate_review.py, agents/{grader,comparator,analyzer}.md, references/schemas.md, assets/eval_review.html) — right now every "Read X" / "run X" instruction points at a file that does not exist.

DimensionReasoningScore

Conciseness

Mostly purposeful instructional content, but noticeably padded with conversational asides ("Cool? Cool.", the plumbers/grandparents tangent, an all-caps apology paragraph, "billions a year in economic value", a repeated core-loop emphasis block) that could be trimmed without loss.

3 / 5

Actionability

Provides concrete, copy-pasteable commands (python -m scripts.aggregate_benchmark, run_loop invocations, nohup generate_review.py) and full JSON templates for evals/grading/timing/feedback, but several referenced scripts are not bundled so the guidance cannot be fully executed as written.

4 / 5

Workflow Clarity

Clearly sequenced multi-step workflow (Capture Intent → Write SKILL.md → Steps 1–5 for running/evaluating → iteration loop) with explicit validation (grading.json assertions, analyst pass) and a feedback loop (feedback.json → improve → repeat) for error recovery.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep ("Read agents/grader.md", "See references/schemas.md"), but the ~460-line body inlines lengthy environment-specific and description-optimization sections that could be split out, and none of the referenced bundle files (scripts/, eval-viewer/, agents/, references/, assets/) actually exist in the bundle.

4 / 5

Total

16

/

20

Passed

Description

100%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, well-formed description: third-person voice, explicit "Use when" trigger guidance, multiple concrete actions, and a distinct niche. It reads naturally and would trigger reliably for the intended audience without over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Create new skills, modify and improve existing skills, and measure skill performance" plus run evals, benchmark with variance analysis, and optimize a description — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ("Create new skills, modify and improve existing skills, and measure skill performance") and when via a concrete "Use when users want to..." clause enumerating trigger contexts.

5 / 5

Trigger Term Quality

Natural trigger phrases with synonym coverage ("create a skill from scratch", "edit", "optimize an existing skill", "run evals", "benchmark skill performance", "triggering accuracy") that users would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a distinct meta-niche (creating/optimizing skills themselves) with triggers unlikely to collide with other skills, so conflict risk is minimal.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
digoal/blog
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.