skills.rest
tonone-ai
tonone-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pave-catalog

Catalog services, owners, dependencies, health, and documentation from repositories.

69|8|Updated Mar 16, 2026
Search Tags:#documentation#dependencies#catalog#service#inventory#backstage
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill pave-catalog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pave-catalog
Source: https://github.com/tonone-ai/tonone/tree/main/team/pave/skills/pave-catalog
Command: npx skills add https://github.com/tonone-ai/tonone --skill pave-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Service cataloging enables teams to quickly discover, understand, and manage the landscape of services, owners, dependencies, health status, and documentation.

Core Features & Use Cases

  • Inventory all services, frontends, workers, and infra components with owners and status
  • Map upstream/downstream dependencies and data stores for impact analysis
  • Set up a lightweight or Backstage-backed catalog with runbooks and API docs

Quick Start

Register a catalog by scanning repositories to enumerate services, owners, dependencies, and docs, then publish a catalog-info.yaml or Markdown catalog.

Frequently Asked Questions about pave-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a service catalog that maps dependencies and ownership?▼

Build a service catalog by scanning repositories to enumerate services, owners, dependencies, and docs, then publish a machine-readable catalog-info.yaml or Markdown catalog to enable discovery.

Does this service catalog tool work with both monorepos and polyrepos?▼

Yes, the service catalog tool works with both monorepos and polyrepos, inventorying services, frontends, workers, and infrastructure components to build a complete landscape view.

Can I integrate a Backstage catalog with API specs and runbooks?▼

Yes, you can set up a Backstage-backed catalog that integrates API specs, infrastructure configs, and runbooks to provide health visibility and reproducible documentation.

What is the best way to map upstream and downstream service dependencies?▼

The best way to map service dependencies is cataloging upstream and downstream connections alongside data stores, enabling impact analysis and complete visibility across all services.

How do I export a machine-readable service inventory for reproducible integrations?▼

Export a machine-readable service inventory by generating a catalog-info.yaml file during repository scans, satisfying requirements for explicit ownership and reproducible integrations.

When do I need a live service catalog for my infrastructure components?▼

You need a live service catalog when you require quick discovery of service health status, ownership, and documentation across multiple repositories to manage infrastructure effectively.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

component-boundary-ownership

Analyze deployment independence, team ownership, and coupling to define component boundaries.

Community
Advanced
SteveFeldmanSteveFeldman
5

backstage

Generate and update Backstage catalog-info.yaml files for services, APIs, and resources.

Community
Intermediate
fabricioctellesfabricioctelles
47

agent-ready-api-catalog

Publish an RFC 9727 API catalog at /.well-known/api-catalog.

Community
Intermediate
zzafergokzzafergok
1

markdown-to-html-skill

Convert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.

Community
Intermediate