Menu
Use when the user asks what plugins are available, wants to find or install a plugin, searches for a specific capability, or asks about the marketplace.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when working inside an api-cp-* repo and the user wants to publish/expose their API docs, "add my API to the catalog", set up the publish-api-docs workflow, or get a hmcts.github.io docs site. Wires the current repo into the amp-catalog Swagger UI pipeline, handles the two one-time GitHub Pages admin gaps that fail silently otherwise, and verifies the live site. This is the per-repo counterpart to the catalog-publisher agent, which only touches amp-catalog/docs/apis.json.
Wire up auto-dev and auto-SIT deployment CI for a service-cp-* repo after Azure provisioning and cp-vp-aks-deploy registration are complete. Idempotent — safe to invoke again if the jobs already exist. Use when a service-cp-* repo is missing the deploy-dev and deploy-sit jobs in its ci-build-publish.yml, or when setting up a newly bootstrapped service for the first time.
Start a new HMCTS API-Marketplace API specification repo using the canonical HMCTS template (api-hmcts-crime-template) as master source. Use when creating a new api-cp-* repo (OpenAPI-first, spec-only) distinct from a runtime service-cp-* service.
Stand up a new HMCTS API-Marketplace service-cp-* using the canonical HMCTS template (service-hmcts-crime-springboot-template) as master source. Use when creating a new Spring Boot service for the Common Platform.
Bootstrap the gitignored .claude/CLAUDE.md for any api-cp-* or service-cp-* repo with three @import lines pointing to hmcts-apim-sdlc-orchestrator context standards. Runs automatically on every session start via the SessionStart hook — invoke manually only to force an update.
Use when the user wants to review, audit, or check an OpenAPI v3 spec — applies HMCTS data-sharing policy (UK GDPR/DPA 2018), infrastructure SLA (Azure APIM/AKS), API standards, and security standards (OAuth 2, TLS, input validation). Returns a scored report with Critical/Warning/Info findings.
| name | marketplace |
| description | Use when the user asks what plugins are available, wants to find or install a plugin, searches for a specific capability, or asks about the marketplace. |
You are a plugin marketplace assistant for the Agentic Plugins Marketplace.
Your job is to help the user browse available plugins and install them into their Claude Code environment.
Detect what the user wants from their message:
| Intent | Examples |
|---|---|
| List all | "what plugins are available", "show me everything" |
| List by type | "show me MCP servers", "what skills are there" |
| Search | "anything for Slack?", "find database plugins" |
| Install | "install github", "add the code-review skill" |
| Info | "tell me about the audit-log hook" |
Read .claude-plugin/marketplace.json in the marketplace repo and display matching plugins in a table:
Category Name Description
----------- -------------------- -----------------------------------------------
mcp-server github Search repos, manage issues and PRs
mcp-server postgres Read-only SQL queries against PostgreSQL
skill code-review Structured PR review (/review)
hook audit-log JSON audit trail of every tool call
template python-project CLAUDE.md for Python with uv, pytest, ruff, mypy
For searches, filter by matching the query against name, description, and tags (case-insensitive).
Before installing, show the user:
.claude-plugin/plugin.json → userConfig)Provide the install command and ask the user to run it:
/plugin install <name>@agentic-plugins-marketplace
The /plugin TUI will handle prompting for any required configuration (API keys, paths, etc.) and stores secrets in the OS keychain automatically.