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.
Datos de origen
- Repositorio
- aiming-lab/MetaClaw
- Última actividad en el origen
- 10 de marzo de 2026 a las 18:04
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 3460
- Forks
- 449
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- 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.
Ver en GitHub