api-status-communication Skill (samber): Status Pages and Incidents

Makes Claude design how your API platform tells developers about incidents, from status-page setup to postmortems and maintenance notices.

Installs: 9.6K; on skills.sh
Stars: 9; on GitHub
Files: 4; besides SKILL.md
Updated: Nov 2026; last repo commit

api-status-communication makes Claude design the status and incident side of an API platform. It covers component and status modeling, wiring the page to monitoring, push and pull channels, incident update cadence, public postmortems, SLA reporting and maintenance notices.

It starts when you mention a status page, Statuspage, incident updates, uptime or SLA reporting, postmortems or scheduled maintenance. Claude asks 7 opening questions, then works through 7 steps. The skill bundles no scripts.

Good for

API platform teams with no status page or one that stays green during outages
Engineers writing their first public postmortem
Support and DevRel leads planning maintenance announcements

Install api-status-communication

Claude Code

Copy this prompt.

Install the api-status-communication skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-platform-skills
/plugin install developer-platform-skills@developer-platform-skills

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route, not both, or you get every skill twice. The README asks you to install the whole set, not just api-status-communication, because the skills reference each other and a lone skill leaves those hand-offs with nowhere to go. The plugin adds all 61 skills in the repo (counted from the repo tree). Its manifests list no hooks, agents or MCP servers.

From the project README. Source.

What's in the skill

When it loads

Design how an API platform communicates status and incidents to external consumers - status-page modeling (the four-stage incident lifecycle, degraded/partial/major component semantics, component granularity), monitoring-driven status instead of a hand-flipped green light, pull and push channels, incident-update cadence and templates, public postmortems for a developer audience, public SLA/SLO reporting, and maintenance-window notices. Use whenever the user mentions a status page, Statuspage, incident updates, uptime or SLA reporting, postmortems, or scheduled maintenance - even if they never say "status communication". Do NOT use for deprecation and breaking-change notices - use samber/developer-platform-skills@api-versioning-policy instead.

Sections in SKILL.md

Clarifying questions
Reader roles
Workflow
1. Model statuses and components
2. Wire status to monitoring
3. Choose the channels
4. Design the incident-lifecycle communication practice
5. Set the postmortem policy
6. Publish SLA/SLO reporting
7. Set maintenance-window conventions
Failure modes
Measurement
Invocation examples
References

Key facts

Author: Samuel Berthe
License: MIT
Version: 1.0.1
Installs on skills.sh: 9,597 (Nov 2, 2026)
GitHub stars: 9 (Nov 2, 2026)
skills.sh audits: Gen Agent Trust Hub pass; Socket pass; Snyk pass (Nov 2, 2026)
Last repo commit: Nov 1, 2026
What installs: 5 files including SKILL.md: evals/evals.json and 3 reference files. It bundles no scripts.
Needs: The other skills in the repo; the README says to install the whole set
Works in: Claude Code, Claude.ai, Codex, Cursor, Gemini CLI, and other agents through the skills CLI

What it includes

Asks 7 questions in one batch before designing anything.
Try: “Design a status page for our public API - today we only tweet when something breaks.”
Opening questions
Sets the four incident statuses and what degraded, partial and major mean.
Model statuses and components
Ties the page to health checks so no person decides when customers are told.
Wire status to monitoring
Pairs the pull page with push options: email, RSS, webhook and SMS.
Choose the channels
Runs every incident through the four statuses using Atlassian's five practices.
Design the incident-lifecycle practice
Decides whether to publish postmortems; the sourced default leans toward publishing.
Set the postmortem policy
Keeps SLI, SLO and SLA as distinct terms in everything public.
Publish SLA/SLO reporting
Scales notice for planned work, within a 24-hour to 2-week horizon.
Set maintenance-window conventions
Advises saving decisions to developer-platform-context.md when memory is a file.
Write · Remember decisions (optional)

From the official docs

Permissions

Low risk

This skill is written advice that bundles no scripts. The one thing it may write is a decisions file, so check what Claude saves.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It may save decisions to a file
SKILL.md advises using developer-platform-context.md when memory lives in a file, and calls it an advisory reference. Check or delete that file if you do not want decisions kept. github.com
The plugin route adds all 61 skills
The README asks you to install every skill in the repo, and the repo has 61. The plugin manifests list no hooks, agents or MCP servers, and the repo tree holds none. github.com
Folder holds Markdown and one JSON file
This skill's folder has 5 files: SKILL.md, evals/evals.json and 3 reference files. It has no .py, .sh or .js file. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	No read-only setting is documented. Decline the memory-file suggestion if you want no files written.
Scopes	Asks you opening questions and works from your answers and anything you share, such as specs or docs May save settled decisions to a file named developer-platform-context.md if your memory lives in a file

Questions

How do I install api-status-communication?

Use the install box above. The README asks you to install all 61 skills in the repo, not just this one, because the skills point to each other. In Claude Code that is the plugin route, and elsewhere the skills CLI or the client's own route installs the set.

Does api-status-communication work in Claude.ai, Codex or Cursor?

The README documents installs for Claude.ai, Claude Code, Codex, Cursor and Gemini CLI. It also lists the skills CLI, which it calls universal for Agent Skills-compatible tools. The Claude.ai route adds the whole repo as a plugin marketplace.

Does it need an API key or any setup?

SKILL.md sets no environment variable and the folder bundles no scripts. It does ask for details of your own API or product in its opening questions.

Is api-status-communication safe to use?

The folder holds Markdown and one JSON file, and no scripts. SKILL.md does suggest saving settled decisions to developer-platform-context.md when your memory lives in a file, so check what Claude writes. Our advice: treat the design it produces as a draft for your team to review before you publish it.

api-status-communication vs api-versioning-policy?

This skill owns notice for planned maintenance, from 24 hours to 2 weeks ahead. SKILL.md hands deprecation and breaking-change notices, which run 6 to 12 months, to api-versioning-policy.

Should we publish postmortems?

SKILL.md calls it a deliberate decision that touches legal exposure, trust and reliability culture. Its sourced default for developer platforms leans toward publishing anyway, and it cites Google SRE's view that sharing a postmortem with customers multiplies its value.

Information

updated Nov 2, 2026

Repository: samber/developer-platform-skills
Folder: skills/api-status-communication

samber/developer-platform-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6

README · github.com
api-status-communication SKILL.md · github.com
api-status-communication folder · github.com
api-versioning-policy SKILL.md · github.com
marketplace.json · github.com
plugin.json · github.com