CtrlK
BlogDocsLog inGet started
Tessl Logo

hard-cut

Remove a feature completely with no backward compatibility. Use when the user says "hard cut", "rip it out", "delete it", "unship", "kill this feature", or wants dead code removed instead of deprecated. Delete the surface, callers, tests, docs, comments, fallbacks, and stubs.

74

Quality

93%

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

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An efficient, well-structured instruction skill with concrete deletables and a clear sweep sequence. The only gap is the absence of an explicit error-recovery feedback loop after the verification step, which caps workflow clarity at 2 for this destructive operation.

Suggestions

Add an explicit feedback loop after Sweep step 5: state what to do if verification fails (fix the breakage, re-run verification, only stop when it passes).

Name a concrete verification command or check in step 5 (e.g. build, typecheck, or test suite) instead of the abstract 'narrowest honest verification'.

DimensionReasoningScore

Conciseness

Lean throughout — every section (Rules, Sweep, Smells, Bias) earns its place, assumes Claude's competence, and explains no background concepts Claude already knows.

3 / 3

Actionability

Instruction-only but concrete: names the tool ('Trace references with `rg`'), enumerates specific deletables (surface, callers, types, state, tests, docs, comments), and gives a numbered sweep procedure — actionable per the instruction-only scoring note.

3 / 3

Workflow Clarity

The Sweep section is a clear 5-step sequence with a verification step (step 5, 'Run the narrowest honest verification'), but it lacks an explicit validate→fix→retry feedback loop, which the guidelines require for destructive operations.

2 / 3

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no external references; its well-organized sections (Rules, Sweep, Smells, Bias) justify a 3 under the simple-skills scoring note.

3 / 3

Total

11

/

12

Passed

Description

100%

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 tight, well-constructed description: concrete actions, an explicit 'Use when' clause packed with natural trigger phrases, and a clear niche that distinguishes it from deprecation-style skills. No verbosity or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person voice — 'Remove a feature completely' and 'Delete the surface, callers, tests, docs, comments, fallbacks, and stubs' — matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both 'what' (remove a feature completely, delete surface/callers/tests/docs/comments/fallbacks/stubs) and 'when' via a clear 'Use when the user says...' trigger clause.

3 / 3

Trigger Term Quality

Strong natural phrasing users would actually say: "hard cut", "rip it out", "delete it", "unship", "kill this feature", "dead code removed instead of deprecated" — good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a distinct niche — complete removal with no backward compatibility versus deprecation — with idiosyncratic triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
udecode/plate
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.