cold-email SKILL.md skillA
cold-email from furuyan1234/nano-banana-pro is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add furuyan1234/nano-banana-pro/cold-email@git:20260227.0564cc7Pins git:20260227.0564cc7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- furuyan1234/nano-banana-pro
- Path
.agents/skills/cold-email/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260227.0564cc7, committed Feb 27, 2026
- Size
- 6,646 bytes
- Repository stars
- 20
- License
- MIT
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
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
# Cold Email Writing You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template. ## Before Writing **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Understand the situation (ask if not provided): 1. **Who are you writing to?** — Role, company, why them specifically 2. **What do you want?** — The outcome (meeting, reply, intro, demo) 3. **What's the value?** — The specific problem you solve for people like them 4. **What's your proof?** — A result, case study, or credibility signal 5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger. --- ## Writing Principles ### Write like a peer, not a vendor …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ianvotcmh3jpnqgi/aa842b9c52e60203917fada02ca80780c18ac9042dfc85080c8d75a9e8c31758.json
Then /plugin install cold-email@markdownregistry-ianvotcmh3jpnqgi in Claude Code. It installs git:20260227.0564cc7, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add furuyan1234/nano-banana-pro/cold-email@sha256:aa842b9c52e60203The line at the top of this page pins the label git:20260227.0564cc7, 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_ianvotcmh3jpnqgi)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in furuyan1234/nano-banana-pro/cold-email 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 cold-email from somewhere else? Ask it: where did my cold-email 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 1 version of this file, committed on Feb 27, 2026.
Watch this file (sign in, one email per new version)
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.
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.
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.
Installed this file, say at .claude/skills/cold-email/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6646 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
furuyan1234/nano-banana-pro · 20 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ianvotcmh3jpnqgi GET https://markdownregistry.com/api/v1/resolve?ref=furuyan1234/nano-banana-pro/cold-email GET https://markdownregistry.com/api/v1/blob/aa842b9c52e60203917fada02ca80780c18ac9042dfc85080c8d75a9e8c31758
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 furuyan1234/nano-banana-pro
Every file in furuyan1234/nano-banana-pro
Other files named cold-email
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.