Skip to content
Skills Library
Sales & customer service · Writing

update-client

/update-client

Write a short, non-technical update the user can paste to their client: plain text, in the user's voice. Use for /update-client.

Repository
skills ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

86/ 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.
Content21 / 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
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.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 a short, non-technical update the user can paste to their client: plain text, in the user's voice. Use for /update-client.

Original author description

Write a short, non-technical update the user can paste to their client: plain text, in the user's voice. Use for /update-client.

How it works

SKILL.md has no level-two headings · 14 lines, 175 words

SKILL.md preview
---
name: update-client
description: "Write a short, non-technical update the user can paste to their client: plain text, in the user's voice. Use for /update-client."
disable-model-invocation: true
---

# Update client

The user will paste this to a non-technical client under their own name.

1. Pin the time window. It defaults to "since the last update"; "since Thursday" means since Thursday.
2. Gather from the record, not memory: merged PRs, ticket changes, results, and what comes next. Check each claim against git, the tracker, or the results files.
3. Write it in the first person singular, in the user's voice: casual and direct, "I shipped…", using "we" only when the user asks.
4. Say what changed for the client and what it means for them, in 3–6 short bullets, then one line on what comes next. Leave out file names, ticket IDs, PR numbers, and jargon. Describe a technical change by its effect ("pages load in a second instead of timing out").
5. Output plain text, ready to copy in one selection: unquoted, with nothing of yours mixed into it.
6. Cut it until it is short.

**Done when:** every claim is checked, a non-technical reader understands every line, and it copies cleanly.
Files in this package (2)
  • SKILL.md 1 KB
  • status-update/SKILL.md 1 KB

Versions

The database has no other skills named update-client.

Database snapshot: 13.11.2026 · package version 84ce3380aaec (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

  • 96status-update
    Write a short update the user can paste to a client, Slack, or a coworker: plain text, in the user's voice. Use for /status-update.
  • 100client-update
    Write a status update or milestone report for whoever is waiting on the work - a client, or the person you answer to inside a company. Trigger on "update the client", "write a status update", "write my status update", "project update", "send a progress report", "milestone…
  • 100daily-update
    Write a short, casual end-of-day status update for your boss, team lead or client, summarising what got done today in plain, non-technical language they can read in ten seconds. Use whenever the user asks for a "daily update", "EOD update", "end of day report", "status update…
  • 100weekly-client-update
    Drafts the weekly update email to a client from the account's memory, this week's files and emails: what we did, what we're seeing, what's next and what we need from them. Saves it as a draft and never sends. Use when asked for a weekly, Friday or end-of-week client update, a…
  • 100weekly-client-update
    Drafts the weekly update email to a client from the account's memory, this week's files and emails: what we did, what we're seeing, what's next and what we need from them. Saves it as a draft and never sends. Use when asked for a weekly, Friday or end-of-week client update, a…
  • 85client-update-drafter
    Drafts a plain, honest status update for a client on a matter already underway — what has happened, what it means, what happens next, and any bad news or delay stated plainly rather than buried. Use this whenever a user wants a client informed of progress — including phrasings…

Feedback and reports

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