CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-optimizer

Self-evolving skill optimization via SkillOpt-paper-grounded text-space optimizer.

50

Quality

55%

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 ./skills/skill-optimizer/SKILL.md
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.

The body is a strong operational document: fully specified commands, an explicit pipeline with mandatory validation gates and feedback loops, and honest anti-patterns. Its weaknesses are repetition of the bundled-mutation safety rules across four sections and a monolithic single-file layout with no reference files despite ~190 lines of detail. Both are fixable without losing substance.

DimensionReasoningScore

Conciseness

The body is dense and almost free of explanation of concepts Claude already knows, but it is noticeably repetitive: the bundled-skill mutation rules ('--allow-mutate-bundled' AND '--held-out' >= 5 tasks) are restated in the Iron Law, 'Where your skills live', the decision tree, and Anti-Patterns, and the '--split 1:1:1' / d_sel_too_small point appears twice. Matches anchor 3 ('mostly efficient but could be tightened'); not 4 because four restatements of one rule is more than a minor trim.

3 / 5

Actionability

Nearly everything is copy-paste ready: exact commands with flags ('gbrain skillopt X --bootstrap-from-skill', '--split 1:1:1'), exit codes, the benchmark JSONL line shape, and the rule-check vocabulary. Matches anchor 4 ('mostly executable guidance; concrete code or commands with minor gaps'); not 5 because the load-bearing 'review AND STRENGTHEN the judges' step gives vocabulary but no worked before/after example of a weak check upgraded to a strong one.

4 / 5

Workflow Clarity

The multi-step pipeline is explicit and validation-saturated: pre-flight gates, mandatory median-of-3 + epsilon=0.05 gating, hard refusals (exit 2, d_sel_too_small), a numbered 4-step bootstrap walkthrough, resume-on-crash, and a rejected-edits LRU. Matches anchor 5 ('clear sequence with explicit validation steps; feedback loops for error recovery') — the destructive/batch cap does not apply since validation gating is the skill's core.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the skill ships no bundle files and the ~190-line body inlines content that could live in one-level-deep references (the runSkillOpt contract schema, the benchmark line shape and rule-check vocabulary), with only a single external tutorial link. Matches anchor 3 ('some structure; content that should be separate is inline'); not 4 because there is no bundle structure at all and detail is not split out.

3 / 5

Total

15

/

20

Passed

Description

41%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.

The description names a distinctive niche but communicates it in paper-grounded jargon rather than concrete, user-legible capabilities, and it omits any 'Use when...' trigger guidance. Trigger-term coverage is thin: only 'skill optimization' is a phrase a user would plausibly say. Rewriting it to state 2-3 concrete actions plus explicit trigger phrases would move most dimensions up a full level.

Suggestions

State 2-3 concrete capabilities in third person instead of jargon, e.g. 'Improves an existing skill's execution quality by iteratively rewriting its SKILL.md body against a benchmark, with validation-gated, cost-capped runs.'

Add an explicit 'Use when...' clause covering the natural trigger phrases users would say: 'Use when the user wants to optimize, tune, or benchmark an existing skill, or bootstrap a benchmark for one.'

Replace paper-grounded jargon ('SkillOpt-paper-grounded text-space optimizer') in the routing-facing description with plain capability terms; the arXiv citation can live in the body where it already appears.

DimensionReasoningScore

Specificity

The description names the domain ('Self-evolving skill optimization') but its actions are abstract jargon — 'SkillOpt-paper-grounded text-space optimizer' — with no concrete capability stated (e.g. that it rewrites SKILL.md bodies against a benchmark). Matches anchor 2 ('names the domain but actions are minimal or generic'); not 3 because no user-legible concrete action like 'Processes PDF files and extracts content' is given.

2 / 5

Completeness

A domain-level 'what' is stated ('Self-evolving skill optimization'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is stated rather than entirely vague; not 4 because 'when' is wholly absent from the description.

3 / 5

Trigger Term Quality

Only 'skill optimization' resembles a phrase a user would naturally say; 'SkillOpt-paper-grounded' and 'text-space optimizer' are technical jargon users would not utter. Matches anchor 2 ('one or two generic keywords; missing the natural phrases users say'); not 3 because common variations like 'make the skill better', 'tune the skill', or 'benchmark' never appear in the description.

2 / 5

Distinctiveness Conflict Risk

'SkillOpt' / 'skill optimization' carves a clear niche with minor overlap risk only against closely related skills (e.g. skill scaffolding or generic skill editing). Matches anchor 4 ('mostly distinct; minor overlap risk'); not 5 because the description supplies no distinct concrete triggers, leaving it modestly confusable with generic 'improve your skills' guidance.

4 / 5

Total

11

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
garrytan/gbrain
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.