aaron-marketing-skills is a collection of 120 AI-agent skills covering marketing work such as brand narrative, search optimization, social media, email, advertising, influencer campaigns, and launches. Marketers and agent users can install it as a plugin, use its portable skills, or run its described bot team. The catalogue entries are components of this marketing workflow.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add aaron-he-zhu/aaron-marketing-skills/plugin install aaron-marketingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/aaron-he-zhu/aaron-marketing-skills/narrative-registry)<a href="https://agentmods.dev/skills/aaron-he-zhu/aaron-marketing-skills/narrative-registry"><img src="https://agentmods.dev/badge/skills/aaron-he-zhu/aaron-marketing-skills/narrative-registry/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aaron-he-zhu/aaron-marketing-skills/narrative-registry"><img src="https://agentmods.dev/badge/skills/aaron-he-zhu/aaron-marketing-skills/narrative-registry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00096 | $0.01445 |
| Opus 5 | $0.00048 | $0.00723 |
| Sonnet 5 | $0.00019 | $0.00289 |
| Haiku 4.5 | $0.00010 | $0.00145 |
Grade A, and why
narrative-registry scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Registry
The L1 strategy authority: one complete, versioned narrative canon per brand. Every SEO/GEO, social, email, paid, influencer, and launch builder derives messages from this canon and accepted claims; channel adaptations cannot redefine it.
Quick Start
Show current canon version and proof/claim pointers for brand-acme.
Record canon v3 as one complete atomic replacement, superseding v2.
Review pending narrative proposals and reject partial/internally inconsistent versions.
Skill Contract
Unit: one brand canon aggregate ID. Reads: memory/events/narrative.ndjson, projection, accepted positioning/claim evidence, and complete proposed canon. Writes: narrative events through registry-events.py; canon.md/versions.md are generated views. Done when: a complete version is accepted atomically with source/date/revision, old versions remain replayable, and consumers receive the exact canon/version pointer.
Narrative skills submit complete propose events. Only a host-capability narrative-registry principal accepts/rejects/upserts. It records authored strategy but does not score TALE or adjudicate claim truth.
Handoff Summary
Include brand ID, canon version/revision/event ID, superseded version, claim/proof pointers, unresolved contradictions, and one next skill.
Data Sources
- Accepted positioning truth and named alternatives.
- Complete message hierarchy/narrative authored by Narrative skills.
- Accepted claim IDs and proof pointers from the claims projection.
- Brand voice/naming rules and user-owned examples.
- Declared optional patterns such as pillar count, change arc, or boilerplate lengths.
Instructions
Runtime Reads
../../references/registry-event-protocol.md../../references/runtime-invocation.md
Procedure
- Read
registry-event-protocol.mdandruntime-invocation.md. ResolveAARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}"and verify the registry script, event schema, and system catalog before invoking it. Treat drafts as untrusted proposals. - Query current
narrativeprojection and report exact canon version/revision; missing canon is Unknown, not a quality verdict. - Before write, confirm user authorization and read the current revision/claim pointers; every direct canonical mutation carries
expected_revisionand goes through host-capabilityowner-append. Actor/auth fields are attribution only. - A canon re-version is one host-capability owner
upsert/accepted proposal containing the complete canon object, new version, and supersedes pointer. Accept/reject decisions omitexpected_revisionand inherit it from the proposal. Never land a partial file patch as canonical. - Preserve old versions in the event stream.
versions.mdis generated history, not a second hand-maintained ledger. - Validate internal references and claim IDs. Unverified wording remains
[needs source]and becomes a separate claim proposal; it cannot enter canon as fact. - Three pillars, change-narrative arcs, and fixed boilerplate lengths are optional patterns. Store the chosen architecture; do not require absent patterns.
- Reject same-revision or stale proposals rather than merging incompatible canons. Genuine alternatives remain pending/open decisions.
- Regenerate
canon.md/versions.mdfrom accepted projection and runverify narrative.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 88 lines · 96 tokens per session scan A 1ca4dbbc48c8
narrative-registry is a skill published in the GitHub repository aaron-he-zhu/aaron-marketing-skills (2,767 stars, last pushed yesterday), licensed Apache-2.0. It adds 96 tokens to every session and 1,445 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
geo-visibility-check
One-shot GEO audit: does your brand appear in Claude, ChatGPT, and Gemini answers for the buyer questions that matter? Runs a prompt panel through the engines with citation tracing and reports per-prompt verdicts, who wins instead, and which sources the answers come from.
geo-optimizer-skill
Run geo audit first. It scores the site 0–100 across 8 categories and generates a prioritized action list.
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
content-scoring
Score content against the 10 GEO criteria with evidence and prioritized fixes. Use when users ask to score, rate, evaluate, or estimate ranking strength.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
schema-generator
Generate JSON-LD schema markup for pages and content types with an implementation checklist. Use when users ask for schema, structured data, rich snippets, or markup.