CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inversion

Find the route to guaranteed failure, negate it. Use when a goal keeps not being reached head-on.

Quality

82%

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

92%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 exemplary lean instruction skill: a tight three-step inversion workflow with a built-in filtering checkpoint, a crisp output contract, and explicit edge-case routing. The only improvement would be a short worked example showing what a negated imperative line looks like.

DimensionReasoningScore

Conciseness

The body is ~15 lines with zero padding and no explanations of concepts Claude already knows — lines like "Hand it back as short bullets, one imperative per line, and stop there: nothing else rides along" make every token instruct, matching the lean-and-efficient anchor.

5 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill ("Negate each into one imperative line: a thing to do or a thing to stop", "Cut any line that is a risk to watch rather than an action to take", with a specified output format), but no worked example of a negated line is given — a minor gap below fully-executable coverage.

4 / 5

Workflow Clarity

A clear numbered 3-step sequence with an explicit validation step (step 3 filters risk-statements out of the route) and an error-recovery section for misapplication ("The failing is the execution, not the route → own it and fix it"); as a simple single-purpose skill with unambiguous steps, the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (no bundle files exist), and is well-organized into an intro constraint, steps, output contract, and edge cases — satisfying the under-50-lines guideline for a top progressive-disclosure score.

5 / 5

Total

19

/

20

Passed

Description

62%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 cleanly states both what the skill does and when to use it, in third person with a distinct method framing. Its weakness is trigger-term coverage and abstract phrasing: the 'when' clause misses the natural synonyms a stuck user would actually say, and the capability description stays at a high level of abstraction.

Suggestions

Add natural trigger phrases and synonyms to the 'when' clause, e.g. "Use when a goal keeps not being reached head-on, when the team is stuck, or when repeated attempts keep failing."

Ground the 'what' in more concrete actions, e.g. "List the fewest actions that guarantee failure, negate each into one imperative, and cut risks-to-watch from the list."

DimensionReasoningScore

Specificity

"Find the route to guaranteed failure, negate it" names 1-2 concrete actions (find, negate) but has no domain grounding and limited coverage, matching the anchor for 1-2 concrete actions without comprehensiveness rather than the several-specific-actions level.

3 / 5

Completeness

A clear 'what' ("Find the route to guaranteed failure, negate it") is paired with an explicit "Use when..." clause, so both are present; the 'when' is somewhat abstract rather than concrete trigger phrases, fitting the level where 'when' could be more explicit.

4 / 5

Trigger Term Quality

"Use when a goal keeps not being reached head-on" includes a relevant keyword ("goal... not being reached") but misses common natural variations users would say, such as "stuck", "keeps failing", "blocked", or "can't make progress".

3 / 5

Distinctiveness Conflict Risk

The inversion framing ("guaranteed failure, negate it") carves a fairly distinct niche, but the broad 'when' clause (any goal not reached) leaves minor overlap risk with general planning or problem-solving skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saadshahd/moo.md

Path

hope/skills/inversion/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.