basemind-comms

Exchange room-scoped conversations and per-agent inbox messages via basemind's broker.

75|13|Updated Jun 1, 2024
One-click install
npx skills add https://github.com/Goldziher/basemind --skill basemind-comms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: basemind-comms
Source: https://github.com/Goldziher/basemind/tree/main/opencode-plugin/skills/basemind-comms
Command: npx skills add https://github.com/Goldziher/basemind --skill basemind-comms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate with other agents working the same repo via basemind's broker — scoped rooms, a per-agent inbox, and two-tier messages. Reach for it whenever you start, finish, or hit a decision while collaborating, or to check whether another agent is already touching the code you're about to change.

Core Features & Use Cases

  • Rooms & scope auto-join: Join repo-scoped rooms automatically to stay aligned.
  • Two-tier messaging: Front matter summaries and lazy-loaded bodies keep rooms focused.
  • Workflow: post, read, reply: Start tasks, report blockers, and finish work with linked threads.

Quick Start

On start, run inbox_read and room_list to surface recent activity, then post a concise starting message to the relevant room.

Frequently Asked Questions about basemind-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multiple agents working on the same repository?

To coordinate multiple agents working on the same repository, you can use a broker to exchange room-scoped conversations and per-agent inbox messages. This ensures agents stay aligned on start and finish decisions while maintaining context and accountability.

How does room-scoped messaging work for collaborative agent coding?

Room-scoped messaging for collaborative coding works by automatically joining agents to repo-scoped rooms. Agents use a two-tier message payload with frontmatter summaries and lazy-loaded bodies to keep conversations focused and predictable.

What is the best way to check if another agent is already modifying code I need to change?

The best way to check if another agent is modifying the same code is to read recent activity from the agent inbox and list room history. This surfaces ongoing tasks and blockers before you start making changes.

How do I start collaborative coding tasks using a message broker?

Start collaborative coding tasks by running inbox read and room list commands to surface recent activity. Then post a concise starting message to the relevant room to announce your work and establish a linked reply thread.

Can I maintain context and accountability across multiple agents in a shared workspace?

You can maintain context and accountability across multiple agents by using room history and reply threads. These features trace collaborative decisions and ensure predictable interactions within workspace-scoped rooms.

Does agent coordination require specific message payload formats?

Agent coordination requires a two-tier message payload format combining frontmatter summaries with lazy-loaded bodies. This structure keeps rooms focused and ensures predictable, traceable collaboration across the workspace.