Skip to content
Skills Library
Sales & customer service · Writing

client-comms

/client-comms

Write client communications - intake, follow-ups, check-ins, proposals, project updates. Use when user says "write a follow-up for [client]", "client intake email", "check in with [client]", "draft a proposal", or "project update email".

Licence
MIT
Last repository change
22.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write client communications - intake, follow-ups, check-ins, proposals, project updates. Use when user says "write a follow-up for [client]", "client intake email", "check in with [client]", "draft a proposal", or "project update email".

Triggers from the description

write a follow-up for [client]client intake emailcheck in with [client]draft a proposalproject update email
Original author description

Write client communications - intake, follow-ups, check-ins, proposals, project updates. Use when user says "write a follow-up for [client]", "client intake email", "check in with [client]", "draft a proposal", or "project update email".

How it works

  1. Setup Required
  2. Before You Start
  3. Inputs
  4. Communication Types
  5. Steps
  6. Output
  7. Rules
Original SKILL.md headings · 78 lines, 451 words
SKILL.md preview
---
name: client-comms
description: Write client communications - intake, follow-ups, check-ins, proposals, project updates. Use when user says "write a follow-up for [client]", "client intake email", "check in with [client]", "draft a proposal", or "project update email".
department: community
---

# Client Communications

Write any type of client communication — intake, session follow-ups, check-ins, re-engagement, testimonial requests, proposals, and project updates.

Kernel preamble §4 applies: `references/kernel-preamble.md`.

## Setup Required

Kernel preamble §1 applies: `references/kernel-preamble.md`.

## Before You Start

1. Read the resolved `voice` context — must sound like the owner
2. Read the resolved `brand` context — communication style
3. Read the resolved `icp` context — who the clients are
4. Read the resolved `offers` context — services available
5. If client model: read `projects/[client-name]/notes.md` for client context
6. Check the relevant employee's `memory.md` for client history

## Inputs

The user provides:
- **Communication type** — see types below
- **Client name** (if specific)
- **Context** — what happened, what's next, the situation
- **Urgency** (optional) — routine or time-sensitive

## Communication Types

| Type | Purpose | Tone |
|------|---------|------|
| **Intake / Welcome** | New client onboarding | Professional, warm, sets expectations |
| **Session Follow-up** | After a coaching/consulting session | Specific, actionable, prompt |
| **Check-in** | Between sessions — how's progress? | Caring, accountable, supportive |
| **Re-engagement** | Client gone quiet | Direct, value-forward, no guilt |
| **Testimonial Request** | Ask for a case study or review | Grateful, specific, easy to say yes |
| **Proposal** | Pitching a new engagement | Clear scope, confident, outcome-focused |
| **Project Update** | Status report on deliverables | Organized, transparent, next steps clear |

## Steps

### Step 1: Gather Context
- Pull client notes from `projects/[client-name]/` if available
- Review past session notes or memory entries
- Understand where this client is in their journey

### Step 2: Write the Communication

- **Subject line** — 3 options (clear > clever)
- **Opening** — reference something specific to this client
- **Body** — the purpose (keep it focused — 150-300 words)
- **CTA** — one clear next step
- **Sign-off** — matches the owner's professional style

### Step 3: Proposal Format (if applicable)

For proposals, use this structure:
1. **Context** — what they told you they need
2. **Approach** — how you'll solve it
3. **Scope** — what's included (and what isn't)
4. **Investment** — pricing and terms
5. **Next Steps** — how to move forward

## Output

Save to `outputs/YYYY-MM/comms/[client-slug]/` or `projects/[client-name]/`

If an email platform is connected via MCP, offer to create a draft.

## Rules

- Every client communication must reference something specific to THEM
- Never send generic templates — personalize based on available context
- Follow-ups within 24 hours of sessions (prompt the owner if overdue)
- Proposals: lead with their problem, not your credentials
- Match the owner's voice — clients should feel they're hearing from the owner directly

Versions

RepositoryScoreLicence
This page · trainingsites/campus-ai-os90MIT
getedgehq/skills90Apache-2.0

Database snapshot: 13.11.2026 · package version 78e9a6bac192 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90follow-up-cadence
    Creates and manages follow-up sequences for small business sales. Handles post-meeting recaps, post-proposal check-ins, conference lead follow-ups, re-engagement of cold leads, and batch follow-up reviews. Use when user says 'follow up with', 'write a follow-up email', 'what…
  • 90student-comms
    Write student communications - welcome sequences, check-ins, re-engagement, feedback requests. Use when user says "welcome email for students", "student onboarding", "check in with students", "re-engage inactive students", or "student communication".
  • 100client-email
    Draft client-facing emails for legal services — cover notes for contract deliverables, redline summaries, deal status updates, and follow-ups. Use when composing or revising outbound emails to clients about legal work product. Triggers on "draft reply," "email to client," "cover…
  • 82email-writer
    Write targeted emails — launch announcements, follow-ups, re-engagement, or cold outreach. Use when the user needs to write an email to customers, leads, students, or any audience.
  • 100internal-comms
    A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company…
  • 90client-intake-builder
    Generate a branded, single-file HTML client intake questionnaire for any service business. Picks the right question set (brand identity, web design, automation project, or pre-call brief), styles it with the project's brand colours and fonts, and includes validation, progress,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.