CtrlK
BlogDocsLog inGet started
Tessl Logo

collapse-pass

Run a continuous collapse-and-simplify pass that surgically removes indirection failing to earn its boundary. Use when the user says 'collapse pass', 'simplify pass', 'simplify this', 'reduce indirection', 'shrink the surface', 'find what to delete', when asking to audit a package for dead abstractions, when reviewing a pull request, branch, or recent merged change for simplification (isolated in a worktree), or when the goal is a sequence of small refactor commits that delete more than they add. When the target is the branching inside one function rather than a surface spanning files, use control-flow instead.

72

Quality

89%

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

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

A well-structured, dense instruction skill with a clearly sequenced ritual, explicit validation and revert feedback loops, and clean one-level-deep references that all resolve to real bundle files. It assumes Claude's competence and mostly avoids over-explanation.

DimensionReasoningScore

Conciseness

Dense and assumes competence (no explanations of indirection, worktrees, rg, or bun), with every section earning its place; the 'Pass parameters' and implementation-gate table are slightly verbose and could be trimmed.

4 / 5

Actionability

Provides concrete executable commands (rg, bun test, bun run typecheck, git worktree/fetch/diff) and a copy-paste finding-format template, though some ritual steps are procedural ('mentally inline') rather than literal code, matching an instruction skill.

4 / 5

Workflow Clarity

Clear 7-step ritual with explicit validation checkpoints (bun test, typecheck, re-grep straggler sweep), a feedback loop ('If none is true, the change was cosmetic. Revert'), and explicit stop conditions, satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

SKILL.md is an overview with six well-signaled, one-level-deep references ('Load on demand:' plus descriptive bullets), each prefacing its contents; all six referenced files exist in references/ and content is appropriately split.

5 / 5

Total

18

/

20

Passed

Description

95%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 states what the skill does and when to use it, with comprehensive natural trigger phrases and explicit boundary guidance that routes to a sibling skill. It is concise yet complete, avoiding buzzwords.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('removes indirection failing to earn its boundary', 'audit a package for dead abstractions', 'small refactor commits that delete more than they add'), with minor gaps since the actions lean conceptual rather than a fully enumerated list.

4 / 5

Completeness

Explicitly answers both 'what' (a continuous collapse-and-simplify pass that removes unearned indirection) and 'when' via a concrete 'Use when...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger phrases users would actually say ('collapse pass', 'simplify pass', 'simplify this', 'reduce indirection', 'shrink the surface', 'find what to delete') including synonyms and trigger contexts.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers, plus explicit boundary routing ('When the target is the branching inside one function... use control-flow instead') that actively steers away from a sibling skill, minimizing 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 suspicious

Warning

Total

15

/

16

Passed

Repository
EpicenterHQ/epicenter
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.