Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
Passed 20 of 22 test cases with the skill, and 13 of 22 without it.
and 7 more in the full report
9 fixed11 passed either way0 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
A developer asks an AI assistant to 'fix that bug from last week'. Which collaboration anti-pattern does this phrasing exemplify?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the phrasing as unanchored pronouns. | Missed | Passed |
The instructions your model reads when the skill loads.
Spot the protocol gap, name the better tactic, point at the durable handle. Small surgical interventions, not a lecture.
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.
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.
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.
Earlier candidate extensions, second-pass verified — usage details belong in a dedicated reference, not here:
https://platform.claude.com/docs/en/agents-and-tools/tool-use/tool-search-tool.| 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).
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.