/install-plugin
Install Claude Code marketplace plugins or route local/Git wrappers through the supported package workflow
$ npx -y skills add jmagly/aiwg --skill install-plugin --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
/install-plugin
Context preview
The summary Claude sees to decide when to auto-load this skill.
Install Claude Code marketplace plugins or route local/Git wrappers through the supported package workflow
SKILL.md
install-plugin.SKILL.mdnamespace: aiwg
name: install-plugin
platforms: [all]
description: Install Claude Code marketplace plugins or route local/Git wrappers through the supported package workflow
Install Plugin
You install a Claude Code marketplace plugin. In AIWG vocabulary, a plugin is a delivery wrapper around an extension, addon, or framework, not a separate content type. You handle registry lookup, download, and local deployment.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "I want the SDLC plugin" → install sdlc@aiwg
- "add the voice bundle" → install voice@aiwg
- "get me the marketing kit" → install marketing@aiwg
- "set up the testing tools" → install utils@aiwg
Trigger Patterns Reference
| Pattern | Example | Action | |---------|---------|--------| | Install plugin | "install plugin sdlc@aiwg" | Run `aiwg install-plugin sdlc@aiwg` | | Add plugin | "add plugin voice@aiwg" | Run `aiwg install-plugin voice@aiwg` | | Plugin install | "plugin install marketing@aiwg" | Run `aiwg install-plugin marketing@aiwg` | | Claude Code plugin | "install claude code plugin utils" | Run `aiwg install-plugin utils@aiwg` | | Dry run | "show me what installing sdlc would do" | Run `aiwg install-plugin sdlc@aiwg --dry-run` | | Specific version | "install sdlc version 2026.3.0" | Run `aiwg install-plugin sdlc@aiwg@2026.3.0` | | Local wrapper | "install this local plugin wrapper" | Run `aiwg install <path> --dry-run`, then `aiwg use <plugin-id>` | | Git wrapper | "install this plugin Git URL" | Run `aiwg install <git-url> --dry-run`, then `aiwg use <plugin-id>` |
Behavior
When triggered:
1. **Extract intent**:
- Which plugin is being requested? (name and optional `@scope`)
- Is a specific version mentioned?
- Is this a dry run?
2. **Run the appropriate command**:
# Install from AIWG marketplace (default scope)
aiwg install-plugin sdlc@aiwg
aiwg install-plugin voice@aiwg
aiwg install-plugin marketing@aiwg
aiwg install-plugin utils@aiwg
# Install a specific version
aiwg install-plugin sdlc@aiwg@2026.3.0
# Preview what would be installed
aiwg install-plugin sdlc@aiwg --dry-run
# Force reinstall even if already installed
aiwg install-plugin sdlc@aiwg --force
# Standalone local/Git wrappers use the package installer, not the legacy
# manifest-only install-plugin backend.
aiwg install ./path/to/wrapper --dry-run
aiwg install https://example.invalid/owner/wrapper.git --dry-run
aiwg use <plugin-id>
3. **Report the result** — name the installed marketplace wrapper and confirm which agents, skills, commands, and rules were deployed and where.
Available Marketplace Packages
| Package | Payload | Use Case | |--------|----------|----------| | `sdlc@aiwg` | 58 agents, 42 commands, SDLC workflows | Full software development lifecycle | | `voice@aiwg` | Voice profiles, soul system | Content style and persona management | | `marketing@aiwg` | Marketing agents, campaigns, media | Marketing operations framework | | `utils@aiwg` | Core utility skills and rules | Foundational cross-framework utilities |
What Happens on Install
1. Delivery manifest fetched from marketplace 2. Agents deployed to `.claude/agents/` 3. Commands deployed to `.claude/commands/` 4. Skills deployed to `.claude/skills/` 5. Rules deployed to `.claude/rules/` 6. Delivery wrapper registered in local plugin registry
Examples
Example 1: Install SDLC plugin
**User**: "Install the SDLC plugin"
**Extraction**: Plugin name is `sdlc`, scope is `aiwg`
**Action**:
aiwg install-plugin sdlc@aiwg
**Response**: "Installed sdlc@aiwg v2026.3.15. Deployed 58 agents to .claude/agents/, 42 commands to .claude/commands/, 12 skills to .claude/skills/, 33 rules to .claude/rules/."
Example 2: Dry run before installing
**User**: "What would installing the voice plugin add?"
**Extraction**: Dry-run for voice plugin
**Action**:
aiwg install-plugin voice@aiwg --dry-run
**Response**: "Dry run — voice@aiwg v2026.3.15 would add: 6 voice profiles to .claude/skills/voices/, 4 soul system skills, 2 rules. No changes made."
Example 3: Force reinstall after corruption
**User**: "The SDLC plugin seems broken, reinstall it"
**Extraction**: Force reinstall of sdlc
**Action**:
aiwg install-plugin sdlc@aiwg --force
**Response**: "Force reinstalled sdlc@aiwg. All 58 agents and 42 commands redeployed cleanly."
Clarification Prompts
If the plugin name is ambiguous:
- "Which plugin would you like to install? Available: sdlc@aiwg, voice@aiwg, marketing@aiwg, utils@aiwg"
- "Did you mean `sdlc@aiwg`? Run `aiwg catalog list` to see all available plugins."
References
- @$AIWG_ROOT/src/cli/handlers/utilities.ts — Command handler
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference
Read more
namespace: aiwg name: install-plugin platforms: [all] description: Install Claude Code marketplace plugins or route local/Git wrappers through the supported package workflow
Install Plugin
You install a Claude Code marketplace plugin. In AIWG vocabulary, a plugin is a delivery wrapper around an extension, addon, or framework, not a separate content type. You handle registry lookup, download, and local deployment.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "I want the SDLC plugin" → install sdlc@aiwg
- "add the voice bundle" → install voice@aiwg
- "get me the marketing kit" → install marketing@aiwg
- "set up the testing tools" → install utils@aiwg
Trigger Patterns Reference
| Pattern | Example | Action | |---------|---------|--------| | Install plugin | "install plugin sdlc@aiwg" | Run `aiwg install-plugin sdlc@aiwg` | | Add plugin | "add plugin voice@aiwg" | Run `aiwg install-plugin voice@aiwg` | | Plugin install | "plugin install marketing@aiwg" | Run `aiwg install-plugin marketing@aiwg` | | Claude Code plugin | "install claude code plugin utils" | Run `aiwg install-plugin utils@aiwg` | | Dry run | "show me what installing sdlc would do" | Run `aiwg install-plugin sdlc@aiwg --dry-run` | | Specific version | "install sdlc version 2026.3.0" | Run `aiwg install-plugin sdlc@aiwg@2026.3.0` | | Local wrapper | "install this local plugin wrapper" | Run `aiwg install <path> --dry-run`, then `aiwg use <plugin-id>` | | Git wrapper | "install this plugin Git URL" | Run `aiwg install <git-url> --dry-run`, then `aiwg use <plugin-id>` |
Behavior
When triggered:
1. **Extract intent**:
- Which plugin is being requested? (name and optional `@scope`)
- Is a specific version mentioned?
- Is this a dry run?
2. **Run the appropriate command**:
# Install from AIWG marketplace (default scope) aiwg install-plugin sdlc@aiwg aiwg install-plugin voice@aiwg aiwg install-plugin marketing@aiwg aiwg install-plugin utils@aiwg # Install a specific version aiwg install-plugin sdlc@aiwg@2026.3.0 # Preview what would be installed aiwg install-plugin sdlc@aiwg --dry-run # Force reinstall even if already installed aiwg install-plugin sdlc@aiwg --force # Standalone local/Git wrappers use the package installer, not the legacy # manifest-only install-plugin backend. aiwg install ./path/to/wrapper --dry-run aiwg install https://example.invalid/owner/wrapper.git --dry-run aiwg use <plugin-id>
3. **Report the result** — name the installed marketplace wrapper and confirm which agents, skills, commands, and rules were deployed and where.
Available Marketplace Packages
| Package | Payload | Use Case | |--------|----------|----------| | `sdlc@aiwg` | 58 agents, 42 commands, SDLC workflows | Full software development lifecycle | | `voice@aiwg` | Voice profiles, soul system | Content style and persona management | | `marketing@aiwg` | Marketing agents, campaigns, media | Marketing operations framework | | `utils@aiwg` | Core utility skills and rules | Foundational cross-framework utilities |
What Happens on Install
1. Delivery manifest fetched from marketplace 2. Agents deployed to `.claude/agents/` 3. Commands deployed to `.claude/commands/` 4. Skills deployed to `.claude/skills/` 5. Rules deployed to `.claude/rules/` 6. Delivery wrapper registered in local plugin registry
Examples
Example 1: Install SDLC plugin
**User**: "Install the SDLC plugin"
**Extraction**: Plugin name is `sdlc`, scope is `aiwg`
**Action**:
aiwg install-plugin sdlc@aiwg
**Response**: "Installed sdlc@aiwg v2026.3.15. Deployed 58 agents to .claude/agents/, 42 commands to .claude/commands/, 12 skills to .claude/skills/, 33 rules to .claude/rules/."
Example 2: Dry run before installing
**User**: "What would installing the voice plugin add?"
**Extraction**: Dry-run for voice plugin
**Action**:
aiwg install-plugin voice@aiwg --dry-run
**Response**: "Dry run — voice@aiwg v2026.3.15 would add: 6 voice profiles to .claude/skills/voices/, 4 soul system skills, 2 rules. No changes made."
Example 3: Force reinstall after corruption
**User**: "The SDLC plugin seems broken, reinstall it"
**Extraction**: Force reinstall of sdlc
**Action**:
aiwg install-plugin sdlc@aiwg --force
**Response**: "Force reinstalled sdlc@aiwg. All 58 agents and 42 commands redeployed cleanly."
Clarification Prompts
If the plugin name is ambiguous:
- "Which plugin would you like to install? Available: sdlc@aiwg, voice@aiwg, marketing@aiwg, utils@aiwg"
- "Did you mean `sdlc@aiwg`? Run `aiwg catalog list` to see all available plugins."
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

