Set up, diagnose, search, and operate Spotify Portal from Claude Code, Codex, and Cursor.

Highlights

• Set up the Portal CLI for the current coding-agent host.
• Diagnose plugin, CLI, authentication, and action readiness without changing state.
• Search the software catalog and technical documentation using natural language.
• Build concise service briefings covering ownership, health, incidents, and documentation.
• Discover and safely invoke Portal actions with help, dry-run, and confirmation safeguards.

Overview

Spotify Portal for Backstage is Spotify's managed internal developer portal. This plugin gives coding agents focused workflows for the Portal CLI.

The workflow skills are bundled as plugin behavior. They are not published or installed as standalone skill packages.

Installation

Claude Code

claude plugin marketplace add spotify/portal-ai-plugins
claude plugin install portal@portal

Start a new Claude Code session, then run:

/portal:setup

Codex

codex plugin marketplace add spotify/portal-ai-plugins
codex

Open /plugins, install Spotify Portal, start a new task, and ask:

Set up Spotify Portal for me.

Cursor

Register this GitHub repository in the Cursor team marketplace, then install Spotify Portal from Cursor Settings → Plugins.

Cursor uses the shared Portal CLI workflows.

Workflows

Claude Code exposes the plugin skills directly under the Portal namespace:

/portal:setup [instance-name or backend-url]
/portal:doctor [instance-name]
/portal:search <query>
/portal:service <service-name or entity-ref>
/portal:actions [action-id]

Codex and Cursor auto-discover the same workflows from the plugin skills.

Portal CLI

Claude Code, Codex, and Cursor use the shared Portal CLI workflows.

The workflows invoke the upstream CLI through:

npx @spotify/portal-cli <command>

Setup verifies the required auth, actions, owner, search, and service commands before continuing.