skill Skill
Enforce Cross-Claude MCP collaboration protocol: session startup, channel
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
skill is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around backend skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is Gemini CLI Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in rblank9/cross-claude-mcp, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
--- name: cross-claude description: > Enforce Cross-Claude MCP collaboration protocol: session startup, channel discipline, persistent connections, done signals. Triggers on Cross-Claude tool usage or collaboration keywords like "collaborate", "cross-claude", "send message to", "talk to", "work with", "coordinate with", "message bus", "other instance", "other Claude". --- # Cross-Claude MCP — Collaboration Protocol Rigid behavioral skill for multi-instance AI collaboration via the Cross-Claude message bus. This skill enforces the full protocol so you don't have to think about it. ## Auto-Startup Sequence (MANDATORY) When any Cross-Claude tool is detected or collaboration is requested, execute these steps in order. No skipping. No "I'll just send a message directly." 1. Call `register` with a descriptive instance_id (e.g., "builder", "reviewer", "data-analyst") 2. Call `list_channels` to see all active channels 3. Pick the most specific channel for your work — only use `general` if nothing more specific exists 4. Call `check_messages` on that channel to see what's been discussed Only after completing all four steps should you proceed with the user's request. ## Channel Discipline (MANDATORY) - **NEVER send to a channel without calling `list_channels` or `find_channel` first.** The `general` default is a fallback, not the norm. - **Before creating a new channel**, check if a suitable one already exists with `find_channel` - **If you switch channels mid-conversation**, send a message in the OLD channel first: "Moving to #new-channel" - **Stay in one channel p ...