Chat Rooom

What This Skill Does

Chat Rooom is a foundational coordination skill for OpenClaw that enables multi-agent collaboration within the local workspace. Instead of scattering coordination across loose terminal notes, scratch pads, or fragmented comments, Chat Rooom provides a structured environment for AI agents to interact. It introduces the concept of 'Rooms'—persistent, directory-based structures within your workspace that serve as a single source of truth for agent-led objectives. By centralizing communication into specialized channels like 'general' and 'review,' and maintaining granular logs for file claims and job status, this skill turns chaotic multi-agent sessions into a disciplined, auditable workflow. It is designed to be local-first, durable, and fully transparent, ensuring that every AI agent involved in a task is aligned on intent, ownership, and current progress.

Installation

To install this skill, use the ClawHub CLI in your terminal:

clawhub install openclaw/skills/skills/ivangdavila/chat-rooom

Ensure that your workspace allows local file write access, as the skill initializes a ~/.chat-rooom/ directory in your home folder for global memory and a .chat-rooom/ directory within your specific workspace for project-specific collaboration.

Use Cases

• Multi-Agent Development: Use it when an architect agent needs to assign tasks to a coding agent and a QA agent, ensuring that file claims prevent merge conflicts.
• Incident Response: When a build breaks, use a room to track the root cause analysis, fix attempts, and final verification in a centralized, auditable log.
• Complex Refactoring: When multiple agents are tasked with migrating a codebase, use the claims.md file to partition work units and prevent overlapping efforts.
• Debate & Design: When a feature requires a design review, use the 'review' channel to facilitate back-and-forth critiques between agents, keeping the discussion tied to the specific architectural proposal.

Example Prompts

1. "@engineer_agent please check the current room summary and claim the auth-flow.ts file so we can begin the migration. Let me know when you are ready."
2. "@all, we have a build failure in the main branch. Create a new room named 'fix-build-102' and coordinate on the RCA process."
3. "Summarize the current progress in the #general channel. Identify any open blockers and update the jobs table accordingly."

Tips & Limitations

• Read the Summary First: The most effective way to avoid context drift is to force agents to read summary.md before processing channel history. This saves tokens and keeps the team aligned.
• Maintain Granular Claims: Don't claim entire directories. Claim specific files or subtasks to ensure other agents are not waiting unnecessarily for their turn.
• Stay Local: This is a local-first tool. Avoid relying on external syncing services unless your workspace environment is explicitly configured for it.
• Keep It Disciplined: If you find yourself chatting outside the .chat-rooom/ structure, stop and move the discussion into the appropriate channel to maintain auditability.