client-reply SKILL.md skillA

client-reply from msolecki/developer-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add msolecki/developer-os/client-reply@git:20261024.8456bc0

Pins git:20261024.8456bc0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
msolecki/developer-os
Path
plugin/skills/client-reply/SKILL.md
Versions recorded
4
Latest version
git:20261024.8456bc0, committed Oct 24, 2026
First version recorded
Oct 15, 2026
Size
2,235 bytes
Repository stars
3
License
MIT

Draft a reply to a client's feedback round or business question in plain, non-technical business language, in the user's language and voice. Drafts only and never sends. Use when the user asks to answer a client or turn technical notes into a message for one, for example "reply to the client", "write to the client", "put this in plain language", "answer the feedback".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Client reply

1. Collect the input: the client's message or feedback round, the technical facts (bug summary, PR, commits, notes), and what the user wants to say. If a fact the reply depends on is missing (a date, whether something is fixed), ask for it; never invent dates, prices, or promises.
2. Write in the language of the client's message, otherwise the language the user writes in. Apply any voice rule in the user's instructions (for example, first person singular instead of "we") and their usual greeting and sign-off if the conversation shows them.
3. List the technical terms in the input: code identifiers, error names, endpoints, migrations, branches, PR and commit references, tool and framework names, internal environment names. Translate each into what the client sees: what did not work, for whom, since when, what was done, what happens next, and when.
4. Answer every point of a feedback round in the client's order, one short paragraph or bullet each. Say plainly what is done, what is not, and what needs the client's decision or input.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_d5mzmenapa6jk5wp/7c736ac34d9746ad92bd51cbf47520c08ec0ed3452fdac54fd37c4c30633409b.json

Then /plugin install client-reply@markdownregistry-d5mzmenapa6jk5wp in Claude Code. It installs git:20261024.8456bc0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add msolecki/developer-os/client-reply@sha256:7c736ac34d9746ad

The line at the top of this page pins the label git:20261024.8456bc0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_d5mzmenapa6jk5wp.svg)](https://markdownregistry.com/a/art_d5mzmenapa6jk5wp)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in msolecki/developer-os/client-reply since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of client-reply from somewhere else? Ask it: where did my client-reply come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 4 versions of this file, between Oct 15, 2026 and Oct 24, 2026, about one every 3 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261024.8456bc0 latest2026-10-24 8456bc0 2,235 BA view · diff
git:20261016.f1b9b142026-10-16 f1b9b14 2,271 BA view · diff
git:20261015.eeda64b2026-10-15 eeda64b 2,278 BA view · diff
git:20261015.1c324a82026-10-15 1c324a8 2,200 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2235 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

msolecki/developer-os · 3 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_d5mzmenapa6jk5wp
GET https://markdownregistry.com/api/v1/resolve?ref=msolecki/developer-os/client-reply
GET https://markdownregistry.com/api/v1/blob/7c736ac34d9746ad92bd51cbf47520c08ec0ed3452fdac54fd37c4c30633409b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from msolecki/developer-os

AGENTS.md AGENTS.md file
msolecki/developer-os · AGENTS.md
git:20261108.1076e93 · audit A · 3 stars
CLAUDE.md CLAUDE.md file
msolecki/developer-os · CLAUDE.md
git:20261016.f01de22 · audit B · 3 stars
audit-to-backlog SKILL.md skill
msolecki/developer-os · plugin/skills/audit-to-backlog/SKILL.md · Run parallel specialist reviews of a repository, require file-and-line evidence, deduplicate findings, and write an…
git:20261109.9e5d826 · audit A · 3 stars
brain-capture SKILL.md skill
msolecki/developer-os · plugin/skills/brain-capture/SKILL.md · Save a decision, a lasting lesson or a reference from the current session as a new inbox note in the user's Obsidian…
git:20261109.9e5d826 · audit A · 3 stars
brain-compile SKILL.md skill
msolecki/developer-os · plugin/skills/brain-compile/SKILL.md · Synthesize several notes on one topic from the user's Obsidian knowledge vault into one compiled inbox note that lists…
git:20261109.9e5d826 · audit A · 3 stars
brain-garden SKILL.md skill
msolecki/developer-os · plugin/skills/brain-garden/SKILL.md · Produce a stale, broken-link, frontmatter, duplicate and orphan report for the user's Obsidian knowledge vault, with…
git:20261109.9e5d826 · audit A · 3 stars
brain-import-memory SKILL.md skill
msolecki/developer-os · plugin/skills/brain-import-memory/SKILL.md · Move one project's Claude Code auto memory into the user's Obsidian vault, proposing per file a new inbox note, an…
git:20261109.9e5d826 · audit A · 3 stars
brain-project-refresh SKILL.md skill
msolecki/developer-os · plugin/skills/brain-project-refresh/SKILL.md · Bring the current repository's project hub note in the user's Obsidian vault up to date — drifted claims, moved paths…
git:20261109.9e5d826 · audit A · 3 stars
brain-review SKILL.md skill
msolecki/developer-os · plugin/skills/brain-review/SKILL.md · Review the inbox of the user's Obsidian knowledge vault — summarize captured notes, then promote, merge, reject or…
git:20261109.9e5d826 · audit A · 3 stars
brain-search SKILL.md skill
msolecki/developer-os · plugin/skills/brain-search/SKILL.md · Search the user's Obsidian knowledge vault for earlier decisions, lessons, and references on a topic, and answer only…
git:20261109.9e5d826 · audit A · 3 stars
brain-setup SKILL.md skill
msolecki/developer-os · plugin/skills/brain-setup/SKILL.md · Create the user's Obsidian knowledge vault from the developer-os template, or connect an existing one by adding only…
git:20261109.9e5d826 · audit A · 3 stars
bug-triage SKILL.md skill
msolecki/developer-os · plugin/skills/bug-triage/SKILL.md · Triage a reported defect or incident by setting severity, reproducing it, ranking evidence-backed hypotheses…
git:20261109.9e5d826 · audit A · 3 stars

Every file in msolecki/developer-os

Browse by kind, by grade A, or by owner.