manage-software-catalog

Manage Backstage catalog entities like Components, APIs, and Groups.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/em-jones/staccato-toolkit --skill manage-software-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-software-catalog
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/manage-software-catalog
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill manage-software-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the management and evolution of your Backstage software catalog, ensuring accurate and up-to-date documentation of your software ecosystem.

Core Features & Use Cases

  • Entity Management: Create, update, and organize Components, APIs, Systems, Domains, Groups, and Users within Backstage.
  • Automation Guidance: Provides patterns and scripts for automatically generating catalog entities from code, infrastructure, and API definitions.
  • Use Case: When a new microservice is developed, use this Skill to define its Component entity, link it to its owning team (Group), and specify its dependencies and provided APIs, ensuring it's discoverable and well-documented in the catalog.

Quick Start

Use the manage-software-catalog skill to add a new component named 'user-profile-service' owned by the 'platform-team'.

Frequently Asked Questions about manage-software-catalog

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

FAQPage Schema
How do I organize Backstage software catalog entities like Components and APIs?

You can organize Backstage software catalog entities by defining and managing Components, APIs, Systems, Domains, Groups, and Users. This skill provides automation patterns to structure your software ecosystem for accurate discoverability.

What is the best way to automate Backstage catalog generation from code and infrastructure?

Automating Backstage catalog generation involves using provided scripts to extract entity definitions from dependency files, IaC, and API specifications. This ensures your catalog stays up-to-date without manual data entry.

Can I link a new microservice Component to its owning Group in Backstage?

Yes, you can link a new Component to its owning Group in Backstage. When defining a Component entity like 'user-profile-service', you specify the 'platform-team' Group to document ownership and dependencies.

Does this approach support generating catalog entries from API specifications?

Yes, generating catalog entries from API specifications is supported. The skill provides guidance and automation patterns to parse API definitions and automatically populate the corresponding Backstage entities.

How do I document software ecosystem dependencies using a Backstage software catalog?

Documenting software ecosystem dependencies in a Backstage software catalog requires mapping relationships between Components, APIs, and Systems. Defining these entity links ensures services are well-documented and easily discoverable.