contact-verification SKILL.md skillA
contact-verification from leadmagic/gtm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leadmagic/gtm-skills/contact-verification@\"1.0.0\"Pins \"1.0.0\" in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leadmagic/gtm-skills
- Path
skills/prospecting/contact-verification/SKILL.md- Versions recorded
- 6
- Latest version
- \"1.0.0\", committed Oct 1, 2026
- First version recorded
- Jun 7, 2026
- Size
- 6,908 bytes
- Repository stars
- 76
- License
- MIT
Verify email addresses before they enter outbound sequences to prevent bounces and protect sender reputation. Use when the user wants to validate emails, check deliverability, verify contact data, prevent bounces, clean a list, or ensure their outreach list is safe to send. Triggers on: \"verify emails\", \"validate this list\", \"check if these emails are real\", \"email verification\", \"bounce prevention\", \"clean my list\", \"are these safe to send\", or any request to confirm email…
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
# Contact Verification ## Overview Verification is the gate between finding emails and sending to them. Skipping it is the single most expensive mistake in outbound — a 5% bounce rate triggers automated spam filtering at every major inbox provider. Recovery takes months. The rule: every email address entering a sequence must pass verification first. No exceptions. Verify when you find, re-verify every 90 days, and always verify before a new campaign launches. ## When to Use - \"Verify these emails before we send\" - \"Check if these addresses are deliverable\" - \"Clean my prospect list\" - \"Are these safe to send to?\" - \"Validate this CSV of contacts\" - \"What's the bounce risk on this list?\" Do NOT use for: - Finding new emails — use email-finding first - Deliverability infrastructure setup — use email-deliverability - General list hygiene beyond email — use list-building ## Authoritative Foundations Email verification is grounded in established deliverability practices. Industry consensus across major sending platforms (Google Workspace, M365, Smartlead, Instantly) converges on a bounce rate ceiling of 2% for cold …
Read the whole file at its exact version.
How to install
mdr add leadmagic/gtm-skills/contact-verification@sha256:4f9e6d2578b60f2bThe line at the top of this page pins the label \"1.0.0\", 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_jn7ocyu55jjeqgzv)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 7, 2026 and Oct 1, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| \"1.0.0\" latest | 2026-10-01 | ca0d2ec | 6,908 B | A | view · diff |
| \"1.0.0\" | 2026-09-02 | a19750a | 6,915 B | A | view · diff |
| \"1.0.0\" | 2026-06-10 | 17b6e1f | 6,909 B | A | view · diff |
| \"1.0.0\" | 2026-06-10 | 9f00d65 | 6,910 B | A | view · diff |
| \"1.0.0\" | 2026-06-08 | 2fb2a99 | 6,671 B | A | view · diff |
| \"1.0.0\" | 2026-06-07 | 20a6821 | 6,575 B | A | view |
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 (6908 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
leadmagic/gtm-skills · 76 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jn7ocyu55jjeqgzv GET https://markdownregistry.com/api/v1/resolve?ref=leadmagic/gtm-skills/contact-verification GET https://markdownregistry.com/api/v1/blob/4f9e6d2578b60f2b44875296c3800f1e035905114ac864af85e9ef0bbf01528a
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.