skills.rest
yoshisada
yoshisadaCOMMUNITY
Explore all skills by this author →
GitHub

wheel-stop

Stop active workflows and archive state files to .wheel/history/.

Updated Mar 26, 2026
Search Tags:#automation#workflow#cleanup#history#state-archiving#hook-interception#ownership-resolution
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill wheel-stop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wheel-stop
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-wheel/skills/wheel-stop
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill wheel-stop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stops active workflows, archives state files to .wheel/history/, and deactivates hook interception to ensure safe cleanup.

Core Features & Use Cases

  • Stop active workflows and archive their state to preserve history.
  • Deactivate the PostToolUse hook interception to prevent further interactions.
  • Target specific workflows by session_id or agent_id, or stop all workflows.

Quick Start

Stop a specific workflow by its session_id or agent_id, or stop all workflows.

Frequently Asked Questions about wheel-stop

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

FAQPage Schema
How do I stop an active workflow and archive its state history?▼

To stop an active workflow, this skill halts the process and archives existing state files to .wheel/history/ before removal. This preserves your workflow history automatically while safely reclaiming resources.

Can I selectively target workflows by session ID or agent ID for cleanup?▼

Yes, you can selectively target workflows by session_id or agent_id to stop specific instances. Alternatively, you can issue a command to stop all active workflows simultaneously for bulk resource reclamation.

Why does workflow cleanup require deactivating hook interception?▼

Workflow cleanup requires deactivating hook interception to ensure safe, ownership-aware cleanup. By deactivating the PostToolUse hook, the script prevents further automated interactions while removing state files.

What is the best way to preserve workflow history before removing state files?▼

The best way to preserve workflow history is to archive existing state files to .wheel/history/ before removal. This ensures your historical workflow data remains intact and accessible after the active process stops.

When should I stop workflows and archive state files?▼

You should stop workflows and archive state files when you need to reclaim system resources, preserve workflow history for auditing, or safely deactivate automated hook interception without losing previous state data.

Does wheel-stop support stopping all workflows simultaneously?▼

Yes, wheel-stop supports stopping all active workflows simultaneously. It archives their respective state files to .wheel/history/ and executes ownership-aware cleanup via the deactivate.sh script for safe removal.

Related Skills

Explore More Software Engineering Skills→
TomGranotTomGranot
58

cleanup-lead-owners

Reassign HubSpot contacts, companies, and deals from non-employees to active owners.

Community
Intermediate
dioerdendioerden

session-logs

Search and analyze past session conversations in JSONL files using jq and regex.

Community
Intermediate
bosens-Chinabosens-China
10

langgraph-persistence

Manage LangGraph persistent state with checkpointers and thread IDs.

Community
Advanced
tmustiertmustier
3

long-task-harness

Preserve session progress and feature state across long-running agent tasks.

Community
Intermediate