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.
Source facts
- Repository
- aiming-lab/MetaClaw
- Last source activity
- March 10, 2026 at 18:04
- Detected SKILL.md language
- English
- Stars
- 3,460
- Forks
- 449
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- async-communication-etiquette
- description
- 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.
- category
- communication
# 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.
View on GitHub