Installing

The Claude plugin surface is evolving quickly. Verify these commands against the current Claude plugin documentation before filing a bug.

Add the marketplace and install

/plugin marketplace add b08x/ris_assist
/plugin install ris-assist@ris-assist

The repository is its own marketplace — .claude-plugin/marketplace.json at the root declares a single plugin sourced from plugins/ris-assist. There is nothing to build and no runtime dependency to install; the plugin is markdown and YAML.

What you get

Six slash commands, backed by four skills over a shared analyst persona:

First run

Run /setup before anything else. Every other skill reads the site profile it produces, and without one they fall back to generic templates labelled not yet tuned to this site.

The interview asks about your systems, named interfaces, escalation matrix, SLA tiers, identifier formats, and downtime procedures. It writes the result to a local path outside the plugin directory, so it survives plugin updates and never enters the repository.

Keep the site profile wherever your local secrets live. It contains real interface names, escalation contacts, and distribution lists — it is yours, not the plugin’s.

See Site profile setup for what the interview covers and how to edit a profile afterwards.

Verifying the install

Ask for something the plugin should decline:

/explain what is our escalation path

With no profile written, the expected response names the gap rather than inventing a plausible chain. If you get a confident answer describing an escalation path you never configured, something is wrong — that behaviour is the thing the guardrails exist to prevent.

Upgrading

Re-running /plugin install replaces the plugin directory. Your site profile is untouched because it lives outside it. If a schema field is added in a later version, /setup in edit mode fills the gap without re-running the whole interview.