async-communication-etiquette
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.
More from aiming-lab/metaclaw
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.
13avoid-hallucinating-specifics
Common mistake — stating specific facts (API endpoints, library versions, config options, function signatures) with false confidence when uncertain. Always flag uncertainty rather than guessing specifics.
12codebase-navigation
Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes.
12graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
11uncertainty-acknowledgment
Use this skill when you are not sure about a fact, have outdated knowledge, or the question is contested. Explicitly communicate the level of confidence instead of asserting uncertain things as fact.
11secure-code-review
Use this skill when reviewing or writing code that handles user input, authentication, file I/O, network requests, or database queries. Always check for common security vulnerabilities before considering the code complete.
10