Set up the AI plugins
The nullplatform AI plugins bring platform operations into your coding assistant (Claude Code, Kiro, Cursor, and others). You describe what you want in plain language and the plugin handles the rest: querying entities, paginating results, and calling the right API endpoints.
Every AI Ops feature starts here. Workflow authoring, checklist specs, governance sweeps, and troubleshooting sessions all begin with a plugin prompt, so setting the plugins up once unlocks everything that builds on them.
The plugins are open source and maintained at github.com/nullplatform/ai-plugins. The repository is the source of truth for the full plugin catalog and per-plugin documentation, which evolve faster than this page.
Before you start
- A coding assistant that supports plugins. The commands below use Claude Code; the same plugins also work with Kiro, Cursor, Factory AI, Codex CLI, and more
- A nullplatform API key. The role it needs depends on what you plan to do: Developer covers day-to-day
/np-developeroperations like deployments and scope changes, while organization-level configuration (categories, checklists, workflows) needs Admin or Ops
1. Install the plugins
Clone the plugin repository and install it:
git clone https://github.com/nullplatform/ai-plugins.git
cd ai-plugins
claude plugin install .
This installs the full nullplatform plugin suite. Once installed, slash commands like /np-governance (action items, workflows, checklists, and AI suggestions) and /np-developer (queries, deployments, scope operations, and diagnostics) become available inside any session. Browse the plugin catalog on GitHub for the complete, up-to-date list.
2. Configure your API key
Export your API key so the plugins can authenticate:
export NP_API_KEY=<your_api_key_here>
Your API key needs access to the accounts and namespaces you want to operate on. See API keys to create one.
3. Verify the setup
Start a session and type:
/np-developer show my latest deployments
The plugin queries your organization and lists the most recent deployments, with their application, scope, and status. An empty list is a valid response if nothing has been deployed yet.
If you get a list (or an empty list), the plugins are working. If you see an authentication error, double-check the NP_API_KEY variable.
Next steps
- Your first workflow: describe a hello world workflow, run it, and activate it
- Your first checklist: describe a two-item deploy gate and watch it govern a real deploy
- Detect stale applications with AI: find apps that haven't been deployed in over 90 days and open action items for them
- Track a runtime migration with Governance and Insights: flag every affected service and follow the migration in a dashboard
- Action items: what the plugins create and how teams work through it