saas-lifecycle-email-orchestration SKILL.md skillA
saas-lifecycle-email-orchestration from peterbamuhigire/chwezi-dev-engine is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add peterbamuhigire/chwezi-dev-engine/saas-lifecycle-email-orchestration@git:20260911.7afa6eaPins git:20260911.7afa6ea in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- peterbamuhigire/chwezi-dev-engine
- Path
skills/saas/saas-lifecycle-email-orchestration/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260911.7afa6ea, committed Sep 11, 2026
- First version recorded
- May 19, 2026
- Size
- 10,297 bytes
- Repository stars
- 28
- License
- MIT
Use when deriving SaaS lifecycle email decisions from user state, product events, consent, channel pressure, suppression, and measurable outcomes; use the design engine for each message's visual composition and the writing route for its words.
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
# SaaS Lifecycle Email Orchestration Design the decision system that determines whether an email should exist, who should receive it, what verified state it responds to, and when it must stop. Do not begin from a sequence catalogue, fixed cadence, benchmark, or message template. <!-- dual-compat-start --> ## Use When - Product events or state transitions may justify a lifecycle email. - Email and in-product messages can collide or contradict one another. - Consent, suppression, frequency pressure, tenant roles, or account state determine eligibility. - A team needs testable trigger, branch, exit, attribution, and recovery contracts. ## Do Not Use When - The task is HTML email or newsletter presentation. Route to the design engine's `email-and-newsletter-design` skill, which composes the message for its purpose and client matrix. - The task is subject lines, body copy, or CTA wording. Route to the appropriate content-writing or UX-writing skill after the message job and evidence are approved. - The task is ESP selection, authentication, reputation, bounce processing, or provider operations. Use the retained `saas-transactional-email-infrastructure` reference branch. …
Read the whole file at its exact version.
How to install
mdr add peterbamuhigire/chwezi-dev-engine/saas-lifecycle-email-orchestration@sha256:391bb47f0fe8d3dbThe line at the top of this page pins the label git:20260911.7afa6ea, 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_zcsbo2ejnq2lxq2c)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 19, 2026 and Sep 11, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.7afa6ea latest | 2026-09-11 | 7afa6ea | 10,297 B | A | view · diff |
| git:20260911.6a695ab | 2026-09-11 | 6a695ab | 15,430 B | A | view · diff |
| git:20260907.1b775c1 | 2026-09-07 | 1b775c1 | 15,070 B | A | view · diff |
| git:20260712.a867952 | 2026-07-12 | a867952 | 15,071 B | A | view · diff |
| git:20260519.bd4658a | 2026-05-19 | bd4658a | 13,503 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 (10297 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
peterbamuhigire/chwezi-dev-engine · 28 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zcsbo2ejnq2lxq2c GET https://markdownregistry.com/api/v1/resolve?ref=peterbamuhigire/chwezi-dev-engine/saas-lifecycle-email-orchestration GET https://markdownregistry.com/api/v1/blob/391bb47f0fe8d3dbb44174dac41404bb948fb7601bcae12f351e6ebf502dd3d5
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.