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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./memory_data/skills/async-communication-etiquette/SKILL.md

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.

Repository: aiming-lab/MetaClaw
Path: memory_data/skills/async-communication-etiquette/SKILL.md
Commit: 922caf3

Last updated: 9 days ago
First committed: 5 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.