CtrlK
BlogDocsLog inGet started
Tessl Logo

cleanup

Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, and comments — analyzing in parallel, then applying fixes sequentially

68

Quality

83%

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

100%

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 tightly written, fully actionable orchestration workflow with clear sequencing and validation checkpoints, well-organized into labeled sections without unnecessary bundle references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never lectures on basics Claude already knows, and its explanatory prose (dependency ordering, snapshot-relative proposals) is non-obvious orchestration logic that earns its tokens.

3 / 3

Actionability

It gives fully executable, copy-paste-ready guidance: the eight exact `/skill <scope> fix=false` invocations, a numbered dependency order, a content-anchored apply procedure, and the concrete `bun run lint:check` command.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with explicit validation checkpoints — the re-read/locate-by-content reconciliation loop in Step 3 and the post-edit `bun run lint:check` run provide the feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

No bundle files exist, and this self-contained ~50-line skill is organized into clear labeled sections (Steps 1–4 plus Boundary Audit Guidance) with no nested references, which earns a 3 under the simple-skills scoring note.

3 / 3

Total

12

/

12

Passed

Description

67%

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 is specific and distinctive, enumerating the eight sub-skills and the parallel-then-sequential execution model, but it lacks any 'Use when...' trigger guidance and relies on technical skill names over natural user phrasing.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants a full code-quality cleanup pass across recent changes, a PR, a directory, or the whole codebase.'

Replace some technical skill-name jargon with natural user phrasing (e.g. 'review my code', 'clean up unused effects/memos/state') so the trigger terms match what a user would actually say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions/skills by name — 'effects, memo, callbacks, state, React Query, emcn design review, url-state, and comments — analyzing in parallel, then applying fixes sequentially' — matching the anchor that lists several specific concrete actions.

3 / 3

Completeness

It clearly states what the skill does (run all code quality skills in parallel then apply fixes sequentially) but never states when Claude should use it; the missing 'Use when...' clause caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

It surfaces some relevant keywords ('code quality', 'React Query', 'effects') but leans on technical skill names rather than natural phrases a user would say, with no 'Use when...' phrasing or common variations like 'clean up my code'.

2 / 3

Distinctiveness Conflict Risk

The enumerated list of eight named sub-skills plus the explicit 'run all ... in parallel, then apply fixes sequentially' framing carves a distinct meta-orchestrator niche unlikely to be confused with any single sub-skill.

3 / 3

Total

10

/

12

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
simstudioai/sim
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.