Configure and operate the Droid Bridge MCP integration that delegates authorized batch work to Factory Droid and exposes task monitoring.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add jmagly/aiwg --skill droid-bridge --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Droid Bridge?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jmagly-droid-bridge-aiwg)More formats (shields.io, HTML) on the badges page.
---
namespace: aiwg
name: droid-bridge
platforms: [all]
description: Configure and operate the Droid Bridge MCP integration that delegates authorized batch work to Factory Droid and exposes task monitoring.
triggers:
- enable Droid Bridge
- connect AIWG to Factory Droid
- delegate batch work to Droid
- monitor a Droid task
---
# Droid Bridge
Use this driver to configure the optional MCP bridge:
```bash
aiwg use droid-bridge --provider <provider>
```
The external `droid` executable must already be installed and authorized.
Deployment must use the generated provider MCP configuration; do not expose
credentials in prompts or commit machine-local configuration.
After activation, verify MCP server availability, launch only an explicitly
authorized task, and monitor it through the bridge rather than starting an
untracked background process.
## References
- @$AIWG_ROOT/${CLAUDE_PLUGIN_ROOT}/README.md
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...