How do I install the AI Collab Protocols skill?

Run npx skillmds add majiayu000/ai-collab-protocols in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is AI Collab Protocols safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with AI Collab Protocols?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is AI Collab Protocols free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published AI Collab Protocols?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

AI Collab Protocols by majiayu000 — Agent Skill

Name: AI Collab Protocols
Rating: 4.2 (5 reviews)
Author: majiayu000

AI Collab Protocols

Surface in-task-collaboration protocols when the user describes an AI workflow informally — URL-as-entity-reference, PR-comment threads as session memory. Trigger when the user names entities by colloquial label instead of stable URL, asks "how should I structure this for Claude", or describes a multi-step Claude workflow without a durable handle. Apply reactively, not as a checklist.

majiayu000 a31358a 2 files · 5.0 KB Updated Sep 9, 2026 567 repo stars

File contents

Spot the protocol gap, name the better tactic, point at the durable handle. Small surgical interventions, not a lecture.

Core protocols

URL-as-entity-reference

If the user says "the PR Bob mentioned", "that bug from last week", or "the function we discussed", stop and ask for the URL or the symbol path. Why: names are ambiguous in long-context sessions and unrecoverable across sessions. A stable URL — GitHub PR comment permalink, MCP resource URI like @github:pr/owner/repo/123#comment-456, file:line reference — survives compaction and enables exact match. The chat that prompted this skill explicitly named this as the highest-signal collaboration tip.

Durable PR-comment threads as session memory

Long-running PR comment threads outlive any single session and form the persistence layer for multi-session work. Prefer leaving a comment on the PR over a chat-only handoff. Why: the next session — yours, a colleague's, or a future agent's — can resume from the thread without replaying context. Chat is ephemeral; PR comments are addressable.

Fit the protocol

When a project has an AGENTS.md, CLAUDE.md, or .clinerules, read it before acting. When the project has none and the work is non-trivial, propose authoring one — defer to init for AGENTS.md authoring rather than re-doing it here. Why: project-level rule files are the cross-tool agent-config convention; fighting them creates drift across sessions.

Anti-patterns to flag

Screenshot-only context — loses URL grounding, copy-paste, and search. Pair every screenshot with the URL or text export.
Unanchored pronouns — "the PR" / "that function" / "the bug" hallucinate badly in long contexts. Demand a URL or symbol path before continuing.
Token-usage / LOC framing as a quality proxy — quantity is not capability. The chat that prompted this skill explicitly rejects this framing; surface the rejection if the user reaches for it.

Optional 2026 research extensions (verification status)

Earlier candidate extensions, second-pass verified — usage details belong in a dedicated reference, not here:

✅ Tool Search Tool (verified — Anthropic official). Source: https://platform.claude.com/docs/en/agents-and-tools/tool-use/tool-search-tool.
❌ REVERSE_PROMPT.md / TASKLOG.md bidirectional pattern (unverified). No primary-source documentation found. Do not cite as 2026 standard.
⚠️ Structured-output filtering / summarization (partial — different API names). Concepts exist in the Messages API but not under the names originally claimed. Refer to the official Messages API reference before citing.

Modality differentiation

Skill	When
`ai-collab-protocols`	In-task tactic surfacing — user describes an AI workflow informally
`contexts`	Pre-implementation context sweep — gather files / patterns / tooling for a feature
`qa`	Bug capture — user reports something broken in plain language
`init`	AGENTS.md authoring — onboarding a repository, capturing hard-to-rediscover conventions

Do not invoke this skill for context sweeps (use contexts), bug filing (use qa), or AGENTS.md authoring (defer to init).

Posture

Surface one tactic at a time. Name the protocol. Show the better handle in concrete form (the actual URL, the actual file path, the actual symbol name). Do not dump the catalog on the user — pick the one tactic that matches the gap and surface that.

---name: ai-collab-protocolsdescription: Surface in-task-collaboration protocols when the user describes an AI workflow informally — URL-as-entity-reference, PR-comment threads as session memory. Trigger when the user names entities by colloquial label instead of stable URL, asks "how should I structure this for Claude", or describes a multi-step Claude workflow without a durable handle. Apply reactively, not as a checklist.--- Spot the protocol gap, name the better tactic, point at the durable handle. Small surgical interventions, not a lecture. ## Core protocols ### URL-as-entity-reference If the user says "the PR Bob mentioned", "that bug from last week", or "the function we discussed", stop and ask for the URL or the symbol path. *Why:* names are ambiguous in long-context sessions and unrecoverable across sessions. A stable URL — GitHub PR comment permalink, MCP resource URI like `@github:pr/owner/repo/123#comment-456`, file:line reference — survives compaction and enables exact match. The chat that prompted this skill explicitly named this as the highest-signal collaboration tip. ### Durable PR-comment threads as session memory Long-running PR comment threads outlive any single session and form the persistence layer for multi-session work. Prefer leaving a comment on the PR over a chat-only handoff. *Why:* the next session — yours, a colleague's, or a future agent's — can resume from the thread without replaying context. Chat is ephemeral; PR comments are addressable. ### Fit the protocol When a project has an `AGENTS.md`, `CLAUDE.md`, or `.clinerules`, read it before acting. When the project has none and the work is non-trivial, propose authoring one — defer to `init` for AGENTS.md authoring rather than re-doing it here. *Why:* project-level rule files are the cross-tool agent-config convention; fighting them creates drift across sessions. ## Anti-patterns to flag - **Screenshot-only context** — loses URL grounding, copy-paste, and search. Pair every screenshot with the URL or text export. - **Unanchored pronouns** — "the PR" / "that function" / "the bug" hallucinate badly in long contexts. Demand a URL or symbol path before continuing. - **Token-usage / LOC framing as a quality proxy** — quantity is not capability. The chat that prompted this skill explicitly rejects this framing; surface the rejection if the user reaches for it. ## Optional 2026 research extensions (verification status) Earlier candidate extensions, second-pass verified — usage details belong in a dedicated reference, not here: - **✅ Tool Search Tool** *(verified — Anthropic official)*. Source: `https://platform.claude.com/docs/en/agents-and-tools/tool-use/tool-search-tool`. - **❌ REVERSE_PROMPT.md / TASKLOG.md bidirectional pattern** *(unverified)*. No primary-source documentation found. Do not cite as 2026 standard. - **⚠️ Structured-output filtering / summarization** *(partial — different API names)*. Concepts exist in the Messages API but not under the names originally claimed. Refer to the official Messages API reference before citing. ## Modality differentiation | Skill | When | | ------------------------ | ----------------------------------------------------------------------------------- | | **`ai-collab-protocols`** | In-task tactic surfacing — user describes an AI workflow informally | | `contexts` | Pre-implementation context sweep — gather files / patterns / tooling for a feature | | `qa` | Bug capture — user reports something broken in plain language | | `init` | AGENTS.md authoring — onboarding a repository, capturing hard-to-rediscover conventions | Do not invoke this skill for context sweeps (use `contexts`), bug filing (use `qa`), or AGENTS.md authoring (defer to `init`). ## Posture Surface one tactic at a time. Name the protocol. Show the better handle in concrete form (the actual URL, the actual file path, the actual symbol name). Do not dump the catalog on the user — pick the one tactic that matches the gap and surface that.

Frequently asked questions