/plugin-status
List installed Claude Code marketplace plugins with version, install date, and enabled status
$ npx -y skills add jmagly/aiwg --skill plugin-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/plugin-status
Context preview
The summary Claude sees to decide when to auto-load this skill.
List installed Claude Code marketplace plugins with version, install date, and enabled status
SKILL.md
plugin-status.SKILL.mdnamespace: aiwg
name: plugin-status
platforms: [all]
description: List installed Claude Code marketplace plugins with version, install date, and enabled status
Plugin Status
You list installed Claude Code marketplace plugins with their version, install date, and enabled status. In AIWG vocabulary, these are delivery wrappers around extension, addon, or framework payloads.
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**:
# 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 package name, version, install date, enabled status, and update availability.
Output Format
Installed Marketplace Packages (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**:
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**:
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**:
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**:
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 reference
Read more
namespace: aiwg name: plugin-status platforms: [all] description: List installed Claude Code marketplace plugins with version, install date, and enabled status
Plugin Status
You list installed Claude Code marketplace plugins with their version, install date, and enabled status. In AIWG vocabulary, these are delivery wrappers around extension, addon, or framework payloads.
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**:
# 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 package name, version, install date, enabled status, and update availability.
Output Format
Installed Marketplace Packages (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**:
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**:
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**:
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**:
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 reference
Multi-agent AI framework for Claude Code, Copilot, Cursor, Warp, and 6 more platforms 200+ agents, 109+ CLI commands, 400+ deployable agent/skill/command/rule artifacts, 8 core frameworks, 32 addons, and a 40-plugin Claude Code marketplace.
Repo: jmagly/aiwg
Other skills on aiwg.
- /agent-loop-ext
Crash-resilient external agent loop with state persistence and CI/CD integration
Open skill - /agent-loop
Detect requests for iterative autonomous agent loops and route to the appropriate loop executor
Open skill - /auto-test-execution
Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern
Open skill - /cross-task-learner
Enable agent loops to learn from similar past tasks and share patterns across loops
Open skill - /debug-memory
Query and manage the executable feedback debug memory
Open skill - /execute-feedback
Execute tests on generated code and iterate until passing
Open skill

