CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

collapse-pass

Find and carry through worthwhile code simplifications across recent edits, named files, or a subsystem. Use when asked for a collapse pass, a refactoring pass, another simplification pass, "simplify this", to clean up code, or to hunt for indirection and dead abstractions. Specific transformations, planning requests, review-only requests, and explicit file limits determine the work. Use control-flow for a request limited to one function's branching.

Quality

90%

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

86%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 exceptionally dense, actionable process guide with verified one-level-deep references and explicit verification/error-recovery checkpoints. Its weaknesses are modest: some repetition of authorization and scope rules across sections, and validation guidance that names but does not specify how to choose the checks to run.

Suggestions

Consolidate the authorization/scope rules (currently spread across 'Start and expand the hunt', 'Judge candidates', 'Carry each finding through', and 'Protect load-bearing information') into one section to remove repetition and trim tokens.

Make the pass-level workflow sequence explicit (e.g., a brief ordered summary of the hunt → judge → carry → verify → finish phases near the top) so the reader does not have to synthesize the order from six prose sections.

Sharpen the validation checkpoint: instead of "run checks appropriate to the affected behavior", give a short heuristic for selecting checks (e.g., typecheck plus the tests covering the traced callers) so the key verification step is concrete.

DimensionReasoningScore

Conciseness

The body is dense and operational with no filler and no explanations of concepts Claude already knows, but authorization/scope rules recur across sections ("Respect instructions such as 'only these files'", "Changes beyond existing authorization remain proposals", "Existing authorization may already settle the decision"), which is minor trimmable repetition. It is above anchor 3 because nothing is padded or over-explained, but short of anchor 5's 'every token earns its place'.

4 / 5

Actionability

For an instruction-only process skill the guidance is fully executable: copy-paste-ready literal search lists ("search literally for `registry`, `Map`, `Set`, `index`, `flag`, `cache`, `pending`, and `retry`"; "`fallback`, `adapter`, `legacy`, `migration`, and `compatibility`"), concrete candidate patterns (forwarding layers, re-export chains, shadow state, dead exports), and explicit keep/remove decision rules cover the common cases.

5 / 5

Workflow Clarity

The sections form a clear phased sequence (start/expand the hunt, judge candidates, carry each finding through, protect load-bearing information, finish) with explicit checkpoints and error recovery ("Finish with post-implementation-review", "Resolve regressions introduced by the pass before proceeding", "undo only that edit"). It falls short of anchor 5 because "run checks appropriate to the affected behavior" leaves which checks to run unspecified, and the sequence must be synthesized from prose rather than an explicit ordered procedure.

4 / 5

Progressive Disclosure

The body is a process overview with well-signaled, one-level-deep references, each linked at its point of use with a stated purpose ("Read the relevant [refactoring methods](references/refactoring-methods.md) for caller evidence, safe inlining...", concept-inventory, library-refusal, durable-contracts, report-format), and all five referenced files exist in references/. The 18KB refactoring-methods detail is appropriately split out of the overview, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Description

91%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 description: it states a concrete capability, gives an explicit and richly quoted 'Use when' trigger clause covering natural synonyms, and delineates request modes that shape the work. The only weaknesses are slightly abstract action phrasing and minor overlap with generic refactoring/cleanup skills.

DimensionReasoningScore

Specificity

"Find and carry through worthwhile code simplifications" and "hunt for indirection and dead abstractions" name several concrete actions with explicit scopes ("recent edits, named files, or a subsystem"), plus distinct request modes (planning, review-only, specific transformations). It falls short of anchor 5 because the actions remain more abstract than a crisply enumerable operation list, and above anchor 3 because multiple specific behaviors are stated.

4 / 5

Completeness

The first sentence explicitly states what the skill does, and "Use when asked for..." explicitly states when with concrete trigger phrases, matching the anchor-5 example structure. It is not anchor 4 because the 'when' clause is already fully explicit and specific rather than needing more precision.

5 / 5

Trigger Term Quality

The trigger clause quotes natural user phrasings verbatim and covers the domain's synonyms: "a collapse pass, a refactoring pass, another simplification pass, \"simplify this\", to clean up code, or to hunt for indirection and dead abstractions". This is comprehensive natural-term coverage (file extensions are inapplicable here), exceeding anchor 4's "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (simplification/collapse passes) with distinct triggers, and even routes a neighboring case away ("Use control-flow for a request limited to one function's branching"). Minor overlap risk remains with generic refactoring or code-cleanup skills via "a refactoring pass" and "to clean up code", fitting anchor 4 rather than anchor 5's minimal-conflict profile.

4 / 5

Total

18

/

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

relative_links

Relative link issues: 10 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/collapse-pass/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.