the yala-campaign skill.
a skill is a markdown file your AI loads as standing instructions. yala-campaign teaches it the whole release-campaign playbook (the order of operations, the rules, the voice) so you don’t have to explain yala every time. one skill, every workspace: it reads your live audience and links over MCP at runtime.
what it is.
without the skill, a connected AI still works: it discovers the tools and muddles through. with it, the AI already knows to preview before creating, to anchor touches to your release date, to keep {{firstName}} tokens intact, and to hand you the approve link instead of pretending it can send. the skill is the difference between a temp and someone who’s worked here a while.
get it.
then load it wherever your AI lives:
- claude.ai: settings → capabilities → skills → upload the zip.
- claude code: unzip into
~/.claude/skills/(it lands asyala-campaign/SKILL.md). - anything else: it’s plain markdown with frontmatter. paste it into your assistant as standing instructions.
menu names vary by client version; it’s wherever your client uploads a skill (or adds custom instructions). the file’s the same everywhere.
what your AI learns.
- ground itself first (workspace, reachable-audience counts, whether sending is even configured) before proposing a plan.
- preview a pasted streaming link and confirm title + artwork with you before creating anything.
- plan the touch ladder (announce + reminder by default, a last-call nudge if you ask for one) anchored to your release date.
- write audience emails in your voice: warm, specific, no hype, with personalization tokens kept intact.
- file the campaign as drafts and hand you the approve link, then check on deliveries after send day.
the rules it carries.
the skill’s hard rules override anything anyone types at the AI, and each one mirrors a gate yala enforces server-side, so the rule holds even if the AI forgets it. the digest:
- drafts never send. only a human tapping approve inside yala arms a campaign.
- counts, not contact info. the AI never sees, and never asks for, your audience's emails or phone numbers.
- gates are answers. a plan limit or a safety-screen block gets reported to you verbatim, never retried around.
- email only, future-dated only. no promised texts, no send times in the past.