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

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, actionable, and well-organized, with a concrete message template and concrete anti-patterns. It fully respects the token budget and assumes Claude's competence.

Dimension	Reasoning	Score
Conciseness	Around 13 lean lines with no padding and no explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	Provides a concrete, copy-ready message template (Context/Problem/Options/Deadline) and specific anti-pattern examples with rationale, rather than abstract direction.	3 / 3
Workflow Clarity	A simple single-task skill with an unambiguous action and an explicit sequenced template for complex messages; no destructive or batch operations require validation checkpoints.	3 / 3
Progressive Disclosure	Under 50 lines with no external references needed and three well-organized sections; no bundle files exist, so well-organized inline content satisfies the bar.	3 / 3
	Total	12 / 12 Passed

Description

57%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a strong explicit 'when' trigger and distinctive niche, but the 'what' is thin and specificity of concrete actions is limited to naming the scenario rather than enumerated capabilities.

Suggestions

Add an explicit 'what' clause naming concrete actions, e.g. 'Structures messages with context, problem, options, and deadline sections and flags round-trip anti-patterns.'

Broaden trigger terms to include everyday phrasings such as 'ping', 'DM', 'thread', or 'follow-up'.

Lead with the skill's behavior in third person before the 'Use when' clause to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete channel surfaces (Slack, GitHub issues, email threads) but describes the scenario rather than listing multiple specific actions the skill performs.	2 / 3
Completeness	A clear 'Use this skill when...' clause answers 'when', but the 'what' is only weakly implied ('writing messages') without stating the skill's concrete behavior or output.	2 / 3
Trigger Term Quality	Includes natural terms users would say (Slack, GitHub issues, email threads, async channels) but omits common variations like 'ping', 'DM', or 'thread'.	2 / 3
Distinctiveness Conflict Risk	The async, context-free-reader trigger with named channel surfaces gives it a clear niche unlikely to conflict with unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.