メニュー
Surface in-task AI collaboration protocols one tactic at a time. Use when the user refers to entities by colloquial labels, asks how to structure a Claude workflow, or describes a multi-step workflow without durable URLs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Demolish bloated code and re-derive it clean, cutting every surface the rebuilt contract does not name. Use for a repo-wide bloat sweep, when patching a subsystem has stopped paying, or when the user says "this whole module is bloated", "rewrite this properly", or "break it and rebuild".
Use when the user says "deslop", "remove debug code", "find placeholders or stub code", or "remove dead code".
Dispatch compress operations. Use when the user says "tidy" or names a file, diff, memory, workspace, git stack, or doc to tidy.
Reduce internal duplication, dead code, and ceremony. Use when you spot dead fields, redundant wrappers, or speculative abstractions in code you are already editing.
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly.
Use when the user says "simplify this diff", or asks for a compression pass over a change-set.
| name | ai-collab-protocols |
| description | Surface in-task AI collaboration protocols one tactic at a time. Use when the user refers to entities by colloquial labels, asks how to structure a Claude workflow, or describes a multi-step workflow without durable URLs. |
| disable-model-invocation | true |
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 |
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).