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

AGPL-3.0Auto-check passed

Install Cancel

skills CLI
$ npx skills add yangyuan-zhen/PolyWeather --skill cancel -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yangyuan-zhen/PolyWeather cancel --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yangyuan-zhen/PolyWeather.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/cancel .claude/skills/cancel && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cancel
GitHub stars
316
Token cost
~3.7k tokens
SKILL.md length
1,254 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
AGPL-3.0

At a glance

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

  • Works in 3 steps: Target Ralph state is terminalized, not… → If Ralph is linked to Ultrawork or… → Cancellation MUST remain scope-safe: no…
  • SKILL.md covers What It Does, Usage, Auto-Detection and Normative Ralph cancellation…, plus 7 more sections
  • Calls jq

What it does

Cancel is an agent skill from yangyuan-zhen/PolyWeather. [OMX] Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team)

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: polymarket Intelligent Weather Quant Analysis Bot. The licence is AGPL-3.0.

Example prompts

  • “/cancel”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Target Ralph state is terminalized, not silently removed
  2. If Ralph is linked to Ultrawork or Ecomode in the same scope, that linked mode is also terminalized/non-active.
  3. Cancellation MUST remain scope-safe: no mutation of unrelated sessions.

What it can do on your machine

Read from SKILL.md and the folder at commit 43e658b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cancel loads about 3.7k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 1,254 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yangyuan-zhen/PolyWeather at commit 43e658b, republished under its AGPL-3.0 licence (© yangyuan-zhen). 1,254 words, ~3,659 tokens.

Download SKILL.mdSave it as .claude/skills/cancel/SKILL.md (or your agent's skills folder).
name
cancel
description
[OMX] Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team)

Cancel Skill

Intelligent cancellation that detects and cancels the active OMX mode.

The cancel skill is the standard way to complete and exit any OMX mode. When the stop hook detects work is complete, it instructs the LLM to invoke this skill for proper state cleanup. If cancel fails or is interrupted, retry with --force flag, or wait for the 2-hour staleness timeout as a last resort.

What It Does

Automatically detects which mode is active and cancels it:

  • Autopilot: Stops workflow, preserves progress for resume
  • Ralph: Stops persistence loop, clears linked ultrawork if applicable
  • Ultrawork: Stops parallel execution (standalone or linked)
  • Ecomode: Stops token-efficient parallel execution (standalone or linked to ralph)
  • UltraQA: Stops QA cycling workflow
  • Swarm: Stops coordinated agent swarm, releases claimed tasks
  • Ultrapilot: Stops parallel autopilot workers
  • Pipeline: Stops sequential agent pipeline
  • Team: Sends shutdown inbox to all workers, waits for exit, kills tmux session, and clears team state

Usage

/cancel

Or say: "cancelomc", "stopomc"

Auto-Detection

/cancel follows the session-aware state contract:

  • By default the command inspects the current session via state_list_active and state_get_status, navigating .omx/state/sessions/{sessionId}/… to discover which mode is active.
  • When a session id is provided or already known, that session-scoped path is authoritative. Legacy files in .omx/state/*.json are consulted only as a compatibility fallback if the session id is missing or empty.
  • Swarm is a shared SQLite/marker mode (.omx/state/swarm.db / .omx/state/swarm-active.marker) and is not session-scoped.
  • The default cleanup flow calls state_clear with the session id to remove only the matching session files; modes stay bound to their originating session.

Normative Ralph cancellation post-conditions (MUST)

For Ralph-targeted cancellation (standalone or linked), completion is defined by post-conditions:

  1. Target Ralph state is terminalized, not silently removed:
    • active=false
    • current_phase='cancelled'
    • completed_at is set (ISO timestamp)
  2. If Ralph is linked to Ultrawork or Ecomode in the same scope, that linked mode is also terminalized/non-active.
  3. Cancellation MUST remain scope-safe: no mutation of unrelated sessions.

See: docs/contracts/ralph-cancel-contract.md.

Active modes are still cancelled in dependency order:

  1. Autopilot (includes linked ultragoal/ultraqa/ecomode cleanup plus explicit legacy Ralph cleanup)
  2. Ralph (cleans its linked ultrawork or ecomode)
  3. Ultrawork (standalone)
  4. Ecomode (standalone)
  5. UltraQA (standalone)
  6. Swarm (standalone)
  7. Ultrapilot (standalone)
  8. Pipeline (standalone)
  9. Team (tmux-based)
  10. Plan Consensus (standalone)

Normative Ralph post-conditions (MUST)

When cancellation targets Ralph state in a scope, completion requires all of the following:

  1. Ralph state is terminal in that same scope: active=false, current_phase='cancelled' (or linked terminal phase), and completed_at is set.
  2. Linked Ultrawork/Ecomode in the same scope is also terminal/non-active.
  3. Unrelated sessions are untouched.

Exact-scope force compatibility

--force is a compatibility flag for the same proven current scope as bare cancellation. It does not widen cancellation to other sessions, legacy roots, Team runtimes, or workspace artifacts. Its only additional behavior is exact-session native-stop cleanup after the same ownership checks.

--all is intentionally unsupported. Workspace-wide destructive cancellation requires a separately reviewed command and authority contract. Unknown flags and mixed flag combinations fail before mutation.

Exact canonical recovery under resumed ownership drift

The native PreToolUse exemption accepts an inherited non-empty NODE_EXTRA_CA_CERTS only for the exact canonical omx cancel command shape (and workflow-supported --force). This does not relax NODE_OPTIONS, loader/import hooks, OPENSSL_CONF, shell startup/function injection, PATH/PATHEXT shadowing, leading assignments, command chaining, noncanonical executable resolution, or unrelated commands.

For session-scoped cancellation, a stale top-level owner_codex_session_id in skill-active-state.json may be replaced—not aliased—only inside the existing cancellation transaction after the current pointer, native owner sidecar, canonical target session, and all nested owner/session evidence agree. Displaced owner evidence must be positively absent or stale/dead; live, malformed, foreign, indeterminate, nested-contradictory, or cross-session evidence fails closed. If the skill marker is absent, mode-only cancellation keeps its existing behavior and does not create one.

The replacement and terminal skill state are serialized as one final skill payload. Cancellation retains all-target prevalidation, O_NOFOLLOW, content/identity revalidation, per-file sync, and reverse rollback. These are in-process transaction guarantees, not crash-atomic multi-file visibility; rollback restoration failures are reported rather than presented as successful cleanup.

text
/cancel
/cancel --force
Argument contract
  • no arguments: cancel only the provably current session/root scope;
  • --force: same scope, plus exact-session native-stop cleanup;
  • --all: reject without mutation;
  • unknown or multiple flags: reject without mutation.
State discovery

Cancellation derives writable targets from the already-proven writable scope. Compatibility discovery may inform status, but never grants write authority. Unrelated session, legacy-root, Team, and run-dir state remains untouched unless it is independently proven as the exact cancellation target.

3B. Smart Cancellation (default)
Show full SKILL.md (526 more words)Show less
If Team Active (tmux-based)

Teams are detected by checking for config files in .omx/state/team/:

bash
# Check for active teams
ls .omx/state/team/*/config.json 2>/dev/null

Two-pass cancellation protocol:

Pass 1: Graceful Shutdown

For each team found in .omx/state/team/:
  1. Read config.json to get team_name and workers list
  2. For each worker:
     a. Write shutdown inbox to .omx/state/team/{name}/workers/{worker}/inbox.md
     b. Send short trigger via tmux send-keys
     c. Wait up to 15 seconds for worker tmux pane to exit
     d. If still alive: mark as unresponsive

Pass 2: Force Kill

After graceful pass:
  1. For each remaining alive worker:
     a. Send C-c via tmux send-keys
     b. Wait 2 seconds
     c. Kill the tmux window if still alive
  2. Destroy the tmux session: tmux kill-session -t omx-team-{name}

Cleanup:

  1. Strip AGENTS.md team worker overlay (<!-- OMX:TEAM:WORKER:START/END -->)
  2. Remove team state directory: rm -rf .omx/state/team/{name}/
  3. Clear team mode state: state_clear(mode="team")
  4. Emit structured cancel report

Structured Cancel Report:

Team "{team_name}" cancelled:
  - Workers signaled: N
  - Graceful exits: M
  - Force killed: K
  - tmux session destroyed: yes/no
  - State cleaned up: yes/no

Implementation note: The cancel skill is executed by the LLM, not as a bash script. When you detect an active team:

  1. Check .omx/state/team/*/config.json for active teams
  2. For each worker in config.workers, write shutdown inbox and send trigger
  3. Wait briefly for workers to exit (15s timeout)
  4. Force kill remaining workers via tmux
  5. Destroy tmux session: tmux kill-session -t omx-team-{name}
  6. Strip AGENTS.md overlay
  7. Remove state: rm -rf .omx/state/team/{name}/
  8. state_clear(mode="team")
  9. Report structured summary to user
If Autopilot Active

Call cancelAutopilot() from src/hooks/autopilot/cancel.ts:27-78:

bash
# Autopilot handles its own cleanup + ralph + ultraqa
# Just mark autopilot as inactive (preserves state for resume)
if [[ -f .omx/state/autopilot-state.json ]]; then
  # Clean up ralph if active
  if [[ -f .omx/state/ralph-state.json ]]; then
    RALPH_STATE=$(cat .omx/state/ralph-state.json)
    LINKED_UW=$(echo "$RALPH_STATE" | jq -r '.linked_ultrawork // false')

    # Clean linked ultrawork first
    if [[ "$LINKED_UW" == "true" ]] && [[ -f .omx/state/ultrawork-state.json ]]; then
      rm -f .omx/state/ultrawork-state.json
      echo "Cleaned up: ultrawork (linked to ralph)"
    fi

    # Clean ralph
    rm -f .omx/state/ralph-state.json
    rm -f .omx/state/ralph-verification.json
    echo "Cleaned up: ralph"
  fi

  # Clean up ultraqa if active
  if [[ -f .omx/state/ultraqa-state.json ]]; then
    rm -f .omx/state/ultraqa-state.json
    echo "Cleaned up: ultraqa"
  fi

  # Mark autopilot inactive but preserve state
  CURRENT_STATE=$(cat .omx/state/autopilot-state.json)
  CURRENT_PHASE=$(echo "$CURRENT_STATE" | jq -r '.phase // "unknown"')
  echo "$CURRENT_STATE" | jq '.active = false' > .omx/state/autopilot-state.json

  echo "Autopilot cancelled at phase: $CURRENT_PHASE. Progress preserved for resume."
  echo "Run /autopilot to resume."
fi
If Ralph Active (but not Autopilot)

Call clearRalphState() + clearLinkedUltraworkState() from src/hooks/ralph-loop/index.ts:147-182:

bash
if [[ -f .omx/state/ralph-state.json ]]; then
  # Check if ultrawork is linked
  RALPH_STATE=$(cat .omx/state/ralph-state.json)
  LINKED_UW=$(echo "$RALPH_STATE" | jq -r '.linked_ultrawork // false')

  # Clean linked ultrawork first
  if [[ "$LINKED_UW" == "true" ]] && [[ -f .omx/state/ultrawork-state.json ]]; then
    UW_STATE=$(cat .omx/state/ultrawork-state.json)
    UW_LINKED=$(echo "$UW_STATE" | jq -r '.linked_to_ralph // false')

    # Only clear if it was linked to ralph
    if [[ "$UW_LINKED" == "true" ]]; then
      rm -f .omx/state/ultrawork-state.json
      echo "Cleaned up: ultrawork (linked to ralph)"
    fi
  fi

  # Clean ralph state
  rm -f .omx/state/ralph-state.json
  rm -f .omx/state/ralph-plan-state.json
  rm -f .omx/state/ralph-verification.json

  echo "Ralph cancelled. Persistent mode deactivated."
fi
If Ultrawork Active (standalone, not linked)

Call deactivateUltrawork() from src/hooks/ultrawork/index.ts:150-173:

bash
if [[ -f .omx/state/ultrawork-state.json ]]; then
  # Check if linked to ralph
  UW_STATE=$(cat .omx/state/ultrawork-state.json)
  LINKED=$(echo "$UW_STATE" | jq -r '.linked_to_ralph // false')

  if [[ "$LINKED" == "true" ]]; then
    echo "Ultrawork is linked to Ralph. Use /cancel to cancel both."
    exit 1
  fi

  # Remove local state
  rm -f .omx/state/ultrawork-state.json

  echo "Ultrawork cancelled. Parallel execution mode deactivated."
fi
If UltraQA Active (standalone)

Call clearUltraQAState() from src/hooks/ultraqa/index.ts:107-120:

bash
if [[ -f .omx/state/ultraqa-state.json ]]; then
  rm -f .omx/state/ultraqa-state.json
  echo "UltraQA cancelled. QA cycling workflow stopped."
fi
No Active Modes
bash
echo "No active OMX modes detected."
echo ""
echo "Checked for:"
echo "  - Autopilot (.omx/state/autopilot-state.json)"
echo "  - Ralph (.omx/state/ralph-state.json)"
echo "  - Ultrawork (.omx/state/ultrawork-state.json)"
echo "  - UltraQA (.omx/state/ultraqa-state.json)"
echo ""
echo "Use --force for exact-session native-stop cleanup without widening scope."

Implementation Notes

The cancel skill runs as follows:

  1. Parse arguments strictly. Bare cancellation and a single --force are accepted; --all, unknown flags, and multiple flags fail before mutation.
  2. Resolve one writable scope and treat compatibility discovery as read-only.
  3. Cancel only active state files whose exact scope, ownership fields, and frozen file identity are proven.
  4. With --force, remove only the selected session's native-stop entry after the same proof and revalidation.
  5. Leave unrelated sessions, legacy compatibility roots, Team artifacts, and tmux sessions untouched.

Mode-specific subsections below describe same-scope dependency ordering only.

Messages Reference

ModeSuccess Message
Autopilot"Autopilot cancelled at phase: {phase}. Progress preserved for resume."
Ralph"Ralph cancelled. Persistent mode deactivated."
Ultrawork"Ultrawork cancelled. Parallel execution mode deactivated."
Ecomode"Ecomode cancelled. Token-efficient execution mode deactivated."
UltraQA"UltraQA cancelled. QA cycling workflow stopped."
Swarm"Swarm cancelled. Coordinated agents stopped."
Ultrapilot"Ultrapilot cancelled. Parallel autopilot workers stopped."
Pipeline"Pipeline cancelled. Sequential agent chain stopped."
Team"Team cancelled. Teammates shut down and cleaned up."
Plan Consensus"Plan Consensus cancelled. Planning session ended."
Force"All OMX modes cleared. You are free to start fresh."
None"No active OMX modes detected."

What Gets Preserved

ModeState PreservedResume Command
AutopilotYes (phase, files, spec, plan, verdicts)/autopilot
RalphNoN/A
UltraworkNoN/A
UltraQANoN/A
SwarmNoN/A
UltrapilotNoN/A
PipelineNoN/A
Plan ConsensusYes (plan file path preserved)N/A

Notes

  • Dependency-aware: Autopilot cancellation cleans up Ultragoal/UltraQA state and any explicit legacy Ralph state
  • Link-aware: Ralph cancellation cleans up linked Ultrawork or Ecomode
  • Safe: Only clears linked Ultrawork, preserves standalone Ultrawork
  • Local-only: Clears state files in .omx/state/ directory
  • Resume-friendly: Autopilot state is preserved for seamless resume
  • Team-aware: Team cancellation is permitted only when the selected state carries exact same-scope Team authority; unrelated Team artifacts and tmux sessions remain untouched.

Tmux Team Cleanup

Cancellation MUST NOT enumerate or kill every omx-team-* session and MUST NOT recursively delete .omx/state/team/. Team shutdown requires the exact frozen Team root, internal name, session, leader pane, and runtime identity selected by the authorized state transition. When that proof is unavailable or changes, cancellation fails closed without signals, pane actions, overlay edits, or Team-state deletion.

--force does not widen Team scope. It only enables exact-session native-stop cleanup after the same authority checks.

© yangyuan-zhen, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/cancel of yangyuan-zhen/PolyWeather.

Open the folder on GitHubat commit 43e658b

Compare with similar skills

Cancel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cancel compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cancel this skillyangyuan-zhen/PolyWeather316—~3.7kAutomated safety check: PassAGPL-3.0
Cancel Ralphcursor/plugins11k—~183Automated safety check: PassNone
Cancel Ralphforyourhealth111-pixel/Vibe-Skills3.6k—~247Automated safety check: PassApache-2.0
OMC Mode CancellationYeachan-Heo/oh-my-claudecode40k—~4.6kAutomated safety check: PassMIT
Ultraworkcode-yeongyu/oh-my-openagent70k—~8kAutomated safety check: PassCustom licence
AutopilotYeachan-Heo/oh-my-claudecode40k—~4.4kAutomated safety check: PassMIT

Similar skills

  • Cancel Ralph

    cursor/plugins

    Official

    Cancel an active Ralph Loop. An agent skill from cursor/plugins.

    11k GitHub stars~183 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Cancel Ralph

    foryourhealth111-pixel/Vibe-Skills

    Codex-compatible cancel command for Ralph loop state, preserving the original command name.

    3.6k GitHub stars~247 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • OMC Mode Cancellation

    Yeachan-Heo/oh-my-claudecode

    Detects and gracefully cancels whichever OMC mode, autopilot, ralph, swarm, pipeline, or team, is currently active, then clears its state.

    40k GitHub stars~4.6k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Ultrawork

    code-yeongyu/oh-my-openagent

    The binding ultrawork-mode directive. An agent skill from code-yeongyu/oh-my-openagent.

    70k GitHub stars~8k tokensUpdated today
    Auto-check passed
  • Autopilot

    Yeachan-Heo/oh-my-claudecode

    Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.

    40k GitHub stars~4.4k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Ralph

    Yeachan-Heo/oh-my-claudecode

    Self-referential loop until task completion with configurable verification reviewer

    40k GitHub stars~7.5k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

More from yangyuan-zhen/PolyWeather

All 26 skills in this repo
  • AI Slop Cleaner

    yangyuan-zhen/PolyWeather

    [OMX] Run an anti-slop cleanup/refactor/deslop workflow. An agent skill from yangyuan-zhen/PolyWeather.

    316 GitHub stars~2.2k tokensUpdated 20 days ago
    Auto-check passed
  • Analyze

    yangyuan-zhen/PolyWeather

    [OMX] Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries.

    316 GitHub stars~1.6k tokensUpdated 20 days ago
    Auto-check passed
  • Autoresearch

    yangyuan-zhen/PolyWeather

    [OMX] Stateful validator-gated research loop with native-hook persistence

    316 GitHub stars~786 tokensUpdated 20 days ago
    Auto-check passed
  • Best Practice Research

    yangyuan-zhen/PolyWeather

    [OMX] Bounded best-practice research wrapper using official/upstream evidence first

    316 GitHub stars~1.4k tokensUpdated 20 days ago
    Auto-check passed
  • Configure Notifications

    yangyuan-zhen/PolyWeather

    [OMX] Configure OMX notifications - unified entry point for all platforms

    316 GitHub stars~2.7k tokensUpdated 20 days ago
    Auto-check passed
  • Design

    yangyuan-zhen/PolyWeather

    [OMX] Canonical repo-local DESIGN.md workflow for product, UI/UX, and frontend decision source of truth

    316 GitHub stars~1.8k tokensUpdated 20 days ago
    Auto-check passed

Questions about Cancel

What does Cancel do?

[OMX] Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team). Cancel is an agent skill from yangyuan-zhen/PolyWeather.

How do I install Cancel in Claude Code?

Run `npx skills add yangyuan-zhen/PolyWeather --skill cancel -a claude-code`. Or copy the skill folder (.codex/skills/cancel in yangyuan-zhen/PolyWeather) into .claude/skills/cancel in your project. Claude Code loads it when a task matches its description.

How do I install Cancel in Codex?

Run `npx skills add yangyuan-zhen/PolyWeather --skill cancel -a codex`. Or copy the skill folder (.codex/skills/cancel in yangyuan-zhen/PolyWeather) into .agents/skills/cancel in your project. Codex loads it when a task matches its description.

Can I use Cancel in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yangyuan-zhen/PolyWeather --skill cancel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cancel, .gemini/skills/cancel, .github/skills/cancel and .opencode/skills/cancel in your project.

What does Cancel need to run?

Going by SKILL.md and its folder, Cancel needs the command-line tools its instructions call (jq).

Does Cancel access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cancel safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cancel use?

Cancel is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cancel use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cancel?

Skills that share tags, products or a category with Cancel: Cancel Ralph (cursor/plugins, 11k stars), Cancel Ralph (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), OMC Mode Cancellation (Yeachan-Heo/oh-my-claudecode, 40k stars) and Ultrawork (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cancel?

yangyuan-zhen (a GitHub user) maintains it in yangyuan-zhen/PolyWeather, which has 316 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on September 20, 2026.

Source: yangyuan-zhen/PolyWeather on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.