Skip to content

JasonColapietro/suede-creator-skills / skills/suede-sms

suede-sms

Verified

Design consent-aware SMS/MMS programs: channel fit, welcome, cart recovery, post-purchase and win-back flows, exact copy, segment counts, cadence, quiet hours, platform selection, and measurement. Use when asked to "draft our SMS welcome flow" or audit a text program. Checks current consent, opt-out, and registration requirements. NOT FOR: email (use suede-emails), capture UX (use suede-site-alchemy), legal certification, or sending, scheduling, importing, or registering anything.

FileKindSize
CARD.mdmarkdown4.4 KB
SKILL.mdskill md18.7 KB
agents/openai.yamlconfig526 B
evals/evals.jsonconfig8.4 KB
references/compliance.mdmarkdown9.3 KB
references/platforms.mdmarkdown9.6 KB
references/sequence-templates.mdmarkdown6.8 KB
references/worked-handoff.mdmarkdown1.9 KB

references/worked-handoff.md

View on GitHub
# Suede SMS Skills: Worked Handoff

## Inputs

Request: “Draft our SMS welcome flow.” Synthetic brand: Cedar. Supplied inputs
are opt-in text and capture source, recipient jurisdictions/timezones, consent
records, current registration sample, approved destination, offer terms, and a
one-segment GSM-7 budget. If those facts are unavailable, the compliance section
names the gaps before a flow recommendation. No send authority is included.

## Expected output

Use the main skill's six-section output. A sample message using a reserved
example destination is:

```text
Trigger: confirmed SMS opt-in
Delay: after confirmation, inside the verified recipient-local send window
Copy: (90 chars, 1 segment, GSM-7)
Cedar: Your welcome guide is ready: https://example.com/welcome Reply STOP to unsubscribe.
CTA link: replace with the approved tracked destination before use
Segment: valid consenting new subscribers; exclude suppressed or withdrawn consent
Compliance footer: STOP language included
```

This is a formatting exercise, not send-ready copy. The real link's full length,
tracking, personalization, and registration consistency must be checked again.

## Failure case

Missing consent, suppression status, local time, or registration evidence leaves
an open program issue. Draft the corrected requirement and owner; never import
numbers or treat email consent as SMS consent. An emoji or smart quote can alter
encoding and segment count: recalculate the exact final text rather than keeping
the sample count.

## Validation

Count the actual message including sender, URL, spaces, and opt-out text. Verify
encoding, concatenated-segment limits, approved destination, personalization
fallback, STOP/HELP handling, recipient-local timing, and registration match.
Use the user's dated delivered/send denominators for performance, without fixed
lift or LTV promises. Current legal and carrier rules require current sources.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall