What problem does it solve? Business analysts working with partner or third-party APIs often lack a structured, business-facing way to document, map, assess, and validate APIs without writing full OpenAPI specs or risking invented endpoints. This Skill produces a single API_BA.md artifact per invocation, grounded strictly in cited sources. ## Core Features & Use Cases - Seven analysis modes: api-doc, api-map, api-assess, api-design, api-checklist, api-test, and api-readiness, each filling dedicated sections of a shared template. - Hard safety contract: never invents endpoints or fields, never copies secrets or tokens into artifacts, and never claims production readiness without evidence. - Structured deliverable: every run produces API_BA.md with executive summary, sources, risks, open questions, and handoff sections, plus mode-specific tables such as API-to-screen mappings and Pass/Fail/Unknown readiness gates. - Use Case: A BA evaluating a payment provider's API runs api-assess to compare build vs. integrate options, then api-readiness before go-live to verify auth, error contracts, and rollback plans with cited evidence. ## Quick Start Ask the agent to run api-ba in api-map mode using the partner API documentation URL to produce an API_BA.md mapping API fields to system data and screens.