One-click install
npx skills add https://github.com/benediktms/overmind --skill cancel-benediktms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/cancel
Command: npx skills add https://github.com/benediktms/overmind --skill cancel-benediktms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stops an active Overmind run cleanly via the kernel cancel API. Use when the current objective is no longer wanted, the run is producing the wrong result, or the user asks to stop. Applies to scout, relay, and swarm modes.

Core Features & Use Cases

  • Cancel an ongoing run reliably across scout, relay, and swarm modes.
  • Ensure the brain task is marked cancelled and the neural-link session is closed.
  • Provide a clear confirmation of which mode was stopped and what partial results remain.

Quick Start

Cancel the active Overmind run by invoking the kernel cancel API with the objective_id.

Frequently Asked Questions about cancel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I cancel an active Overmind run cleanly?

To cancel an active Overmind run, invoke the kernel cancel API with the objective_id. This terminates the current objective across scout, relay, and swarm modes while handling state cleanup and preserving partial results.

What happens to partial results when I abort an Overmind execution?

When you abort an Overmind execution using the kernel cancel API, it handles state cleanup and provides optional preservation of partial results. You receive a clear confirmation of what partial results remain.

Can I stop an Overmind run in scout, relay, and swarm modes?

Yes, you can stop an Overmind run in scout, relay, and swarm modes. The kernel cancel API applies across all these execution modes to reliably cancel ongoing objectives.

Do I need specific API access to terminate an Overmind objective?

Yes, terminating an Overmind objective requires access to the mcp__overmind__overmind_cancel API and related status endpoints. These endpoints safely close the neural-link session and mark the brain task as cancelled.

Why should I use the kernel cancel API instead of force stopping a run?

Using the kernel cancel API ensures the brain task is marked cancelled and the neural-link session is closed cleanly. This prevents orphaned processes and provides confirmation of the stopped mode and remaining partial results.