CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

find-simplifications

Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every consumer is named before anything is deleted. Not for tidying a diff you just wrote (that is bundled `/simplify`) and not for defects (that is `/review`).

Quality

85%

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.

An exceptionally actionable, well-sequenced operational skill with strong validation loops and clean one-level-deep references. Its weakness is token efficiency: embedded war-story commentary and dated operational measurements make the body far longer than the guidance itself requires.

Suggestions

Move the extended incident commentary (tmpfs inode measurements, symlink-attack rationale) out of the bash comments in SKILL.md into references/survey.md, keeping only the operative lines and one-line reasons in the body.

Trim the territory table's paragraph-length cell justifications to the mechanism plus outcome, and delegate full evidence (script names, file copies) to the survey reference.

Place dated, time-sensitive measurements (e.g. "Measured 2026-11-12 on the host behind ecs-qwen-hz3-10/hz3-12") in a clearly marked operational-notes section in a reference file so the main body stays stable.

DimensionReasoningScore

Conciseness

The ~47KB body is noticeably verbose: multi-paragraph war-story commentary is embedded in bash comments (inode exhaustion "Measured 2026-11-12 on the host behind ecs-qwen-hz3-10/hz3-12", extended symlink-attack rationale), and the territory table packs paragraph-length justifications into cells. It avoids anchor 1 because none of it explains generic concepts Claude already knows — it is dense, repo-specific operational knowledge — but several sections are padded digressions that could be cut or moved, matching anchor 2.

2 / 5

Actionability

Guidance is fully executable: copy-paste bash blocks with fail-closed `exit 1` checks, exact `gh issue list --state all --search '"find-simplifications" ledger in:title'` commands with quoting rationale, a concrete decision table mapping situations to actions, and specific path-level territory rules. Specific examples cover the common cases.

5 / 5

Workflow Clarity

The multi-phase workflow (survey → ledger → maintainer assent → land one candidate) is clearly sequenced with explicit validation checkpoints: per-run grep calibration ("An empty survey caused by a broken search must never be reported as a clean run"), fail-closed ledger reads that stop the run, a clean-checkout guarantee, and stop-loss rules. For a deletion/batch skill, feedback loops are thorough — well above anchor 4.

5 / 5

Progressive Disclosure

The phase table up top clearly signals the two one-level-deep references (`references/survey.md`, `references/land.md`, both real files) with an explicit reading order. However, substantial survey-phase material — the full territory table and the rotation bash block with its commentary essays — is inlined in SKILL.md rather than pushed into references/survey.md, leaving minor organization gaps characteristic of anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

92%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 highly specific, well-bounded description that clearly states what the skill does, when to use it, and what it is not for. Trigger terms are natural and include explicit negative triggers; only a few common synonyms (dead code, unused exports) are absent.

DimensionReasoningScore

Specificity

Names multiple concrete actions and target surface types — "dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to" — with comprehensive coverage of what the skill does. It goes beyond anchor 4's "minor gaps in coverage" by enumerating both the findings workflow and the landing gate.

5 / 5

Completeness

Explicitly answers when ("Use for a periodic repo-wide sweep… Not for tidying a diff you just wrote… and not for defects") and what (sweep for excess surface, file candidates on a tracking issue, land only maintainer-approved items). Both halves are concrete and explicit, matching the anchor-5 example's structure; the when is stated, not merely implied as at anchor 4.

5 / 5

Trigger Term Quality

Natural phrases like "repo-wide sweep", "dead components", "orphaned locale keys", and "exports nothing consumes" are present, plus explicit negative triggers ("/simplify", "/review"). A few common user phrasings ("dead code", "unused exports", "cleanup") are missing, so it matches anchor 4's "good keyword coverage; a few natural terms missing" rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description draws explicit boundaries against the two most confusable skills ("that is bundled `/simplify`", "that is `/review`") and carves a clear niche — repo-wide accumulated surface, not a diff or a defect. Minimal conflict risk.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

15

/

16

Passed

Repository

QwenLM/qwen-code

Path

.qwen/skills/find-simplifications/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.