CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

asymmetric-wins

Evaluate whether refusing a small promise would eliminate disproportionate complexity. Use when judging asymmetric wins or a proposed refusal of fidelity, compatibility, fallbacks, modes, or duplicate paths; use product-collapse to develop simpler product workflows.

Quality

84%

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

81%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 evaluation skill with genuinely actionable procedure, templates, and a concrete worked example, plus well-signaled one-level-deep cross-references. Its main cost is redundancy: the load-bearing keep-it rule is repeated across nearly every section, and the two decision templates overlap heavily.

Suggestions

State the load-bearing/keep-it decision rule once (e.g., in the Procedure's step 6) and remove the repeated restatements in the opening sections and the post-procedure paragraph.

Differentiate or merge the Decision Template and UI Refactor Template, which share the product-sentence, deletion-prize, and decision fields verbatim — the UI variant only needs to add its 'Must preserve' / 'Can refuse' lists.

Move the UI Refactor Template, UI Artifact Ladder, and worked example into a reference file (e.g., references/ui-refusals.md) to shorten SKILL.md to its spine, procedure, and core template.

DimensionReasoningScore

Conciseness

The core decision rule is restated four-plus times: "keep it when the evidence says the loss is load-bearing", "still be worth keeping when the capability it provides is load-bearing", "If the loss is load-bearing, keep the feature", and "Keep the feature when the user loss is load-bearing" (plus the fidelity restatement at the end). The Decision Template and UI Refactor Template also share four fields verbatim. This is more than the minor trimmability of anchor 4 — genuine tightening is available — but there is no padding or explanation of concepts Claude already knows, so it stays above anchor 2.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a six-step procedure with concrete candidate types ("fast paths, old shapes, rare modes, provider exceptions, compatibility aliases, fallback parsers"), itemized deletion-prize evidence ("methods, adapters, unions, error variants, tests, docs branches"), two copy-paste-ready fill-in templates, a five-rung artifact ladder with use conditions, and a worked example naming real artifacts ("signInWithIdToken", "OIDCProvider narrowing", "two social sign-in docs branches"). Specific examples cover the common cases.

5 / 5

Workflow Clarity

The Procedure is a clearly sequenced six steps with explicit checkpoints: step 4 separates purpose-changing candidates, step 5 states the smallest-loss preference rule, and step 6 is an explicit decision gate ("If the loss is load-bearing, keep the feature... Otherwise, refuse... write that refusal into the spec"). Not a destructive or batch operation, so no validation cap applies; the checkpoints are explicit rather than implicit, fitting anchor 5 over anchor 4.

5 / 5

Progressive Disclosure

Clear section headers throughout, and every external pointer is one level deep with a stated purpose ("[Refactoring methods](../collapse-pass/references/refactoring-methods.md) guide caller counts, fixtures, state branches...", Rethink's clean-break reference, the docs article for narrative context). However, at ~218 lines the UI Refactor Template, UI Artifact Ladder, and worked example — roughly half the file — are inline content that could be split into reference files, and the under-50-line simple-skill exception does not apply, so it fits anchor 4's 'minor organization gaps' rather than anchor 5's 'content appropriately split'.

4 / 5

Total

17

/

20

Passed

Description

82%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 clearly names its evaluative job, provides explicit 'Use when' triggers with concrete domain terms, and cleanly disambiguates from the adjacent product-collapse skill. Its only weakness is that it describes a single action rather than enumerating several capabilities.

DimensionReasoningScore

Specificity

The description states one concrete evaluative action ("Evaluate whether refusing a small promise would eliminate disproportionate complexity") and then delegates ("use product-collapse to develop simpler product workflows") rather than listing several actions. This matches anchor 3 — domain and 1-2 concrete actions, not comprehensive — and not anchor 4, which requires several specific actions.

3 / 5

Completeness

Explicitly answers both parts: what ("Evaluate whether refusing a small promise would eliminate disproportionate complexity") and when, with concrete trigger phrases ("Use when judging asymmetric wins or a proposed refusal of fidelity, compatibility, fallbacks, modes, or duplicate paths"). It also adds routing guidance to product-collapse, matching the anchor-5 example's structure of clear what + explicit trigger-bearing when.

5 / 5

Trigger Term Quality

Good natural vocabulary in "refusal of fidelity, compatibility, fallbacks, modes, or duplicate paths" — terms users genuinely say in refactor and design-fidelity discussions — plus "judging asymmetric wins". It falls short of anchor 5 because common phrasings like "simplify", "delete features", or "reduce complexity" are absent (only "complexity" and "simpler" appear).

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — judging the cost of a specific refusal — with distinct trigger nouns, and explicitly disambiguates the closely related product-collapse skill ("use product-collapse to develop simpler product workflows"). The overlap risk with a sibling simplification skill is handled by an explicit boundary statement, so it fits anchor 5 rather than anchor 4's 'minor overlap risk'.

5 / 5

Total

17

/

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: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/asymmetric-wins/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.