Abort Safe Handler

What Abort Safe Handler is

Abort Safe Handler is a skill published in the digipulse-engineering/GAAI-framework repository on GitHub, which has about 162 stars. The repository describes itself as: “Turns AI coding tools into reliable software delivery systems. Drop a .gaai/ folder into any project — Discovery defines what to build, Delivery executes autonomously until criteria pass. Works with Claude Code, Codex CLI, Gemini CLI, Cursor, and more. No SDK. No package. Markdown + YAML + bash.”

A skill is a folder with a SKILL.md file: frontmatter with a name and a description, followed by instructions Claude follows. Claude loads a skill automatically when a task matches its description, and you can also run it directly with a slash and its name.

Skills work in Claude Code and in Claude Cowork, which makes Abort Safe Handler a portable way to give Claude the same method everywhere.

How to install Abort Safe Handler

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

The repository does not declare an open-source license, so we list only the outline of the file here. Read the full text on GitHub.

• Purpose / When to Activate
• Input Schema
• Process
• Step 0 — No-questions shortcut
• Step 1 — Stage 4 entry gate (AC1)
• Step 2 — Await user choice
• Step 3 — Route on choice
• Step 4 — Abort during entry gate (AC4)
• Orchestrator responsibility after this skill (AC2)
• Output Schema
• Quality Checks
• Non-Goals

Open SKILL.md on GitHub

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ