plugin-status
List installed Claude Code plugins with version, install date, and enabled status
Best use case
plugin-status is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
List installed Claude Code plugins with version, install date, and enabled status
Teams using plugin-status should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/plugin-status/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How plugin-status Compares
| Feature / Agent | plugin-status | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
List installed Claude Code plugins with version, install date, and enabled status
Which AI agents support this skill?
This skill is designed for Codex.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# Plugin Status
You list all installed Claude Code plugins with their version, install date, and enabled status.
## Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "what's installed?" → show all plugins
- "do I have the voice plugin?" → check if specific plugin is installed
- "is the SDLC plugin up to date?" → show installed version vs latest
- "what plugins does this project use?" → show plugin status
## Trigger Patterns Reference
| Pattern | Example | Action |
|---------|---------|--------|
| Status request | "plugin status" | Run `aiwg plugin-status` |
| List request | "show plugins" | Run `aiwg plugin-status` |
| List all | "list plugins" | Run `aiwg plugin-status` |
| What's installed | "what plugins are installed" | Run `aiwg plugin-status` |
| Check specific | "is voice@aiwg installed?" | Run `aiwg plugin-status voice@aiwg` |
| JSON output | "plugin status as JSON" | Run `aiwg plugin-status --json` |
| Outdated check | "are any plugins outdated?" | Run `aiwg plugin-status --check-updates` |
## Behavior
When triggered:
1. **Extract intent**:
- Is a specific plugin being queried, or is this a full list?
- Is the user checking for outdated versions?
- Is machine-readable output needed?
2. **Run the appropriate command**:
```bash
# List all installed plugins
aiwg plugin-status
# Check a specific plugin
aiwg plugin-status sdlc@aiwg
# Check for available updates
aiwg plugin-status --check-updates
# Machine-readable JSON output
aiwg plugin-status --json
```
3. **Report the result** — show plugin name, version, install date, enabled status, and update availability.
## Output Format
```
Installed Plugins (2)
sdlc@aiwg
Version: 2026.3.15
Installed: 2026-03-28
Status: enabled
Update: none (latest)
voice@aiwg
Version: 2026.2.10
Installed: 2026-02-14
Status: enabled
Update: 2026.3.15 available — run `aiwg install-plugin voice@aiwg --force`
```
## Examples
### Example 1: Check what is installed
**User**: "What plugins do I have installed?"
**Extraction**: Full plugin list
**Action**:
```bash
aiwg plugin-status
```
**Response**: "2 plugins installed: sdlc@aiwg v2026.3.15 (enabled, current), voice@aiwg v2026.2.10 (enabled, update available: v2026.3.15)."
### Example 2: Check a specific plugin
**User**: "Is the voice plugin installed and up to date?"
**Extraction**: Query for voice@aiwg specifically
**Action**:
```bash
aiwg plugin-status voice@aiwg
```
**Response**: "voice@aiwg v2026.2.10 is installed (enabled). Update available: v2026.3.15. Run `aiwg install-plugin voice@aiwg --force` to update."
### Example 3: Nothing installed
**User**: "Show plugins"
**Extraction**: Full plugin list
**Action**:
```bash
aiwg plugin-status
```
**Response**: "No plugins installed. Install one with `aiwg install-plugin <name>@aiwg`. Available: sdlc, voice, marketing, utils."
### Example 4: Check for updates
**User**: "Are any of my plugins out of date?"
**Extraction**: Update check requested
**Action**:
```bash
aiwg plugin-status --check-updates
```
**Response**: "1 update available: voice@aiwg 2026.2.10 → 2026.3.15. Run `aiwg install-plugin voice@aiwg --force` to update."
## References
- @$AIWG_ROOT/src/cli/handlers/utilities.ts — Command handler
- @$AIWG_ROOT/docs/cli-reference.md — CLI referenceRelated Skills
customize-status
Show current AIWG customization status — mode, source path, what you've customized vs upstream
uninstall-plugin
Remove a previously installed Claude Code plugin and unregister it from the local plugin registry
soul-status
Show SOUL.md enforcement state across all installed providers with quality check
rlm-status
Show status of RLM task tree execution
research-status
Show research corpus health and statistics
ralph-status
Check status of current or previous agent loop
project-status
Analyze project state from .aiwg/ artifacts and provide contextual status with recommended next steps
pipeline-status
Show status overview of all LLM inference pipelines in the current project
package-plugin
Bundle a single plugin into a distributable marketplace archive, validating metadata and optionally publishing
package-all-plugins
Batch package every plugin in the workspace in a single release-prep operation
marketing-status
Project directory path (default current directory)
install-plugin
Install plugins into Claude Code from the AIWG marketplace with registry lookup, download, and local deployment