verified-reply SKILL.md skillA
verified-reply from geiserx/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add geiserx/agent-skills/verified-reply@git:20261010.d1c0ff8Pins git:20261010.d1c0ff8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- geiserx/agent-skills
- Path
skills/verified-reply/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261010.d1c0ff8, committed Oct 10, 2026
- Size
- 3,303 bytes
- Repository stars
- 4
- License
- GPL-3.0
Draft a reply the user will send as themselves, with every factual claim checked against a live source first and posted only after they approve the exact text. Use when asked to answer a message, reply to a thread, PR or ticket comment, or check a reply the user wrote.
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
# verified-reply A reply that goes out under the user's name must be right, and must read as theirs. Verify first, draft second, post only on their approval of the exact text. ## Order 1. **Read the thread and the asker.** Who asked, what they already tried, what their message shows they know, and what they actually asked. Done when you can state the question in one sentence. 2. **List the claims.** Every factual statement the reply needs: a behaviour, a number, a date, an owner, a decision, a command that works. Done when each claim is one line. 3. **Check each claim against a live source.** Repository facts against the current code at the right ref, not a stale clone or memory; anything executable by running it; tickets and wiki pages through their own tools; earlier decisions in the team's own record, including whether the user already settled this question. Give each claim one verdict: `verified` with the source, `soften` (state it as belief) or `cut` (unverifiable and not needed). Done when no claim rests on memory alone. 4. **Draft in the user's voice.** Two to four lines by default, in the register of the thread. Answer what was asked …
Read the whole file at its exact version.
How to install
mdr add geiserx/agent-skills/verified-reply@sha256:3ec27661d8299c93The line at the top of this page pins the label git:20261010.d1c0ff8, 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.
[](https://markdownregistry.com/a/art_42j6nuklxhu2qpxk)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3303 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
geiserx/agent-skills · 4 stars · license GPL-3.0 · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_42j6nuklxhu2qpxk GET https://markdownregistry.com/api/v1/resolve?ref=geiserx/agent-skills/verified-reply GET https://markdownregistry.com/api/v1/blob/3ec27661d8299c934fe29904a4c48f3b874bcbb5cedd08ddccdbd4e07972ee6b
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 geiserx/agent-skills
Every file in geiserx/agent-skills