cancel

Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team)

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/cancel/SKILL.md

Quality

Content

65%

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

The content is highly actionable with concrete executable handlers per mode and includes validation checkpoints for the destructive team/Ralph operations, but it is hurt by significant redundancy (duplicated sections and restated ordering) and a monolithic structure with an absent external reference.

Suggestions

Merge the two 'Normative Ralph cancellation post-conditions' sections and consolidate the dependency-order list so it appears once instead of being restated across 'What It Does', the inline list, and 'Implementation Notes'.

Fix the numbered lists that skip from 2 to 4 (and remove stray duplicate headers) so the multi-step workflows are unambiguous.

Either create the referenced 'docs/contracts/ralph-cancel-contract.md' or move the long legacy-file compatibility list into a separate reference file to reduce the monolithic body.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no basic-concept padding) and provides concrete code, but it is padded with substantial redundancy: two near-duplicate 'Normative Ralph cancellation post-conditions' sections (lines ~45-56 and ~70-76), a dependency-order list restated across 'What It Does', the inline list, and 'Implementation Notes', plus overlapping Team/Tmux Team Cleanup sections, so it earns 2 rather than 3.	2 / 3
Actionability	It supplies concrete, copy-paste-ready bash with specific file paths, jq filters, and tmux commands for each mode (e.g., the Autopilot and Ralph handlers), matching the 'fully executable, specific examples' anchor.	3 / 3
Workflow Clarity	A clear sequence exists (parse args → detect modes → force/smart cancel) with some validation checkpoints (Ralph post-conditions MUST list, team graceful-then-force two-pass with 15s timeout), but broken numbered lists jump 1→2→4 (lines ~50 and ~74) and the dependency order is restated multiple inconsistent ways, leaving clarity below the clean anchor-3 example.	2 / 3
Progressive Disclosure	No bundle files exist and the ~400-line body is largely monolithic with inline detail (full legacy file list, contract text) that could be split out; the one external reference ('docs/contracts/ralph-cancel-contract.md') is clearly signaled one level deep but the file is not present in the bundle.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 specific and distinct, clearly scoping itself to cancelling active OMX modes with an enumerated mode list, but it omits an explicit 'when to use' trigger clause and relies on product jargon for its trigger terms.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to stop, cancel, or exit an OMX mode like autopilot, ralph, or ultrawork.'

Include common natural-language variations (stop, exit, end) alongside 'cancel' so the description matches what users actually say.

Expand beyond a single action verb by noting the outcome (e.g., '...and performs mode-specific state cleanup') to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Cancel any active OMX mode') and enumerates concrete targets (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team), but it offers a single action verb applied to a list rather than multiple distinct concrete actions like the 3-anchor 'Extract text, fill forms, merge documents'.	2 / 3
Completeness	It clearly answers 'what' (cancels an active OMX mode) but lacks any explicit 'Use when...' or trigger clause telling Claude when to invoke it, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	The enumerated mode names (autopilot, ralph, ultrawork, etc.) are reasonable trigger terms for users familiar with OMX, but 'OMX mode' is product jargon and the description omits common natural variations like 'stop' or 'exit', so it stops at 2.	2 / 3
Distinctiveness Conflict Risk	The phrase 'active OMX mode' plus a specific enumerated list of modes carves out a clear niche (OMX-mode cancellation) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: Yeachan-Heo/oh-my-codex
Path: plugins/oh-my-codex/skills/cancel/SKILL.md
Commit: 435d4a9

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.