capability-maplisted

# capability-map **The problem this solves:** you built a real agent. It reads your data, it reasons, it drafts. And then, over and over, it stops at the same place — it can *see* the thing but it can't *do* the thing. It reads your ad account but can't push the budget change. It reads your CRM but can't move the deal stage. It reads the form submissions but can't write back a status. That's the **80% wall**: the whole workflow is agentic right up until one action isn't *exposed* to the agent, and then a human has to finish it by hand. One member put it exactly: *"everything is, like, 80%… I can't get fully agentic as much as I try."* That wall is almost never your agent being dumb. It's a **coverage gap** — a specific action your tools don't hand to an agent (usually a *write* scope: create, update, delete, publish). You can't fix a gap you can't see. This skill makes the gap visible and tells you what to do about it. It does two things: 1. **Maps your coverage.** You list the actions your business actually needs an agent to take, tag each one green / yellow / red (fully callable / read-only / not exposed), and get back a coverage map — a scorecard of your real automation ceiling and the exact red actions holding you at 80%. 2. **Bridges the gaps.** For every red action, it names which of the **two workarounds** fits and gives you the plain-English move to make. A missing action almost always has a bridge — you just have to know which one. > This is a **map, not a machi