Help us improve
Share bugs, ideas, or general feedback.
From skills-for-humanity
Audits written communication for clarity, identifying where messages will be misread or misunderstood. Activated by phrases like 'clarity audit' or 'check my message'.
npx claudepluginhub human-avatar/skills-for-humanityHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills-for-humanity:s4h-communication-clarity-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Most clarity failures are invisible to the sender because the sender knows what they meant.
Routes communication requests to the right skill (audience-modeling, clarity-audit, medium-selection, objection-mapping) based on situation. Use when unsure which tool fits.
Reviews technical writing for clarity and accessibility by flagging unexplained jargon, hand-wavy process descriptions, and skipped steps. Useful when reviewing documentation, tutorials, or process-heavy content.
Identifies grammar, logic, and flow errors in text and provides targeted revision suggestions without full rewrites. Use for proofreading content, docs, emails, marketing copy, or drafts.
Share bugs, ideas, or general feedback.
Most clarity failures are invisible to the sender because the sender knows what they meant. The receiver does not have that context, and the gap between what was meant and what is read is where miscommunication lives. This audit finds that gap by reading the message as the receiver would — without access to the sender's intent.
Step 1: Read from the Receiver's Perspective Do not read this as the writer who knows what was meant. Read it as someone receiving it cold. What is actually on the page? This requires a deliberate perspective shift — it is the hardest step and the most important one.
Framing check: Confirm the specific message, audience, and goal before continuing. State what you've identified — the actual content being audited, who it's addressed to, and what it's trying to achieve — in one sentence, then use AskUserQuestion:
Step 2: Structure Check Can the main point be identified within 10 seconds? If not, the structure is obscuring it. Is the structure serving the reader or the writer's thinking process? The two are often different.
Step 3: Jargon Inventory List every term or acronym that requires context the reader may not have. Each one is a potential comprehension failure. Include terms that feel obvious — "obvious" is always relative to what the writer knows.
Step 4: Assumption Inventory What must the reader already know or believe for this message to make sense? State each assumption explicitly. For each: does this reader have this context? If not, the message has a gap.
Step 5: Ask — Is It Clear? Is there a clear action or next step? Is it clear who does what, by when? A message that informs without directing produces nothing. A message that directs ambiguously produces the wrong thing.
Step 6: Name the Most Likely Misreading
Before narrowing: Show the complete set of misreadings identified across all steps to the user first. Use AskUserQuestion:
State the single most plausible way this message will be misread or misunderstood by a reasonable receiver. This is the most valuable output — it is the failure that will actually happen if the message is sent as written.
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
Issues found:
| Category | Issue | Severity (High/Med/Low) | Edit |
|---|---|---|---|
| Structure | |||
| Jargon | |||
| Assumptions | |||
| Ask/Action |
Most likely misreading:
[Concrete statement of how a reasonable receiver will misread this — and what they will do or believe as a result]
Priority edits:
A single clear next step with a named owner and a deadline eliminates more miscommunication than any amount of structural or vocabulary editing. If the ask is ambiguous, fix that before anything else.
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-writing-line-editing — Fix the clarity issues the audit identified/s4h-communication-objection-mapping — Address the objections hiding behind confusing points/s4h-writing-restructure — Restructure if the clarity issues are structural