skills.rest
Goblin1024
Goblin1024COMMUNITY
Explore all skills by this author →
GitHub

cancel

Cancel the active OMK workflow and clean up its state.

6|1|Updated Apr 16, 2026
Search Tags:#automation#workflow#orchestration#state-management#cancel#omk
One-click install
npx skills add https://github.com/Goblin1024/oh-my-kimi --skill cancel-goblin1024
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Goblin1024/oh-my-kimi/tree/main/skills/cancel
Command: npx skills add https://github.com/Goblin1024/oh-my-kimi --skill cancel-goblin1024

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stops the active OMK workflow and cleans up related state to prevent drift and ensure a clean slate for the next run.

Core Features & Use Cases

  • Read Current State: Inspect skill-active.json to determine if a workflow is running and identify the active skill.
  • Update State & Cleanup: Mark active as false, set phase to cancelled, record cancelled_at timestamp, store a cancellation reason, archive current state, and release any locks.
  • Confirm & Safe Restart: Report the cancelled workflow and confirm the system is ready for a new run.

Quick Start

Cancel the active workflow by issuing the $cancel command.

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 workflow and restore a clean state?▼

To cancel an active workflow, the system marks it inactive, updates the state to cancelled, records a timestamp and reason, archives state, and releases locks to restore a clean slate for a fresh run.

What happens to active state and locks when halting workflow orchestration?▼

When halting workflow orchestration, the system reads the current state, archives it, sets the active flag to false, and explicitly releases any held locks to prevent state drift.

Why does workflow state drift occur after cancelling automation runs?▼

Workflow state drift occurs when cancellation does not properly archive state or release locks, which this process prevents by recording a cancellation reason, updating the phase to cancelled, and ensuring a clean slate for the next run.

Can I restart an OMK workflow immediately after stopping it?▼

Yes, you can restart an OMK workflow immediately after stopping it because the cancellation process confirms the system is ready by releasing locks and archiving the previous state to prevent conflicts.

Does cancelling a running workflow require manual state cleanup?▼

No, cancelling a running workflow does not require manual state cleanup because the process automatically archives the current state, marks the workflow inactive, and releases locks upon issuing the cancel command.

When should I interrupt a state-management workflow instead of letting it finish?▼

You should interrupt a state-management workflow when you need to prevent drift, discard the current execution path, or prepare the system for a fresh run by archiving the state and releasing active locks.

Related Skills

Explore More Software Engineering Skills→
mikeyobrienmikeyobrien
3.1k

ralph-operations

Manage Ralph orchestration loops by analyzing diagnostic data and debugging loop behavior.

Community
Basic
tkstangtkstang

oat-project-clear-active

Pause the active OAT project and confirm the state update.

Community
Basic
dmae97dmae97
130

mcp-install

Automate MCP server installation and verification for OMK projects.

Community
Intermediate
nichobbsnichobbs

cancel

Cancel active OMC modes with dependency-aware teardown and state cleanup.

Community
Advanced