backstage

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

5|Updated Mar 11, 2026

Search Tags:#yaml #metadata #developer portal #backstage #catalog-info.yaml #service onboarding

Ready to run

npx skills add https://github.com/SteveFeldman/agents-skills --skill backstage-stevefeldman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backstage
Source: https://github.com/SteveFeldman/agents-skills/tree/main/skills/backstage
Command: npx skills add https://github.com/SteveFeldman/agents-skills --skill backstage-stevefeldman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of creating and updating catalog-info.yaml files, ensuring your services are correctly registered and visible within the Backstage developer portal.

Core Features & Use Cases

Generate catalog-info.yaml: Create or update the core component definition for services, APIs, or libraries.
Standardize Metadata: Apply organization-specific annotations and links for discoverability and operational tooling.
Onboard Repositories: Quickly register new projects or services into the software catalog.
Use Case: You've just created a new microservice and need to add it to the Backstage catalog. This skill will generate the necessary catalog-info.yaml with all required annotations and links.

Quick Start

Use the backstage skill to generate a catalog-info.yaml file for a new service named 'user-profile-api' owned by the 'platform-eng' team.

Frequently Asked Questions about backstage

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

FAQPage Schema

How do I create a catalog-info.yaml file for onboarding a new microservice to Backstage?▼

Backstage catalog-info.yaml files require adherence to API versioning and component type definitions. You must apply organization-specific annotations and links for discoverability and operational tooling to ensure services are correctly registered in the software catalog.

Can I use this approach to register APIs and libraries, or is it limited to services?▼

You can register APIs, libraries, and services using catalog-info.yaml. The process supports onboarding various component types into the Backstage software catalog by configuring the appropriate metadata and component type definitions for developer portal visibility.

What is the best way to standardize metadata across multiple repositories in a Backstage developer portal?▼

To update an existing catalog-info.yaml for Backstage, modify the component definition to include new organization-specific annotations, links, and metadata. This updates service registration and maintains visibility within the developer portal software catalog.

Do I need to follow specific API versioning rules when generating a catalog-info.yaml file?▼

Yes, generating a catalog-info.yaml file requires adherence to Backstage API versioning and component type definitions. Following these rules ensures your service metadata is valid and properly registered within the software catalog.