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 teammate would discover in week three anyway
Process
- Interview past the horoscope. For every generic answer ("I like
directness"), push for the behavioural version: what does a well-formed
request actually contain? What's the observable symptom when it's
missing? The spec is built from behaviours, not values.
- Design the endpoints — the 4–6 things people actually come to this
person for. Each gets: method + path (
POST /decisions), request body
(what to include), response (what they'll get and by when), and the errors
it can throw. Include one honest deprecated endpoint (/status-meetings — deprecated, use async /updates instead).
- Publish real numbers. Rate limits with actual figures ("3 meetings/day
before response quality degrades — 429 after that"), response-time SLAs by
channel that match reality, scheduled maintenance (focus blocks, the school
run, timezone). A limit without a number is a mood.
- Write error codes as self-knowledge. The funniest section and the most
useful:
429 Too Many Meetings (symptom: monosyllabic replies; retry:
tomorrow morning) · 400 Vague Request (returns clarifying questions, not
work) · 503 Friday 5pm Surprise (accepted but not processed until Monday;
don't resend). Each code: symptom, what NOT to do, the retry strategy.
- Auth, changelog, quickstart. Auth: how trust levels are earned and what
each unlocks (scope:
direct-feedback granted after…). Changelog: 2–3
honest entries ("v3.1: no longer needs to win every argument — patched
after 2024 retro"). Quickstart on top: the three most-used calls, copy-paste
ready.
Output Format
# [Name] API — v[X.Y]
> One-line summary of what this human is for.
## Quickstart
[The 3 calls covering 90% of use]
## Endpoints
### POST /[thing]
Request: … · Response (SLA): … · Errors: [codes]
## Rate limits
[Real numbers: meetings, interrupts, context switches]
## Error codes
| Code | Trigger | Symptom you'll observe | Retry strategy |
## Auth & scopes
[How trust is earned; what each level unlocks]
## Scheduled maintenance
[Focus blocks, hours, timezone truths]
## Changelog
[2-3 honest entries — growth as version notes]
Quality Checks
Anti-Patterns
Related
[[the-understudy]] is how an AI learns your inside; this is how humans call
your outside. [[working-agreements]] for the team-level contract;
[[onboarding-plan]] to slot this into a new joiner's week one.
Example Trigger Phrases
- "Onboard to a new team."
- "Report arrives."
- "Write my README/user manual."
1---2name: api-for-yourself3description: "Publish 'how to work with me' as a literal API spec — endpoints (what to ask me for and what you'll get back), rate limits (meeting and interrupt tolerance), error codes (what happens when you surprise me Friday 5pm), auth (how to earn trust), and a changelog. Use when onboarding to a new team, when a new manager or report arrives, for a team working-styles session, or 'write my README/user manual'. Produces a personal API spec that's genuinely funny and secretly the best onboarding doc on the team."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/api-for-yourself7---89# API For Yourself Skill1011"User manual for me" documents have existed for years and mostly read like12horoscopes ("I value transparency"). The API-spec format fixes them by force:13an endpoint must say what you send and what comes back; a rate limit must be a14number; an error code must name the actual failure behaviour. The joke is the15format — the payload is real self-knowledge, and the test of every line is16*would a new teammate behave differently after reading it?* Deadpan technical17voice, honest contents, one page.1819## What This Skill Produces2021- A **personal API spec**: endpoints, request formats, rate limits, error22 codes, auth & scopes, dependencies, scheduled maintenance, changelog —23 in deadpan OpenAPI-ish style24- A **quickstart** at the top: the three calls that cover 90% of integrations25 with this human26- Optionally a **team version**: specs for a whole team session, plus the27 facilitation note for running it as an exercise2829## Required Inputs3031Ask for (if not already provided):32- How people should bring them things: channel preferences, context depth33 (one-liner or brief?), and what makes a request instantly workable vs34 instantly annoying35- Real capacity: meeting tolerance per day, focus blocks, response-time honest36 averages by channel37- Actual failure modes, told honestly: what happens when they're surprised38 late Friday, overloaded, given vague asks, or micromanaged39- What earns trust and what burns it; energy sources and drains; current40 quirks a teammate would discover in week three anyway4142## Process43441. **Interview past the horoscope.** For every generic answer ("I like45 directness"), push for the behavioural version: what does a *well-formed46 request* actually contain? What's the observable symptom when it's47 missing? The spec is built from behaviours, not values.482. **Design the endpoints** — the 4–6 things people actually come to this49 person for. Each gets: method + path (`POST /decisions`), request body50 (what to include), response (what they'll get and by when), and the errors51 it can throw. Include one honest deprecated endpoint (`/status-meetings —52 deprecated, use async /updates instead`).533. **Publish real numbers.** Rate limits with actual figures ("3 meetings/day54 before response quality degrades — 429 after that"), response-time SLAs by55 channel that match reality, scheduled maintenance (focus blocks, the school56 run, timezone). A limit without a number is a mood.574. **Write error codes as self-knowledge.** The funniest section and the most58 useful: `429 Too Many Meetings` (symptom: monosyllabic replies; retry:59 tomorrow morning) · `400 Vague Request` (returns clarifying questions, not60 work) · `503 Friday 5pm Surprise` (accepted but not processed until Monday;61 don't resend). Each code: symptom, what NOT to do, the retry strategy.625. **Auth, changelog, quickstart.** Auth: how trust levels are earned and what63 each unlocks (scope: `direct-feedback` granted after…). Changelog: 2–364 honest entries ("v3.1: no longer needs to win every argument — patched65 after 2024 retro"). Quickstart on top: the three most-used calls, copy-paste66 ready.6768## Output Format6970```71# [Name] API — v[X.Y]72> One-line summary of what this human is for.7374## Quickstart75[The 3 calls covering 90% of use]7677## Endpoints78### POST /[thing]79Request: … · Response (SLA): … · Errors: [codes]8081## Rate limits82[Real numbers: meetings, interrupts, context switches]8384## Error codes85| Code | Trigger | Symptom you'll observe | Retry strategy |8687## Auth & scopes88[How trust is earned; what each level unlocks]8990## Scheduled maintenance91[Focus blocks, hours, timezone truths]9293## Changelog94[2-3 honest entries — growth as version notes]95```9697## Quality Checks9899- [ ] Every line passes the behaviour test: a new teammate would act100 differently having read it — zero horoscope lines survive101- [ ] Rate limits and SLAs carry real numbers the person will actually honour102- [ ] At least one error code and one changelog entry required genuine honesty103 (a flaw admitted, a patch noted) — that's what makes readers trust the104 rest105- [ ] The joke never outruns the information: deadpan format, true payload106- [ ] One page; the quickstart works standalone if that's all anyone reads107108## Anti-Patterns109110- [ ] Do not write requirements-for-others disguised as self-documentation —111 it's an API you offer, not an SLA you impose; tone stays "here's how to112 get the best out of me"113- [ ] Do not fake quirks for comedy or hide real ones for image — week three114 reveals everything anyway115- [ ] Do not ship without the errors section; specs with only happy paths are116 marketing117- [ ] Do not let it ossify — the changelog implies maintenance; suggest a118 re-version at role changes119120## Related121122[[the-understudy]] is how an AI learns your inside; this is how humans call123your outside. [[working-agreements]] for the team-level contract;124[[onboarding-plan]] to slot this into a new joiner's week one.125126## Example Trigger Phrases127128- "Onboard to a new team."129- "Report arrives."130- "Write my README/user manual."