skills.rest
apireno
apirenoCOMMUNITY
Explore all skills by this author →
GitHub

escalate-drain

Reads pending escalation files from the CTO inbox and presents them for rulings.

1|Updated Jun 13, 2026
Search Tags:#bash#agent workflow#inbox#multi-repo#triage#escalation#cto
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill escalate-drain-apireno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: escalate-drain
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/escalate-drain
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill escalate-drain-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In a multi-repo agent workflow, dev teams and VP agents drop escalation files into a shared inbox, but nothing surfaces them to the CTO. This Skill drains that inbox so pending cross-repo questions get answered instead of sitting unread. ## Core Features & Use Cases - Inbox scanning: Finds all pending Markdown escalation files in ~/.cto/inbox/ and reports a count. - CTO-home anchoring: Resolves the correct CTO home directory via environment variables, .cto-path pointers, and ~/.cto/home, with validated fallbacks and clear error diagnostics. - Structured ruling workflow: For each escalation, the CTO records a ruling, reasoning, action items, and cross-repo notes, then archives the file to a processed/ folder. - Use Case: At the start of a session you ask "any escalations?" and the Skill lists every pending item from dev teams, you rule on each one, and the summaries are archived with timestamps. ## Quick Start Ask the agent "any escalations?" or "what's pending?" to drain the CTO inbox and rule on each item.

Frequently Asked Questions about escalate-drain

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

FAQPage Schema
How do I check pending escalations from dev teams?▼

Ask the agent "any escalations?" or "what's pending?" and the Skill scans ~/.cto/inbox/ for Markdown files, prints each one, and walks you through ruling on them. Processed files are moved to ~/.cto/inbox/processed/ with timestamps.

How are escalation files created in the inbox?▼

Dev-team or VP Stop hooks drop .escalation-pending Markdown files into ~/.cto/inbox/ when a team needs a CTO decision. The drain Skill only reads and archives them; it does not create them.

Why does the skill report no CTO home found?▼

The Skill requires a directory containing .cto/projects.yaml and checks CTO_HOME, CTO_REPO, CLAUDE_PROJECT_DIR, parent directories, and ~/.cto/home in order. If none validate, run it from the CTO home or write the path to ~/.cto/home.

Can the escalation drain run automatically at session start?▼

Yes, it can be wired to fire automatically via a Stop hook, and it is also designed to be invoked when the CEO starts a session or asks about pending items.

What happens to escalation files after they are handled?▼

After the CTO rules on each escalation, the file is moved to ~/.cto/inbox/processed/ with a date-time suffix so it does not reappear in later drains. Lasting decisions are written as ADRs or RCAs in the affected repo.

Related Skills

Explore More Software Engineering Skills→
yazelinyazelin
31

ctos-kb

Access CTOS knowledge base, library, NAS, and ERPNext data via ctos CLI.

Community
Intermediate
AntonBespalovAntonBespalov

adr-writer

Record architecture decisions with options, criteria, risks, and evidence in Markdown.

Community
Advanced
SocketDevSocketDev
125

fleet-auditing-gha

Diff GitHub Actions settings against a canonical baseline to surface drift.

Official
Intermediate
TitoPrauseeTitoPrausee

inter-agent-gitlab-message-queue

Coordinate asynchronous AI agent messages through GitLab issues.

Community
Intermediate