post-disco-followup SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
post-disco-followup from naveedharri/benai-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add naveedharri/benai-skills/post-disco-followup@git:20260723.0af5e11Pins git:20260723.0af5e11 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- naveedharri/benai-skills
- Path
plugins/benai-sales/skills/post-disco-followup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260723.0af5e11, committed Jul 23, 2026
- Size
- 12,008 bytes
- Repository stars
- 78
- License
- MIT
Produce the post-discovery follow-up package after a sales call: a personalized email recap, and, when your sales process calls for it, a personalized proposal (in PandaDoc or Google Docs, or your own existing template), plus an email draft and a confirmation summary. Nothing is ever sent. Reads all of your specifics (offer, pricing, identity, proposal backend, and where the proposal sits in your process) from config/ so it is yours, not a template, and it adapts to what you produce when.…
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
# Post-Discovery Follow-Up You produce the post-call follow-up package for a sales discovery call. Every artifact is a DRAFT: never send the proposal, never send the email, never push to a protected branch. The final step is always a confirmation summary so the user can review and send. This skill is offer-agnostic, backend-agnostic, and process-agnostic. Every business-specific value lives in `config/` at the project root. What it produces, and whether a proposal is even part of this touch, is driven by the user's sales process in config. Read config first, then act. ## Read config before anything else Config lives at the project root in `config/`: - `config/offer.md`: your offer, identity, delivery channels, the `process` block (where the proposal sits), the `assets` block (your own templates), qualification, confirmation, output dir, autonomy. - `config/pandadoc.md`: only if `proposal.backend` is `pandadoc`. If `config/offer.md` is missing or only `*.example.md` files exist, the user has not run setup. Tell them to run `setup-post-disco` first, and stop. …
Read the whole file at its exact version.
How to install
mdr add naveedharri/benai-skills/post-disco-followup@sha256:9c65e8dee3d5ddf7The line at the top of this page pins the label git:20260723.0af5e11, 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_6fvpx3sn3wt4fxvh)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 23, 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 (12008 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
naveedharri/benai-skills · 78 stars · license MIT · pushed 2026-10-09 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_6fvpx3sn3wt4fxvh GET https://markdownregistry.com/api/v1/resolve?ref=naveedharri/benai-skills/post-disco-followup GET https://markdownregistry.com/api/v1/blob/9c65e8dee3d5ddf7a96c8c9dc4f9b5127d52ab28fbeae18d8c85aa0f0421fa1d
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 naveedharri/benai-skills
Every file in naveedharri/benai-skills