How do I install the Backstage AI Catalog skill?

Run npx skillmds@latest add paulasilvatech/backstage-ai-catalog-2 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 AI 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 AI 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 AI Catalog free to use?

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

Who published Backstage AI Catalog?

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

Backstage AI Catalog by paulasilvatech

Name: Backstage AI Catalog
Author: paulasilvatech

Backstage AI Catalog

Install and use Backstage's AI catalog model for AiResource skills and rules plus mcp-server API entities, ownership, lifecycle, relationships, and source locations. Use when cataloging AI skills, governance rules, agents, or MCP servers.

File contents

Backstage AI catalog

Model AI context as governed catalog entities while keeping skill and rule content in its source repository.

When to invoke

"Catalog our AI skills and governance rules in Backstage."
"Register an MCP server as an API entity."
"Add the AiResource kind to Backstage."
"Model ownership and dependencies between AI resources."

Procedure

Confirm the target Backstage version and catalog backend mode.
Verify the current AI catalog documentation and package version.
Install @backstage/plugin-catalog-backend-module-ai-model in packages/backend and register the module through the backend system.
Model a skill or rule as kind: AiResource with lifecycle, owner, system, and type-specific fields.
Point backstage.io/source-location at the source skill or rule; do not copy its complete content into the entity.
Model an MCP server as kind: API, spec.type: mcp-server, with one or more explicit remotes.
Validate entity schemas, references, ownership, lifecycle, URLs, and catalog ingestion.
Protect internal or non-production MCP endpoints with repository policy and network controls.

Model boundaries

AiResource type skill may declare disciplines, categories, agents, and dependsOn.
AiResource type rule requires a category and rationale.
mcp-server is an API subtype and uses remotes, not an embedded OpenAPI definition.
Source content remains external and addressable through source-location annotations.

Output template

## Backstage AI catalog result

| Entity | Type | Owner | Source or remote | Validation |
| --- | --- | --- | --- | --- |

### Module
- Package:
- Backend registration:

Quality gate

The AI catalog module and target version are verified.
Every AI resource has stable identity, lifecycle, owner, and source location.
Skill dependencies and rule rationales are explicit.
MCP remotes use valid transport types and URLs.
Catalog ingestion validates the registered model.
Sensitive internal endpoints and credentials are not exposed.

References

AI in the Software Catalog

---name: backstage-ai-catalog-2description: Install and use Backstage's AI catalog model for AiResource skills and rules plus mcp-server API entities, ownership, lifecycle, relationships, and source locations. Use when cataloging AI skills, governance rules, agents, or MCP servers.---# Backstage AI catalogModel AI context as governed catalog entities while keeping skill and rule content in its sourcerepository.## When to invoke- "Catalog our AI skills and governance rules in Backstage."- "Register an MCP server as an API entity."- "Add the AiResource kind to Backstage."- "Model ownership and dependencies between AI resources."## Procedure1. Confirm the target Backstage version and catalog backend mode.2. Verify the current AI catalog documentation and package version.3. Install `@backstage/plugin-catalog-backend-module-ai-model` in `packages/backend` and register the module through the backend system.4. Model a skill or rule as `kind: AiResource` with lifecycle, owner, system, and type-specific fields.5. Point `backstage.io/source-location` at the source skill or rule; do not copy its complete content into the entity.6. Model an MCP server as `kind: API`, `spec.type: mcp-server`, with one or more explicit `remotes`.7. Validate entity schemas, references, ownership, lifecycle, URLs, and catalog ingestion.8. Protect internal or non-production MCP endpoints with repository policy and network controls.## Model boundaries- `AiResource` type `skill` may declare disciplines, categories, agents, and `dependsOn`.- `AiResource` type `rule` requires a category and rationale.- `mcp-server` is an API subtype and uses `remotes`, not an embedded OpenAPI definition.- Source content remains external and addressable through source-location annotations.## Output template```markdown## Backstage AI catalog result| Entity | Type | Owner | Source or remote | Validation || --- | --- | --- | --- | --- |### Module- Package:- Backend registration:```## Quality gate- [ ] The AI catalog module and target version are verified.- [ ] Every AI resource has stable identity, lifecycle, owner, and source location.- [ ] Skill dependencies and rule rationales are explicit.- [ ] MCP remotes use valid transport types and URLs.- [ ] Catalog ingestion validates the registered model.- [ ] Sensitive internal endpoints and credentials are not exposed.## References- [AI in the Software Catalog](https://backstage.io/docs/ai/ai-in-the-catalog)

Frequently asked questions