CtrlK
BlogDocsLog inGet started
Tessl Logo

cancel

Cancel stuck or orphaned executions

52

Quality

59%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/skills/cancel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, highly actionable, and well-organized for a simple single-purpose skill, but destructive/batch cancellation operations lack explicit pre-execution validation or error-recovery checkpoints, capping workflow clarity.

Suggestions

Add an explicit validation checkpoint before acting in --all and explicit-ID modes (e.g., confirm the count/IDs to be cancelled and warn that it is irreversible).

Include a brief error-recovery loop for the case where the CLI reports an invalid or already-terminal execution ID.

Move the large ASCII table example into a reference file or trim it, since it contributes padding beyond the core instructions.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, presenting CLI commands and a compact example without explaining what an event store or session is; only minor sections (the table example and next-step lines) could be trimmed.

4 / 5

Actionability

Fully executable copy-paste-ready CLI commands are given for all three modes plus a custom-reason variant, and the worked example demonstrates the interactive flow including expected prompts and output.

5 / 5

Workflow Clarity

The steps are clearly sequenced across the three modes, but this is a destructive/batch operation (cancelling executions, including --all) with no validation checkpoint confirming the selection before acting beyond the CLI's own prompt, so workflow clarity is capped at 3 per the rubric.

3 / 5

Progressive Disclosure

For a sub-50-line single-purpose skill with no bundle files, the content is well-organized into clearly labeled sections (Usage, How It Works, Instructions, State Transitions, Fallback, Example) with no nested references, satisfying the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

43%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 is concise and names a clear, specific action with relevant state qualifiers, but it lacks an explicit 'Use when...' trigger clause and omits common synonyms like kill/abort/stop, capping both completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when an execution is stuck or orphaned and needs to be killed.'

Surface key trigger synonyms (kill, abort, stop) in the description text itself rather than relying only on aliases.

Mention the supported invocation modes (by ID, --all, interactive) to broaden the concrete action coverage.

DimensionReasoningScore

Specificity

The description 'Cancel stuck or orphaned executions' names the domain (executions) and one concrete action (cancel) plus two state qualifiers (stuck, orphaned), but offers only minimal action coverage rather than the several specific actions a 3+ score requires.

2 / 5

Completeness

It clearly states the 'what' (cancel stuck/orphaned executions) but provides no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' is only weakly implied; per the rubric this caps completeness at 3.

3 / 5

Trigger Term Quality

Natural keywords like 'cancel', 'stuck', and 'orphaned' are present and likely match user phrasing, but the description omits common synonyms (kill, stop, abort) that appear only in aliases, leaving some natural variations uncovered.

3 / 5

Distinctiveness Conflict Risk

The niche of cancelling stuck/orphaned executions is fairly distinct with limited overlap against other skills, though the generic word 'executions' keeps it from being a fully unambiguous trigger.

4 / 5

Total

12

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Q00/ouroboros
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.