CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

optimize-approach

Judges whether a change or plan takes the best approach for its intent (codebase-fit, simplicity, performance, robustness) and proposes at most two materially better ones; says nothing when the approach is already sound. Slash-invoked: "/optimize-approach [<files>|<plan path>]".

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean advisory skill: token-efficient, fully executable, with a clearly sequenced workflow and built-in verification gates. Its single real defect is bundle-level — the referenced lens.md is missing entirely, so the one progressive-disclosure promise the skill makes cannot be fulfilled.

Suggestions

Ship the referenced `lens.md` in the bundle or delete the "Lens-eligible for the `pr-reviewer` agent" line — the file does not exist next to SKILL.md, so the claimed auto-load on deep reviews cannot happen.

If per-axis detection heuristics or additional worked examples are added later, place them one level deep in a clearly signaled reference file rather than growing SKILL.md, keeping the current overview-first shape.

DimensionReasoningScore

Conciseness

Every section earns its place: the axis table ("a hand-rolled helper duplicating an export; a bespoke pattern next to a shared one"), the drop rules, the three-part materiality bar, and the output template all carry judgment criteria Claude does not already know. There is no concept tutorial, no library primer, no padded prose — the closing line "silence on a sound approach costs nothing; a weak 'better way' costs trust" encodes the core decision rule rather than over-explaining, so this is anchor 5, not anchor 4's "minor instances of over-explanation".

5 / 5

Actionability

Fully executable for a report-only skill: the exact diff command ("git diff <base>...HEAD, base default origin/main"), a copy-paste output template with per-field slots ("**Now:** <the current approach, one line, with file:line>"), the exact terminal string ("print exactly `Approach: optimal — no materially better approach found.`"), and a worked ✓/✗ pair grounded in file:line. This matches anchor 5's "copy-paste ready… specific examples cover the common cases"; the scoring note for instruction-only skills confirms no code absence penalty applies.

5 / 5

Workflow Clarity

Steps 0–3 are numbered and unambiguous (scope → score four axes → drop what another lens owns → materiality bar → output), with explicit verification gates built in: "grep before you claim one exists" and "stated in two sentences with file:line evidence you read, not a guess". The materiality bar ("Material / Grounded / Worth the switch") is a pre-output checklist and the exact optimal-string removes terminal-state ambiguity — matching anchor 5. The destructive/batch validation cap does not apply since the skill is "Report only; never edit files".

5 / 5

Progressive Disclosure

The inline structure is strong (clear headed sections, ~64 well-organized lines, nothing that should be split out), but the skill's only external reference — "Lens-eligible for the `pr-reviewer` agent: [`lens.md`](./lens.md) auto-loads on `deep` reviews" — points to a file that does not exist in the bundle (no lens.md, and no references/, scripts/, or assets/ directories), so the advertised navigation and deep-review integration are broken. Structure alone reads as anchor 5 and the dangling link as a clear defect, landing between anchors; the false reference is more than anchor 4's "minor organization gaps", so 3.

3 / 5

Total

18

/

20

Passed

Description

67%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 clearly and concretely states what the skill does, differentiates it from generic review helpers, and gives explicit slash-invocation guidance. Its weaknesses are thin natural-language trigger coverage (missing the everyday phrasings users would say) and the absence of situational 'use when' conditions beyond the invocation syntax.

Suggestions

Add an explicit 'Use when…' clause naming the situations that call for it, e.g. "Use when reviewing a diff or plan and the question is whether the approach — not the lines — is right."

Include the natural phrases users actually say — "better way", "is this the right approach", "simpler", "reuse" — alongside the axis names to broaden trigger coverage.

State the boundary with sibling skills in the description (mechanical tidy → /polish, failure modes → /critical) to further reduce overlap with general code-review skills.

DimensionReasoningScore

Specificity

Quotes: "Judges whether a change or plan takes the best approach for its intent (codebase-fit, simplicity, performance, robustness)", "proposes at most two materially better ones", "says nothing when the approach is already sound" — three concrete actions plus four named axes. Not anchor 5 because the actions are stated at a meta level ("judges", "proposes") rather than as fully concrete operations like the anchor's "extract text, fill forms, merge documents"; clearly above anchor 3's "1-2 concrete actions".

4 / 5

Completeness

The 'what' is explicit and multi-part (judge on four axes, propose at most two better approaches, stay silent when sound). The 'when' is present as explicit trigger guidance — "Slash-invoked: \"/optimize-approach [<files>|<plan path>]\"" — which is the operative trigger for a disable-model-invocation skill, but it gives invocation syntax rather than situational conditions, so it cannot reach anchor 5's "concrete trigger phrases"; it sits at anchor 4 ("'when' could be more explicit or specific").

4 / 5

Trigger Term Quality

Natural terms present: "best approach", "change or plan", "simplicity", "performance", "robustness". Common variations a user would actually say are missing — "better way", "is there a simpler way", "reuse", "refactor", "cleaner" — matching anchor 3 ("some relevant keywords but missing common variations or synonyms") rather than anchor 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

The four-axis framing ("codebase-fit, simplicity, performance, robustness") plus the distinctive silence behavior ("says nothing when the approach is already sound") carve a clear niche apart from general review skills. Below anchor 5 because the description does not state its boundaries against closely related review/polish/critical skills — that separation lives only in the body — leaving minor overlap risk with generic code-review skills.

4 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/quality/optimize-approach/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.