Agent Skills
› aiming-lab/MetaClaw
› async-communication-etiquette
async-communication-etiquette
GitHub指导在异步沟通渠道（如Slack、GitHub）中撰写自包含消息的规范，强调提供上下文、结构化表达及避免低效互动。
Trigger Scenarios
编写Slack或邮件消息
提交GitHub Issue或PR评论
Install
npx skills add aiming-lab/MetaClaw --skill async-communication-etiquette -g -y
SKILL.md
Frontmatter
{
"name": "async-communication-etiquette",
"category": "communication",
"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."
}
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.
Version History
- 922caf3 Current 2026-07-25 11:07
