service-catalog-entry
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.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill service-catalog-entry --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Service Catalog Entry Skill Produce a complete service catalog entry for a microservice or internal platform service — giving any engineer at the company the context they need to understand what the service does, how to depend on it, what its reliability characteristics are, and where to go when something goes wrong. A well-written catalog entry eliminates "who owns this?" and "is this safe to use?" questions that slow down teams depending on shared services. ## Required Inputs Ask for these if not already provided: - **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 ## Output Format --- # Service Catalog: [Service Name] > **[One sentence — what this service does for consumers, in plain language]** > >
- Required Inputs
- Output Format
- Identity
- What It Does
- Architecture Context
- System Diagram
- Who Depends on This Service
- What This Service Depends On
- Service Level Agreement
- Availability and Latency
- Support Tiers
- Maintenance Windows
- API Contract
- Authentication
What does the service-catalog-entry skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill service-catalog-entry --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.