How do I install the Backstage Catalog skill?

Run npx skillmds@latest add paulasilvatech/backstage-catalog in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backstage Catalog safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backstage Catalog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backstage Catalog free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backstage Catalog?

paulasilvatech (@paulasilvatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backstage Catalog by paulasilvatech

Name: Backstage Catalog
Author: paulasilvatech

Backstage Catalog

Model, register, discover, validate, and troubleshoot Backstage Software Catalog entities, providers, processors, ownership, relations, locations, and lifecycle. Use when handling catalog-info YAML, entity ingestion, org discovery, duplicate entities, or catalog governance.

File contents

Backstage Software Catalog

Treat the catalog as a governed model whose declarative source remains with the systems it describes.

When to invoke

"Create or validate catalog-info.yaml."
"Configure GitHub organization discovery."
"Why is this entity missing or duplicated?"
"Model systems, APIs, resources, groups, and ownership."

Procedure

Detect the repository mode, Backstage version, catalog providers, processors, and custom kinds.
Inventory entity sources and determine which source is authoritative for each entity.
Model stable identity, namespace, kind, type, lifecycle, owner, system, domain, APIs, resources, and relations.
Keep catalog-info.yaml with the owning code repository when code is the source of truth.
Configure locations or providers with bounded filters, schedules, timeouts, and credentials from integrations or secret storage.
Validate YAML, entity schemas, references, ownership, and ingestion logs.
Diagnose collisions, orphaning, refresh failures, provider rate limits, or processor errors before changing source records.
Report entity counts or examples without exporting sensitive annotations or provider tokens.

Catalog criteria

Entity names and namespaces are stable and unambiguous.
Every production entity has an accountable owner.
Relations use resolvable entity references.
Provider and static-location sources do not duplicate the same entities.
Deprecation and orphan status are explicit lifecycle signals, not cleanup shortcuts.

Output template

## Backstage catalog result

**Source of truth:** <provider, location, or repository file>

| Entity or provider | Owner | Validation | Status |
| --- | --- | --- | --- |

### Findings
- <duplicate, missing relation, ownership, ingestion, or schedule finding>

Quality gate

The authoritative entity source is explicit.
Names, kinds, namespaces, types, lifecycle, and owners are valid.
Relations resolve and discovery sources do not duplicate entities.
Provider schedules and filters are bounded.
Ingestion or catalog validation evidence is recorded.
No credentials or sensitive integration values are stored in entity YAML.

---name: backstage-catalogdescription: Model, register, discover, validate, and troubleshoot Backstage Software Catalog entities, providers, processors, ownership, relations, locations, and lifecycle. Use when handling catalog-info YAML, entity ingestion, org discovery, duplicate entities, or catalog governance.---# Backstage Software CatalogTreat the catalog as a governed model whose declarative source remains with the systems itdescribes.## When to invoke- "Create or validate catalog-info.yaml."- "Configure GitHub organization discovery."- "Why is this entity missing or duplicated?"- "Model systems, APIs, resources, groups, and ownership."## Procedure1. Detect the repository mode, Backstage version, catalog providers, processors, and custom kinds.2. Inventory entity sources and determine which source is authoritative for each entity.3. Model stable identity, namespace, kind, type, lifecycle, owner, system, domain, APIs, resources, and relations.4. Keep `catalog-info.yaml` with the owning code repository when code is the source of truth.5. Configure locations or providers with bounded filters, schedules, timeouts, and credentials from integrations or secret storage.6. Validate YAML, entity schemas, references, ownership, and ingestion logs.7. Diagnose collisions, orphaning, refresh failures, provider rate limits, or processor errors before changing source records.8. Report entity counts or examples without exporting sensitive annotations or provider tokens.## Catalog criteria- Entity names and namespaces are stable and unambiguous.- Every production entity has an accountable owner.- Relations use resolvable entity references.- Provider and static-location sources do not duplicate the same entities.- Deprecation and orphan status are explicit lifecycle signals, not cleanup shortcuts.## Output template```markdown## Backstage catalog result**Source of truth:** <provider, location, or repository file>| Entity or provider | Owner | Validation | Status || --- | --- | --- | --- |### Findings- <duplicate, missing relation, ownership, ingestion, or schedule finding>```## Quality gate- [ ] The authoritative entity source is explicit.- [ ] Names, kinds, namespaces, types, lifecycle, and owners are valid.- [ ] Relations resolve and discovery sources do not duplicate entities.- [ ] Provider schedules and filters are bounded.- [ ] Ingestion or catalog validation evidence is recorded.- [ ] No credentials or sensitive integration values are stored in entity YAML.

Frequently asked questions