samber/developer-platform-skills
api-status-communication
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.
Installation
npx skills add https://github.com/samber/developer-platform-skills
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Board meeting preparation, investor updates, and executive communication.
1.6K installsStructured messaging protocols for agent team communication including message type selection, p…
23 installsGuide technical communication for software developers.
4K installsUse when detecting ambiguous user intent, hedging language, open-ended framing, personal contex…
14 installsHelp users master professional writing to bridge gaps between stakeholders, scale their leaders…
2.2K installsExpert-level telecommunications systems, network management, billing, 5G, SDN, and telecom infr…
1.9K installsAlso in this package
Other skills from samber/developer-platform-skills · top by installs.
npx skills add samber/developer-platform-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.