api-for-yourself

# API For Yourself Skill "User manual for me" documents have existed for years and mostly read like horoscopes ("I value transparency"). The API-spec format fixes them by force: an endpoint must say what you send and what comes back; a rate limit must be a number; an error code must name the actual failure behaviour. The joke is the format — the payload is real self-knowledge, and the test of every line is *would a new teammate behave differently after reading it?* Deadpan technical voice, honest contents, one page. ## What This Skill Produces - A **personal API spec**: endpoints, request formats, rate limits, error codes, auth & scopes, dependencies, scheduled maintenance, changelog — in deadpan OpenAPI-ish style - A **quickstart** at the top: the three calls that cover 90% of integrations with this human - Optionally a **team version**: specs for a whole team session, plus the facilitation note for running it as an exercise ## Required Inputs Ask for (if not already provided): - How people should bring them things: channel preferences, context depth (one-liner or brief?), and what makes a request instantly workable vs instantly annoying - Real capacity: meeting tolerance per day, focus blocks, response-time honest averages by channel - Actual failure modes, told honestly: what happens when they're surprised late Friday, overloaded, given vague asks, or micromanaged - What earns trust and what burns it; energy sources and drains; current quirks a teamm...