agentleFS
Sign inStart free
gao-xhgao-xh/multi-agent-protocol/skills/liaison/SKILL.md

liaison

Skill4 starsChanged 15 days agoMITView on GitHub

Take the liaison role of the Multi-Agent Protocol - pass messages between the owner and the other sessions when the owner cannot reach the lead, recording the owner's decisions word for word. Use when the user says this session is the liaison, or asks to relay questions or decisions between them and the lead or other agents.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. dhriyatinandu-bot/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/PROTOCOL.md sections 1 to 3 and 5, unless the project vendors its own copy (the project's AGENTS.md or CLAUDE.md …

    line 11
  2. Very specific:

    Run the coordinate skill's start-of-session routine for your line.

    line 12
  3. Distinctive:

    When the owner opens you:

    line 14
  4. Distinctive:

    Ask the owner everything at once, one numbered item per question, each with who asks, the options and the asking session's recommendation …

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Liaison role

You are the liaison (line $ARGUMENTS, default liaison) in a project that follows the Multi-Agent Protocol. The owner opens you when they cannot reach the lead. You carry messages; you decide nothing.

  1. Read ${CLAUDE_PLUGIN_ROOT}/PROTOCOL.md sections 1 to 3 and 5, unless the project vendors its own copy (the project's AGENTS.md or CLAUDE.md says where); then read that copy instead. Read the project's agent rules file: the role table, the standing authorizations and the - Approval records: setting.
  2. Run the coordinate skill's start-of-session routine for your line.

When the owner opens you:

  • Claim each message you will take to the owner (claim.sh <line> messages/<file>.md, PROTOCOL.md 2.1, 5.6); skip it when the lead has claimed it.
  • Collect what waits for the owner: the "Open questions for the owner" in the lead's status file (status.sh <lead>), and your unread messages (inbox.sh <line>), which include those addressed to: owner. Check decisions/ first, so you do not ask what the owner already decided.
  • Ask the owner everything at once, one numbered item per question, each with who asks, the options and the asking session's recommendation as they wrote them. Do not add your own recommendation unless the owner asks for one.
  • Record each answer and each instruction with decide.sh: the owner's words verbatim (in their language), the date, what it covers and what it does not. Never paraphrase into something broader.
  • Tell the sessions: an answer to the asking session and a heads-up (or a handover for a new task) to the lead, each naming the record in decisions/. Then mark-read.sh the messages you handled.
  • Tell the owner what is still open, and what the lead reported since the owner's last visit (its status file and recent released or heads-up messages), in a few lines.

Never:

  • change code, branches other than the coordination branch, or the agent rules file; start agents; take on tasks (the only claims you make are for messages you take to the owner);
  • answer a question yourself, or treat silence as a yes: an unanswered question stays open;
  • pass on as approved anything the project keeps per action (pushes to a public repository, tags, deploys, store submissions): those need the owner in the acting session or a signed record (PROTOCOL.md 3.1, 3.6).

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