lifecycle-messaging SKILL.md skillA
lifecycle-messaging from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/lifecycle-messaging@git:20260916.e72e404Pins git:20260916.e72e404 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/demand-generation/skills/lifecycle-messaging/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260916.e72e404, committed Sep 16, 2026
- First version recorded
- Aug 28, 2026
- Size
- 4,894 bytes
- Repository stars
- 2,543
- License
- MIT
Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and 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
# Lifecycle messaging ## Map the lifecycle before writing any message For each stage, name what the person is trying to do and what would move them forward. Messages written without that answer become announcements, and announcements get unsubscribed from. The stages that matter: just signed up, activated but not habitual, habitual, at risk, lapsed. Most programs over-invest in the first and neglect at-risk entirely, which is where the money is. ## The welcome sequence The highest-engagement messages you will ever send. Do not waste them on company history. 1. **Immediate** — deliver whatever was promised, plus the single next action. 2. **Within days** — the fastest route to first value, one step. 3. **After that** — the use case most people miss, or the objection most people have. Set expectations early: what you send, how often. It reduces unsubscribes more than any subject-line technique. ## Timing and cadence Trigger on behavior, not the calendar, wherever possible. A message sent because someone did something is many times more relevant than one sent because it is Tuesday. Cadence sustainable at your worst week. Every message should be one the recipient would miss. …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/lifecycle-messaging@sha256:e7d07d1e2a232a6cThe line at the top of this page pins the label git:20260916.e72e404, 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_ebupo74nc7fipi4t)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 28, 2026 and Sep 16, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 4,894 B | A | view · diff |
| git:20260901.0757404 | 2026-09-01 | 0757404 | 4,555 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 4,140 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 (4894 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ebupo74nc7fipi4t GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/lifecycle-messaging GET https://markdownregistry.com/api/v1/blob/e7d07d1e2a232a6c6883def0e7f55925bc6f376a65adb73c30dbe44033c1dfd5
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 cbrock84/headcount
Every file in cbrock84/headcount