Menú
Bridge plugin capabilities (commands, skills, agents, hooks, MCP) to specific agent environments (Claude Code, GitHub Copilot, Gemini, Antigravity). Use this skill when converting or installing a plugin to a target runtime.
ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files.
(Industry standard: Parallel Agent) Primary Use Case: Work that can be partitioned into independent sub-tasks running concurrently across multiple agents. Parallel multi-agent execution pattern. Use when: work can be partitioned into independent tasks that N agents can execute simultaneously across worktrees. Includes routing (sequential vs parallel), merge verification, and correction loops.
Systematically analyze agent plugins and skills to extract design patterns, architectural decisions, and reusable techniques. Trigger with "analyze this plugin", "mine patterns from", "review plugin structure", "extract learnings from", "what patterns does this plugin use", or when examining any plugin or skill collection to understand its design.
Triggers the L5 Red Team Sub-Agent to rigorously audit a plugin against the 39-point L4 pattern matrix.
Audits a local plugin directory to ensure it perfectly matches the Agent Skills and Claude Plugin Open Standards.
Claude CLI sub-agent system for persona-based analysis. Use when piping large contexts to Anthropic models for security audits, architecture reviews, QA analysis, or any specialized analysis requiring a fresh model context.
| name | bridge-plugin |
| description | Bridge plugin capabilities (commands, skills, agents, hooks, MCP) to specific agent environments (Claude Code, GitHub Copilot, Gemini, Antigravity). Use this skill when converting or installing a plugin to a target runtime. |
| allowed-tools | Bash, Write, Read |
| dependencies | ["pip:yaml"] |
[!NOTE] Preferred Installation Method:
npx skillsFor standard consumption, we strongly recommend usingnpx skills add richfrem/agent-plugins-skills/plugins/<name>. It auto-detects your agent environment and installs plugins natively without Python. Thisbridge-pluginlocal skill is retained primarily for contributors deploying local source modifications or replicating repos.
This skill adapts and transforms plugin content into the specific formats required by different AI agent environments. It ensures each runtime can see and use the plugin's capabilities in its native format.
The auto-detect mode only targets existing directories. Create them first:
mkdir .agent .github .gemini .claude
If no directories are found, the installer will print this exact error with the mkdir command.
CRITICAL: You must never use
--target auto. You must explicitly specify your own runtime environment (e.g.,antigravity,claude,gemini,github) to avoid polluting other IDEs.
Universal Target Support (Agent Awareness):
You are a Universal Translator. You are not limited to the primary examples. If you identify your host system as ANY of the following platforms (or similar ones), you MUST invoke the installer with that specific target name (e.g. --target roo).
Supported Environments: amp, codex, cursor, gemini cli, github copilot, kimi code cli, opencode, antigravity, augment, claude code, openclaw, cline, codebuddy, command code, continue, cortex code, crush, droid, goose, junie, iflow cli, kiko code, kiro cli, kode, mcpjam, mistral vibe, mux, openhands, pi, qoder, qwen code, roo code, trae, trae cn, windsurf, zencoder, neovate, pochi, adal.
# Bridge to Claude Code specifically
python ./scripts/bridge_installer.py --plugin <plugin-path> --target claude
# Bridge to Antigravity specifically
python ./scripts/bridge_installer.py --plugin <plugin-path> --target antigravity
Example:
python ./scripts/bridge_installer.py --plugin plugins/my-plugin --target antigravity
For a standalone plugin install:
python ./scripts/install_all_plugins.py --target gemini
The bridge intelligently maps plugin source components to the correct file extensions, directories, and architectures expected by the agent environment.
| Target Environment | commands/*.md | skills/ | agents/*.md | rules/ | hooks/hooks.json | .mcp.json |
|---|---|---|---|---|---|---|
Claude Code (.claude/) | commands/*.md | skills/ | skills/<plugin>-<agent>/SKILL.md | Appended to ./CLAUDE.md | hooks/<plugin>-hooks.json | Merged (./.mcp.json) |
GitHub Copilot (.github/) | prompts/*.prompt.md | skills/ | skills/<plugin>-<agent>/SKILL.md | Appended to .github/copilot-instructions.md | (Ignored) | Merged (./.mcp.json) |
Google Gemini (.gemini/) | commands/*.toml | skills/ | skills/<plugin>/agents/ | Appended to ./GEMINI.md | (Ignored) | Merged (./.mcp.json) |
Antigravity (.agent/) | workflows/*.md | skills/ | skills/<plugin>-<agent>/SKILL.md | .agent/rules/ | (Ignored) | Merged (./.mcp.json) |
Azure AI Foundry (.azure/) | (Ignored) | skills/ | agents/ | (Ignored) | (Ignored) | .vscode/mcp.json (Capability Hosts) |
Universal Generic (.<target>/) | commands/*.md | skills/ | skills/<plugin>/agents/ | .<target>/rules/ | (Ignored) | Merged (./.mcp.json) |
GitHub Copilot — Two Agent Types: The
agents/*.agent.mdcolumn for GitHub Copilot covers two distinct use cases:
- IDE / UI Agents:
.github/agents/name.agent.md+.github/prompts/name.prompt.md— invokable by human via Copilot Chat slash command or agent dropdown in VS Code / GitHub.com.- CI/CD Autonomous Agents:
.github/agents/name.agent.md+.github/workflows/name-agent.yml— triggered automatically by GitHub Actions on PR/push/schedule with a Kill Switch quality gate.The
commands/*.md→prompts/*.prompt.mdmapping handles the slash-command pointer only. The full rich instruction body should live in the.agent.mdfile, not the.prompt.md. Use thecreate-agentic-workflowskill to scaffold either or both agent types from an existing Skill.
Command .md files are wrapped in TOML. Frontmatter is parsed — the description field is extracted and used as the TOML description. The frontmatter block is stripped from the prompt body.
CRITICAL: The bridge processes
skills/andcommands/(orworkflows/in older plugins) as distinct directories. Algorithms/Logic can be deployed to either, but be careful of duplicating them!
skills/are typically for passive knowledge, tools, and persistent behavior.commands/are for active, slash-command execution workflows.Do not place identical markdown files in both directories within the same plugin, or the bridge will blindly duplicate the logic into the target environments (e.g. into
.agent/workflows/and.agent/skills/simultaneously, causing contextual bloat).
command = "plugin-name:command-name"
description = "Description from frontmatter"
prompt = """
# Command content without frontmatter
...
"""
plugins/..gemini/ etc.