durable-workflow-runtime:delete

Deletes a published durable workflow and removes its catalog binding entry.

Updated May 13, 2026
One-click install
npx skills add https://github.com/onesmash/slm-as-harness --skill durable-workflow-runtime-delete-onesmash
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: durable-workflow-runtime:delete
Source: https://github.com/onesmash/slm-as-harness/tree/main/skills/durable-workflow-runtime/delete
Command: npx skills add https://github.com/onesmash/slm-as-harness --skill durable-workflow-runtime-delete-onesmash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Removing a durable workflow by hand means editing workflow-binding.json, deleting the workflow directory, and cleaning up shortcut skills, which is error-prone and can leave the runtime in an inconsistent state. This Skill performs the removal safely with confirmation checks and default-workflow protection. ## Core Features & Use Cases - Catalog-Aware Deletion: Removes the workflow entry from workflow-binding.json and deletes the matching directory under workflow-runtime/workflows/. - Shortcut Cleanup: Removes the slash-only shortcut skill and its mirrored Claude entry under .claude/skills/ when present. - Default Workflow Safety: Refuses to delete the current default workflow unless you pass --new-default-workflow-id or --clear-default. - Use Case: You published a demo workflow that is no longer needed. Run the delete script with --workflow-id and --confirm to remove its directory, binding entry, and shortcuts, then run the sibling inject script to refresh the repo's AGENTS.md and CLAUDE.md catalog block. ## Quick Start Ask the AI to delete the workflow with a given workflow id from durable-workflow-runtime, confirming the id and choosing a new default workflow if it is currently the default.

Frequently Asked Questions about durable-workflow-runtime:delete

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

FAQPage Schema
How do I delete a durable workflow from workflow-binding.json?▼

Run scripts/delete_workflow.py with --workflow-id and --confirm set to the same workflow id. The script removes the binding entry, deletes the workflow directory under workflow-runtime/workflows/, and cleans up the matching shortcut skills.

How to remove a workflow that is the current default?▼

Pass either --new-default-workflow-id pointing to a remaining published workflow, or --clear-default to remove the default entirely. Without one of these flags, the script refuses to delete the current default workflow.

Does deleting a workflow also remove its shortcut skill?▼

Yes. When present, the script removes the slash-only shortcut under workflow-shortcuts/<workflow_id>/ and the mirrored Claude entry under .claude/skills/<workflow_id>/, reporting both in its JSON success output.

Why does workflow deletion fail with a confirmation error?▼

The script requires --confirm to exactly match --workflow-id as a safety check against accidental deletion. It also fails if the workflow id contains unsafe characters, is not published in the binding catalog, or its directory is missing.

What are the limitations of the workflow delete script?▼

It only validates removal concerns and does not check historical run state, external repository references, or prose mentions in other workflow docs. Refreshing AGENTS.md and CLAUDE.md requires a separate run of the sibling inject script.