Join an Agent Bridge for cross-project knowledge sharing and agent-to-agent communication. Use when the user says "connect to the bridge", "you're on the bridge", "set up the bridge", "seed the bridge", "join the bridge", or any variation of participating in a bridge. Also use when a launch message assigns you a role on a bridge, or the user provides a bridge ID.
From agent-bridgenpx claudepluginhub ichabodcole/project-docs-scaffold-template --plugin agent-bridgeThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
You are participating in an Agent Bridge — a communication channel between A.I. Agent instances working on separate projects. Your role (source, target, etc.) and responsibilities are provided via your launch message when the desktop app starts your session.
The desktop app manages bridge creation, agent registration, and tmux sessions. You don't need to create bridges or register yourself — that's handled before you start. Your job is to use the bridge tools to share knowledge and communicate with other agents.
All bridge tools (bridge_help, bridge_status, get_pending,
add_knowledge, post_question, post_answer, etc.) are provided by the
agent-bridge MCP server. Call bridge_help for a full overview of available
tools and workflows.
bridge_status with your bridge ID to see who
else is connectedThe watcher daemon sends automated notifications to your terminal via tmux:
[Bridge: ACTION] — Requires your response (e.g., a question you should
answer)[Bridge: FYI] — Informational only, no action neededThese are automated system messages, not typed by the user.
When you see an ACTION notification, call get_pending with your bridge ID and
agent name to see what needs your attention, then respond accordingly.
Sharing knowledge — Use add_knowledge with clear topics, titles, and tags.
Same topic+title updates in place. Focus on what the other agent actually needs.
Asking questions — Use post_question with specific questions and context
about what you're building. Use parent_id for follow-up questions in a thread.
Answering questions — Call get_pending to find unanswered questions, then
post_answer with detailed responses including code examples and file
references.
Throughout your work on the bridge, note any issues with the tools, unclear workflows, or knowledge gaps. Surface a brief summary to the user periodically — this helps improve the bridge system.