OpenSkillIndex← back to search
claude-codecommunication

MetaClaw async-communication-etiquette

Use this skill when writing messages in async channels (Slack, GitHub issues, email threads) where the reader may not have context and cannot ask follow-up questions immediately.

install
source · Clone the upstream repo
git clone https://github.com/aiming-lab/MetaClaw
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiming-lab/MetaClaw "$T" && mkdir -p ~/.claude/skills && cp -r "$T/memory_data/skills/async-communication-etiquette" ~/.claude/skills/aiming-lab-metaclaw-async-communication-etiquette && rm -rf "$T"
manifest: memory_data/skills/async-communication-etiquette/SKILL.md
source content

Async Communication Etiquette

Make messages self-contained:

  • Include enough context that the reader doesn't need to chase down previous messages.
  • Link to relevant issues, PRs, docs, or code rather than assuming the reader has them open.

Structure for complex messages:

  • Context: 1–2 sentences on the situation.
  • Problem/question: What specifically do you need?
  • Options considered (for decisions): What alternatives exist?
  • Deadline: By when do you need a response?

Anti-patterns:

  • Hey, got a sec?
    without stating the topic (forces a round trip).
  • Tagging @channel for non-urgent messages.