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.
npx skills add majiayu000/claude-skill-registry --skill ai-collab-protocols --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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 non
- Core protocols
- URL-as-entity-reference
- Durable PR-comment threads as session memory
- Fit the protocol
- Anti-patterns to flag
- Optional 2026 research extensions (verification status)
- Modality differentiation
- Posture
What does the ai-collab-protocols skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ai-collab-protocols --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.