Stats
Actions
Tags
From superpowers-cowork
[INTERNAL ONLY] Choose tools for each step: MCP, browser, desktop, then human fallback. Cross-cutting skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/superpowers-cowork:connector-orchestrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
At each workflow step that needs an external tool:
At each workflow step that needs an external tool:
Retry policy: Before escalating to the next tier, apply the error-handling retry policy — retry once if the failure is transient, skip retries if the tool is unavailable.
When falling back: Always tell the human. "The email connector was not responding, so I used browser automation instead." Never silently skip a step because a tool isn't available.
When chaining across tools (e.g. email attachment → spreadsheet): you must record where each piece of data came from. This note is required — verification cannot proceed without it.
For the full tool table: references/mcp-catalog.md.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub smatty-ice/superpowers-cowork-marketplace --plugin superpowers-cowork