Keyless default — paste data or use free/first-party sources. Full analysis frameworks run either way.

/aaron-marketing:auto infers intent and runs the smallest useful workflow across disciplines.

Where do registries write?

Seven append-only streams under memory/events/*.ndjson with a sole-writer rule; memory-management handles HOT/WARM/COLD working notes.

How Aaron Marketing Skills works

A four-layer marketing operating system: Narrative strategy (L1), five always-on channels (L2), product-launch orchestration (L3), and a shared protocol layer (L4) of registries, memory, and auditor gates.

Install skills npx skills add … Hire AI Staff

More install paths (Claude marketplace, Portable Lite, SkillHub…)

TL;DR

120 skills share one seven-section contract
Eight commands: /auto plus seven discipline entrypoints
Gates emit SHIP / FIX / BLOCK — not vibes

Four layers

Layer	Adopt	Disciplines	Cadence
L1 · Strategy	crawl	Narrative · TALE	always-on
L2 · Channels	walk	SEO/GEO · Social · Email · Paid Ads · Influencer	always-on (influencer episodic-leaning)
L3 · Orchestration	run	Product Launch · RAMP	episodic
L4 · Protocol	—	7 truth registries + working memory · 8 auditor gates · one skill contract	—

Shared skill contract

Trigger / when-to-use
Quick Start
Skill Contract (Expected output · Reads · Writes · Promotes · Done-when · Primary next skill)
Handoff Summary
Data Sources (~~category placeholders with keyless Tier-1 path)
Instructions
Next Best Skill (visited-set + max-depth termination)

Commands

Command	Use	Narrowing
`/aaron-marketing:auto`	Describe any goal — infers intent and runs the smallest useful workflow	`--deep`
`/aaron-marketing:narrative`	Brand narrative (TALE loop)	`--phase trace\|architect\|land\|evaluate`
`/aaron-marketing:seo-geo`	SEO/GEO end-to-end (SITE loop)	`--phase survey\|implement\|tune\|evaluate`
`/aaron-marketing:social`	Organic social (ECHO loop)	`--phase explore\|craft\|host\|observe`
`/aaron-marketing:email`	Email (SEND loop)	`--phase setup\|engage\|nurture\|deliver`
`/aaron-marketing:ad`	Paid ads (ROAS loop)	`--phase research\|orchestrate\|activate\|scale`
`/aaron-marketing:influencer`	Influencer (STAR loop)	`--phase scout\|target\|activate\|report`
`/aaron-marketing:launch`	Product launch (RAMP loop)	`--phase research\|assemble\|mobilize\|prove`

Memory & registries

HOT (hot-cache.md, 80 lines / 25 KB cap) · WARM (per-skill working state) · COLD (archive). Registries curate; gates judge.

entity-registry — Owns machine-facing entity identity and recognition facts
creator-registry — Owns creator identity, audience, rights, terms, and compliance facts
offer-claims-registry — Owns accepted offer/claim wording and substantiation pointers
consent-registry — Owns pseudonymous consent/suppression facts and live safety state
launch-registry — Owns launch stage, dates, submissions, manifests, and outcomes
channel-registry — Owns channel state, cadence, voice pointers, and UGC permissions
narrative-registry — Owns complete versioned narrative canon records
memory-management — Manages authorized HOT/WARM/COLD working notes without impersonating a registry

Protocol layer →

FAQ

What is Tier 1?: Keyless default — paste data or use free/first-party sources. Full analysis frameworks run either way.
What does /auto do?: /aaron-marketing:auto infers intent and runs the smallest useful workflow across disciplines.
Where do registries write?: Seven append-only streams under memory/events/*.ndjson with a sole-writer rule; memory-management handles HOT/WARM/COLD working notes.