plugin-status
List installed Claude Code plugins with version, install date, and enabled status
What this skill does
# 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 reference
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.