skills/dispensary/low-performing-promo-diagnosis/SKILL.md
--- name: low-performing-promo-diagnosis description: Analyze an underperforming SMS or email campaign for a dispensary or brand and produce a concise optimization memo with likely causes, priority fixes, and next actions. Use when a campaign sent but didn't hit expected open rates, click rates, conversions, or revenue. Trigger phrases: "why didn't this campaign work", "campaign underperformed", "low open rate", "nobody clicked", "promo didn't move product", "analyze this campaign", "what went w
npx skillsauth add admin-baked/bakedbot-for-brands skills/dispensary/low-performing-promo-diagnosisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Turn campaign performance data into an opinionated root-cause diagnosis so operators don't repeat the same mistake twice — producing a bounded optimization memo with specific fixes to test on the next send.
craig-campaign for forward-looking workcraig-campaign to strengthen the brief firstcampaign_id — to pull send/open/click/bounce/revenue dataorg_id — for segment and baseline contextbenchmark — optional; defaults to org's prior 90-day campaign averagesDiagnose in layers — each layer has a different fix. Don't jump to copy quality before ruling out delivery and audience issues.
Layer 1: Delivery Did the message reach inboxes/phones?
Layer 2: Audience Was the right segment targeted?
Layer 3: Offer Was the offer compelling?
Layer 4: Copy & creative Only reach this layer if Layers 1–3 are clean.
Benchmarks for context (NY cannabis, BakedBot orgs):
| Metric | Below Expectation | On Target | Strong | |--------|------------------|-----------|--------| | Email open rate | < 15% | 20–30% | > 35% | | Email click rate | < 1% | 2–4% | > 5% | | SMS conversion | < 2% | 4–8% | > 10% | | Attributed revenue / send | < $0.50 | $1–3 | > $5 |
## Campaign Optimization Memo — [Campaign Name] — [Date]
CAMPAIGN: [name] · Sent: [date] · Channel: [SMS/email] · Audience: [segment, N recipients]
PERFORMANCE: Open X% · Click X% · Conversion X% · Attributed revenue $X (vs $X benchmark)
VERDICT: [Underperformed / On target / Overperformed]
### Root Cause (Primary)
**Layer [1–4]: [Delivery / Audience / Offer / Copy]**
[2–3 sentences: what the data shows, why this is likely the cause]
### Contributing Factors
[Bulleted secondary issues — labeled as confirmed or suspected]
### Priority Fixes for Next Send
| # | Change | Expected Impact | Confidence |
|---|--------|----------------|-----------|
| 1 | [Specific change] | [+X% open rate est.] | High/Medium |
### Test Recommendation
[One specific A/B test to run on the next send to validate the diagnosis]
### Retest or Abandon?
[Clear recommendation: retest with fix / abandon this approach / escalate to super_user]
testing
--- name: executive-brief description: Produce a concise executive brief or portfolio digest for a super user or operator — use when summarizing multi-account performance, cross-org anomalies, top actions needed, or weekly business status for leadership review. Trigger phrases: "executive summary", "weekly brief", "portfolio digest", "top actions this week", "what needs my attention", "board update", "cross-account summary". version: 0.1.0 owner: platform agent_owner: pops allowed_roles: - sup
development
--- name: anomaly-to-action-memo description: Interpret a detected anomaly or signal and produce a decision-ready action memo — use when an alert, metric deviation, or operational signal needs to be turned into a prioritized recommendation with evidence, owner, and next step. Trigger phrases: "what does this anomaly mean", "something looks off", "explain this alert", "revenue is down", "traffic dropped", "flag this for review", "what should we do about this". version: 0.1.0 owner: ops-intelligen
testing
--- name: brand-voice description: Apply BakedBot brand voice standards to any customer-facing content — use when generating or reviewing copy that must match a dispensary or brand's approved tone, language patterns, and messaging constraints. Trigger phrases: "does this match our voice", "write in our brand voice", "on-brand copy", "brand guidelines", "tone check". version: 0.1.0 owner: platform agent_owner: craig allowed_roles: - super_user - dispensary_operator - brand_operator outputs:
testing
--- name: sell-through-partner-analysis description: Analyze which retail dispensary partners are selling through a grower's products effectively, identify top performers and laggards, and produce a prioritized partner action plan. Use when a grower wants to know where their products move fastest, which partners need attention, and where to focus wholesale sales effort. Trigger phrases: "which partners are selling our product", "sell-through analysis", "partner performance", "where is inventory