Individual skill

client-communication-standards

Client-facing report formatting standards. Auto-invoke when creating client summaries, investigation reports, monthly reviews, performance analyses, or any communication for stakeholders. Applies mandatory Background → Analysis → Conclusions framework with required "What We Looked At" data source attribution for all findings.

client-communication-standards/SKILL.md

Read pinned source

Source commit 90f0e419f2d820789d5e50eee1237ab9fd14dfc6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
80
Repository last updated
Aug 25, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Client Communication Standards Skill

**Purpose:** Ensures all client-facing communications follow the "Background → Analysis → Conclusions" framework with proper data transparency.

**Type:** Communication standards skill (auto-invoked for client reports)

---

## What This Skill Deliberately Does NOT Do

- **Do the analysis.** The framework structures what you found — the investigation itself happens upstream (see [`investigation-methodology`](../investigation-methodology/)). If the analysis is thin, this framework exposes that; it can't fix it.
- **Verify the data.** "What We Looked At" makes every data source transparent; it doesn't audit whether the numbers are right. Attribution is not verification.
- **Apply to internal docs.** This is for client-facing deliverables only — technical implementation details deliberately stay out of the report (they're for internal notes).
- **Deliver the report.** Output is the formatted communication; sending, presenting, or scheduling it is yours.
Back to top