pre-send-qa
Skill1 starsChanged 48 days agoMITView on GitHub
Run a read-only pre-send QA pass on any Klaviyo email or SMS program to catch broken links, missing fallbacks, audience errors, and compliance gaps before anything ships.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cognyai/claude-code-marketing-skillstheir own version, first seen Oct 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- cognyai/claude-code-marketing-skills★ 106same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- abandonment-recoverySkill
- brief-to-buildSkill
- post-purchaseSkill
- program-scorerSkill
- replenishmentSkill
- sunset-suppressionSkill
- _templateSkill
- welcome-seriesSkill
- winback-reactivationSkill
The file
Files
Pre Send Qa
Status: Planned. This is a stub. Section bodies are TODO markers. See
skills/_template/SKILL.mdfor what belongs in each section.
Scope: Cross-cutting pre-send QA for any Klaviyo email or SMS program.
This skill is read-only. It guides analysis, builds, audits, and QA. It never sends email or SMS.
When to use this skill
TODO: Trigger phrases and situations that should load this skill. List what it is NOT for and point to the sibling skill that covers that case.
Inputs
TODO: Required inputs versus optional inputs. Instruct the agent to ask for anything missing instead of guessing.
Program blueprint
TODO: Objective and audience. Message architecture (each touch: purpose, timing, channel, and the job it does). Timing as guidance with reasoning, not rigid rules. Splits and personalization. Exits and suppression. Content blocks described by the job each block does, not fixed copy.
Klaviyo build mapping
TODO: Flow trigger, profile filters, flow filters, conditional splits, and required catalog or event data. Starting point: Which flow or campaign settings, filters, and template variables the QA pass inspects. For tool names, arguments, and API shapes, defer to klaviyo-labs/agent-context and the live Klaviyo API or MCP catalog. Never trust this skill over the live catalog.
QA
TODO: What "ready to ship" means for this program, as a checklist. The skill guides QA and never sends.
Measurement
TODO: Primary KPI, guardrail metrics, attribution approach, and holdout guidance. Label every benchmark or example number illustrative unless it cites a verifiable source.
Worked example
TODO: Add examples/example-brief.md with a brief-to-build-spec walkthrough for this program, then point to it here.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.