How do I install the Backstage Catalog skill?

Run npx skillmds@latest add paulasilvatech/backstage-catalog-3 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

File contents

Backstage Software Catalog

Conventions

Declare apiVersion, kind, kebab-case metadata.name, a useful description, and a resolvable spec.owner.
Use lowercase kebab-case tags and stable namespaces; avoid encoding environments or mutable deployment details in entity identity.
Express relationships with supported entity references and verify referenced owners, systems, components, APIs, resources, and locations exist.
Keep github.com/project-slug, source locations, and TechDocs annotations pointed at real repositories and tracked paths.
Use ohorizons.ai/* only for Open Horizons agent metadata; do not invent competing top-level fields.
Keep examples ingestible and sanitized because templates and local catalog bootstrap consume them.
Avoid duplicate entity triplets of kind, namespace, and name.

Verification

Catalog validation resolves owners and relation targets.
Location targets and source annotations exist.
Entity examples contain no credentials, tenant IDs, or customer-specific values.

Do / Do Not

Do	Do not
Preserve stable entity identity, ownership, and resolvable relations.	Create duplicate entity triplets or dangling references.
Validate locations and sanitize examples.	Put credentials, tenant IDs, or customer data in catalog files.

Checklist Before Opening a PR

The change matches this instruction's applyTo scope.
Owners, relations, locations, and source annotations resolve.
Entity identity remains unique and stable.
Catalog validation passes and examples are sanitized.
No unrelated edits or unresolved placeholders remain.

---name: backstage-catalog-3description: Use when editing Backstage catalog entities, ownership, relations, annotations, or discovery examples.---# Backstage Software Catalog## Conventions- Declare `apiVersion`, `kind`, kebab-case `metadata.name`, a useful description, and a resolvable `spec.owner`.- Use lowercase kebab-case tags and stable namespaces; avoid encoding environments or mutable deployment details in entity identity.- Express relationships with supported entity references and verify referenced owners, systems, components, APIs, resources, and locations exist.- Keep `github.com/project-slug`, source locations, and TechDocs annotations pointed at real repositories and tracked paths.- Use `ohorizons.ai/*` only for Open Horizons agent metadata; do not invent competing top-level fields.- Keep examples ingestible and sanitized because templates and local catalog bootstrap consume them.- Avoid duplicate entity triplets of `kind`, `namespace`, and `name`.## Verification- Catalog validation resolves owners and relation targets.- Location targets and source annotations exist.- Entity examples contain no credentials, tenant IDs, or customer-specific values.## Do / Do Not| Do | Do not || --- | --- || Preserve stable entity identity, ownership, and resolvable relations. | Create duplicate entity triplets or dangling references. || Validate locations and sanitize examples. | Put credentials, tenant IDs, or customer data in catalog files. |## Checklist Before Opening a PR- [ ] The change matches this instruction's `applyTo` scope.- [ ] Owners, relations, locations, and source annotations resolve.- [ ] Entity identity remains unique and stable.- [ ] Catalog validation passes and examples are sanitized.- [ ] No unrelated edits or unresolved placeholders remain.

Frequently asked questions

Backstage Catalog