Agent skill

API For Yourself

by mohitagw15856 in mohitagw15856/pm-claude-skills

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…

MITAuto-check passedBackend & APIs

Install API For Yourself

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill api-for-yourself -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills api-for-yourself --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/api-for-yourself .claude/skills/api-for-yourself && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
api-for-yourself
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
659 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: Interview past the horoscope. For every… → Design the endpoints — the 4–6 things… → Publish real numbers. Rate limits with… → …
  • Onboarding to a new team
  • SKILL.md covers What This Skill Produces, Required Inputs, Process and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

API For Yourself is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering OpenAPI specifications, Rate limiting and Technical writing. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Onboarding to a new team
  • For a team working-styles session
  • Write my README/user manual

Example prompts

  • “how to work with me”
  • “write my README/user manual”
  • “/api-for-yourself”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Interview past the horoscope. For every generic answer ("I like
  2. Design the endpoints — the 4–6 things people actually come to this
  3. Publish real numbers. Rate limits with actual figures ("3 meetings/day
  4. Write error codes as self-knowledge. The funniest section and the most
  5. Auth, changelog, quickstart. Auth: how trust levels are earned and what

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

API For Yourself loads about 1.4k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 659 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~130
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 659 words, ~1,418 tokens.

Download SKILL.mdSave it as .claude/skills/api-for-yourself/SKILL.md (or your agent's skills folder).
name
api-for-yourself
description
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.

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

  1. 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.
  2. 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).
  3. 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.
  4. 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.
  5. 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.
Show full SKILL.md (201 more words)Show less

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

  • Every line passes the behaviour test: a new teammate would act differently having read it — zero horoscope lines survive
  • Rate limits and SLAs carry real numbers the person will actually honour
  • At least one error code and one changelog entry required genuine honesty (a flaw admitted, a patch noted) — that's what makes readers trust the rest
  • The joke never outruns the information: deadpan format, true payload
  • One page; the quickstart works standalone if that's all anyone reads

Anti-Patterns

  • Do not write requirements-for-others disguised as self-documentation — it's an API you offer, not an SLA you impose; tone stays "here's how to get the best out of me"
  • Do not fake quirks for comedy or hide real ones for image — week three reveals everything anyway
  • Do not ship without the errors section; specs with only happy paths are marketing
  • Do not let it ossify — the changelog implies maintenance; suggest a re-version at role changes

[[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."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/api-for-yourself of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

API For Yourself next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

API For Yourself compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
API For Yourself this skillmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT
Docs Interfacesjh941213/my-cc-harness126—~863Automated safety check: NotesNone
Documentationaiskillstore/marketplace4301 repos~2.7kAutomated safety check: PassNone
B24phpsdk Maintainerbitrix24/b24phpsdk102—~10kAutomated safety check: NotesMIT
Ramp Upgrade Migrationjeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
DocsInsForge/InsForge13k—~761Automated safety check: PassApache-2.0

Similar skills

  • Docs Interfaces

    jh941213/my-cc-harness

    Generate interface/API docs — OpenAPI 3.1/AsyncAPI 3.0 specs, API topology diagrams, interface flow (sequence) diagrams, API changelog.

    126 GitHub stars~863 tokensUpdated 2 mo ago
    Backend & APIsAuto-check: notes
  • Documentation

    aiskillstore/marketplace

    Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation.

    430 GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed
  • B24phpsdk Maintainer

    bitrix24/b24phpsdk

    A skill your agent uses whenever working with GitHub issues in the bitrix24/b24phpsdk repository: creating new issues, reading existing ones, planning implementation from an issue, referencing an…

    102 GitHub stars~10k tokensUpdated 9 days ago
    Backend & APIsAuto-check: notes
  • Ramp Upgrade Migration

    jeremylongshore/tons-of-skills-marketplace

    Upgrade a Ramp integration across API, schema, scope, endpoint, or behavior changes using impact analysis, dual verification, and reversible rollout.

    2.8k GitHub stars~1.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Docs

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's product documentation in this repository.

    13k GitHub stars~761 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • API Design

    WrongStack/WrongStack

    A skill your agent uses when designing, implementing, or reviewing an HTTP API — endpoints, request and response shapes, errors, pagination, versioning, and authorization.

    370 GitHub stars~1.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about API For Yourself

What does API For Yourself do?

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…. API For Yourself is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use API For Yourself?

API For Yourself fits situations like: onboarding to a new team; for a team working-styles session; write my README/user manual.

How do I install API For Yourself in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill api-for-yourself -a claude-code`. Or copy the skill folder (skills/api-for-yourself in mohitagw15856/pm-claude-skills) into .claude/skills/api-for-yourself in your project. Claude Code loads it when a task matches its description.

How do I install API For Yourself in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill api-for-yourself -a codex`. Or copy the skill folder (skills/api-for-yourself in mohitagw15856/pm-claude-skills) into .agents/skills/api-for-yourself in your project. Codex loads it when a task matches its description.

Can I use API For Yourself in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill api-for-yourself -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-for-yourself, .gemini/skills/api-for-yourself, .github/skills/api-for-yourself and .opencode/skills/api-for-yourself in your project.

What does API For Yourself need to run?

SKILL.md names no scripts, command-line tools or credentials: API For Yourself is instructions for the agent only.

Does API For Yourself access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is API For Yourself safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does API For Yourself use?

API For Yourself is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does API For Yourself use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to API For Yourself?

Skills that share tags, products or a category with API For Yourself: Docs Interfaces (jh941213/my-cc-harness, 126 stars), Documentation (aiskillstore/marketplace, 430 stars), B24phpsdk Maintainer (bitrix24/b24phpsdk, 102 stars) and Ramp Upgrade Migration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains API For Yourself?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.