Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From odin
Provides protocols for structuring AI collaboration: use URLs as entity references, leverage PR-comment threads as session memory, and avoid common anti-patterns in multi-step Claude workflows.
npx claudepluginhub outlinedriven/odin-claude-plugin --plugin odinHow this skill is triggered — by the user, by Claude, or both
Slash command
/odin:ai-collab-protocolsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Spot the protocol gap, name the better tactic, point at the durable handle. Small surgical interventions, not a lecture.
Orchestrates AI coding workflows with self-correction loops, pre-flight discipline rules, and cross-agent support for Claude Code and other agents.
Writes AI-optimized docs like README, CLAUDE.md, AGENTS.md, commit messages, PR descriptions using tables, checklists, absolute paths, invariants for cold project starts.
Crafts effective prompts, CLAUDE.md instructions, rules, agent system prompts, and skill bodies for reliable Claude Code behavior.
Share bugs, ideas, or general feedback.
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).
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.