narrative-registry

Q: How do I install narrative-registry?

Run npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill narrative-registry in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/narrative-registry/ (personal) or .claude/skills/narrative-registry/ (project).

by aaron-he-zhuMarketing & SEO

Use when the user asks to record/query the brand narrative canon, tagline, message hierarchy, voice/naming rules, or a canon re-version; curates complete versioned canon events through the append-only narrative stream and derived views. Not for TALE scoring — use narrative-quality-auditor; not for authoring the system — use message-system-architect. 品牌叙事台账/canon 记录/语气与命名规范

Installs: 1K
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill narrative-registry

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads narrative-registry automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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.md and runtime-invocation.md. Resolve AARON_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 narrative projection 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_revision and goes through host-capability owner-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 omit expected_revision and inherit it from the proposal. Never land a partial file patch as canonical.
Preserve old versions in the event stream. versions.md is 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.md from accepted projection and run verify narrative.

Downstream Dependency

Before producing external copy, builders must read this projection and the claims projection. Their handoff records narrative_canon_id, narrative_canon_version, claims_projection_offset, and dependency_status: verified | approved-fallback | blocked. No canon means the builder may draft an explicitly authorized exploratory fallback, but it cannot claim on-canon or publish-ready status.

Save Results

Require explicit permission. Append through the runtime only; never edit NDJSON. Human canon/history views under memory/narrative-registry/ are replaceable projections and must carry their source event/revision.

Capability values never enter request JSON/files/logs. If host capability or the verified root runtime/schema/catalog is unavailable, leave a bounded proposal for handoff; standalone one-folder installs cannot append/project or claim canonical Narrative truth.

Reference Materials

Registry event protocol
TALE benchmark
Claims registry
Security

Next Best Skill

Author system: message-system-architect
Verify truth: positioning-truth-tracer
Cascade: narrative-cascade-planner
Audit profile: narrative-quality-auditor

FAQ

What does the narrative-registry skill do?

How do I install narrative-registry?

Run npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill narrative-registry in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/narrative-registry/ (personal) or .claude/skills/narrative-registry/ (project).

Which AI agents can use narrative-registry?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is narrative-registry safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains narrative-registry?

It is published by aaron-he-zhu in aaron-he-zhu/aaron-marketing-skills. It has 1,000 recorded installs.