SC
Service Catalog Entry
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Write a service catalog entry for a microservice or internal platform service — covering service identity, purpose, architecture context, SLAs, API contract summary, data classification, dependencies, operational runbooks, and known limitations. Use when asked to document a service for an internal developer portal, write a service README for a platform catalog, create a service overview page, or onboard a new service to a service registry. Produces a complete service catalog entry suitable for an internal developer portal or wiki.
What to give it
▸Service name — the canonical identifier used in code, monitoring, and deployments
▸Team and owner — team name, tech lead name, and on-call contact
▸Architecture overview — what the service does, what calls it, and what it calls
▸SLA requirements — availability target, latency SLO, support tier, and maintenance window
▸Key APIs — the most important endpoints other teams use (method, path, brief description)
▸Data handled — what data the service stores or processes, sensitivity classification, retention
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓"What It Does" is written without jargon — a new engineer from another team can understand it in under 2 minutes
✓SLO targets are specific numbers agreed with stakeholders — not aspirational or copied from a template
✓All direct upstream consumers are listed in the "Who Depends on This" table — no omissions
✓API error codes are accurate and tested — not aspirational documentation
✓Known limitations are honest — nothing is glossed over to make the service look better than it is
✓All runbook links are live — not broken references or TODO placeholders
✓Data classification includes retention period and encryption status — not just sensitivity level
✓The entry has been reviewed by at least one consumer team to confirm it matches their experience of the service
⚠️ What it refuses to do
Do not write aspirational SLO targets — targets must be agreed with stakeholders and based on historical data, not copied from a template
Do not leave runbook links as TODO placeholders — broken or missing links make the catalog entry worse than useless during an incident
Do not omit the "Known Limitations" section to make the service look better — undisclosed limitations cause incorrect integrations and downstream incidents
Do not list API error codes without testing them — aspirational error documentation misleads consumers
Do not write the "What It Does" section with jargon — a new engineer from another team must understand it in under 2 minutes
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="service-catalog-entry"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Service Catalog Entry is one of 1098 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog