agentleFS
Sign inStart free
MihirokteMihirokte/agent-skills/skills/agent-bridge/SKILL.md

agent-bridge

Skill0 starsChanged 4 months agoMITView on GitHub

Keep skills, MCP servers, and hooks in sync across Cursor CLI, Kiro CLI, and Zed Agent via agent-bridge. Use when the user installs, adds, removes, or asks to share an MCP server or skill across AI coding agents. Zed Agent skills go in ~/.agents/skills; ACP Cursor/Kiro in Zed use their own skill dirs.

  • Reads credentials

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user adds or changes a skill, MCP server, or hook for Cursor, Kiro, or Zed Agent and wants it elsewhere, use agent-bridge.

    line 12
  2. Distinctive:

    Only sync skills, MCP, and hooks — never IDE settings dumps or secrets into git.

    line 31
  3. Very specific:

    After adding something only in one place, run agent-bridge sync or keep watch running.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Bridge

When the user adds or changes a skill, MCP server, or hook for Cursor, Kiro, or Zed Agent and wants it elsewhere, use agent-bridge.

Commands

agent-bridge init
agent-bridge sync
agent-bridge add skill ./path/to/my-skill
agent-bridge add mcp --from kiro
agent-bridge add mcp ./servers.json
agent-bridge add hook ./hook.json
agent-bridge watch
agent-bridge status
agent-bridge capabilities

Rules

  1. Only sync skills, MCP, and hooks — never IDE settings dumps or secrets into git.
  2. Secrets belong in ~/.agent-bridge/secrets.env.
  3. Kiro: skills + MCP. Zed: skills (~/.agents/skills) + MCP (context_servers in ~/.config/zed/settings.json). Hooks: Cursor only.
  4. In Zed chat:
    • Zed Agent → uses synced ~/.agents/skills + context_servers
    • Cursor / Kiro ACP → uses those agents' own skill/MCP dirs (also synced)
  5. After adding something only in one place, run agent-bridge sync or keep watch running.
  6. Conflicts live under ~/.agent-bridge/conflicts/; never overwrite silently.

Install this meta-skill

agent-bridge init

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free