Best for
- Use when the user asks to "audit our brand narrative" or "is this message on-canon"; runs separate typed TALE truth, system, or effectiveness profiles and never averages them into one composite.
aaron-he-zhu/aaron-marketing-skills/narrative/evaluate/narrative-quality-auditor/SKILL.md
Use it for deployment and marketing tasks; the detail page covers purpose, installation, and practical steps.
Decision brief
Audit narrative truth, message-system coherence, or measured effectiveness as separate TALE profiles. There is no v18 overall composite: truth cannot be averaged away by coherence, and coherence cannot stand in for effectiveness evidence.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Declared | Source record | Install path and trigger |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/aaron-he-zhu/aaron-marketing-skills --skill "narrative/evaluate/narrative-quality-auditor"Inspect the Agent Skill "narrative-quality-auditor" from https://github.com/aaron-he-zhu/aaron-marketing-skills/blob/8a5756ac4b5d7c53d23bbf07704010ae5c2a3739/narrative/evaluate/narrative-quality-auditor/SKILL.md at commit 8a5756ac4b5d7c53d23bbf07704010ae5c2a3739. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Review the “Quick Start” section in the pinned source before continuing.
Read ../../../references/auditor-runbook.md, scoring-semantics.md, tale-benchmark.md, and the TALE catalog entry. Standalone installs use bundled immutable references/auditor-runtime.md; never fetch mutable main. Before deterministic calls, follow runtime-invocation.md, resolve…
Read ../../../references/auditor-runbook.md, scoring-semantics.md, tale-benchmark.md, and the TALE catalog entry. Standalone installs use bundled immutable references/auditor-runtime.md; never fetch mutable main. Before deterministic calls, follow runtime-invocation.md, resolve…
For a flagship pre-publish gate, always execute the system profile procedure and require a compatible current truth result. If no compatible truth result exists, run truth separately when its evidence is available; otherwise record the truth prerequisite as Unknown while still r…
The user asks whether positioning/differentiation is defensible.
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 88/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 2,504 | Source | Repository attention, not individual Skill quality |
| Compatibility | 1 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Audit narrative truth, message-system coherence, or measured effectiveness as separate TALE profiles. There is no v18 overall composite: truth cannot be averaged away by coherence, and coherence cannot stand in for effectiveness evidence.
Run TALE truth on canon v7 against named alternatives and approved claims.
Run TALE system on homepage/pricing/deck against canon v7 before release.
Run a full review as three linked profile results; do not compute an overall score.
Reads: one canon/surface set or message experiment plus current narrative/claims truth. Writes: only permissioned v3 artifacts. Done when: each requested profile is independently complete or its Unknowns are explicit, with no canon, claims, or surface mutation.
narrative-registry owns canon/version state and offer-claims-registry owns claims. This skill judges; authoring/fixing belongs to Trace/Architect/Land skills.
| Need | Preferred evidence |
|---|---|
| Truth | Named alternatives, interviews/win-loss, product reality, claims projection |
| Architecture | Exact canon/version, message hierarchy, voice/naming/version history |
| Landing | Declared rendered flagship surfaces linked to canon version |
| Effectiveness | Preregistered comprehension/recall/behavior evidence and locked panels |
| Public resonance | Dated own/public signals with explicit measured/proxy provenance |
../../../references/auditor-runbook.md../../../references/scoring-semantics.md../../../references/tale-benchmark.md../../../references/runtime-invocation.mdreferences/auditor-runtime.mdRead ../../../references/auditor-runbook.md, scoring-semantics.md, tale-benchmark.md, and the TALE catalog entry. Standalone installs use bundled immutable references/auditor-runtime.md; never fetch mutable main. Before deterministic calls, follow runtime-invocation.md, resolve AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}", and require the scorer, validator, and typed catalogs. If unavailable, still collect the selected profile's typed observations and Unknowns, but return score_state: NOT_SCORED / score_confidence: not_scored with no gate verdict or persistent artifact; runtime absence blocks deterministic scoring, not the observation pass.
Declare target, profile/mode, brand scope, market, audience, canon version, observation date, and evidence window.
truth: score T1–T10 for material differentiation and factual grounding.system: score A1–A10 and L1–L10 for canon coherence and landing consistency.effectiveness: score E1–E10 for one experiment/locked panel/date.full: run the three profiles independently and keep three artifacts/results. Aggregate release language conservatively: any BLOCK → block; otherwise any UNDECIDED → undecided; otherwise any FIX → fix; all SHIP → ship. Never average scores.For a flagship pre-publish gate, always execute the system profile procedure and require a compatible current truth result. If no compatible truth result exists, run truth separately when its evidence is available; otherwise record the truth prerequisite as Unknown while still rendering the requested system-profile result. A missing scorer/runtime changes that result to NOT_SCORED/UNDECIDED; it does not justify skipping the profile. Run effectiveness separately only when the user requests it or the surface makes an effectiveness claim.
Every observed state needs source/date/type/confidence. A missing canon is Unknown, not N/A. A2/A4/A8 are conditional: three pillars, a change arc, and fixed boilerplate lengths are patterns only when deliberately chosen. Run the typed scorer per profile.
Verify profile-relevant vetoes: TALE-T1 false/contradictory/unsubstantiated material differentiation, TALE-A1 demonstrated canon contradiction, TALE-L1 material flagship/canon contradiction, and TALE-E1 unsupported effectiveness claim or proxy-as-measured.
DONE/SHIP, final 86.DONE_WITH_CONCERNS/FIX, final 59.DONE/BLOCK, no final score.NEEDS_INPUT/UNDECIDED, no score.Always name truth/system/effectiveness. On trace request, qualify TALE-T1/A1/L1/E1, especially TALE-E1 versus ECHO-E1 and TALE-A1 versus ROAS/RAMP.
Begin with the auditor-runbook's exact typed conversation header. Never replace status, verdict, or score_state with prose; list each explicitly missing qualified item as ``ID: `unknown``` before findings.
For each profile show verdict, target/canon/context/date, score or coverage/interval, confidence, evidence, Unknowns, and fixes. A full report shows three side-by-side results and no overall number. Do not claim market effectiveness from system coherence.
Persist only after explicit authorization to memory/audits/narrative/YYYY-MM-DD-<topic>-<profile>.md. Preserve the scorer's orthogonal status and verdict; validate the complete v3 draft with validate-audit-artifact.py against the intended relative path, persist only through one full-content Write, and revalidate the target per the auditor runbook. Edit/shell/MCP mutations of the reserved sink are unsupported. Never overwrite another profile or update canon/claims/hot cache autonomously.
Alternatives
aaron-he-zhu/aaron-marketing-skills
Use when the user asks to "build our social posting calendar", "set weekly slots and queue depth per channel", or "plan the evergreen recycle rotation"; produces the always-on brand calendar — pillar allocation with hero/hub/help balance and give:ask targets (all labeled Estimated starting heuristics to calibrate against own analytics, never scored rules), per-channel recurring slots with queue depth, a batching workflow, an evergreen recycle cycle with freshness re-checks, deliberate open slots
aaron-he-zhu/aaron-marketing-skills
Use when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the launch-registry date, a press-release draft in standard structure with no fabricated quotes or numbers, and an analyst briefing outline. Not for press-kit assets — use launch-asset-packager; no
wshobson/agents
Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —
github/awesome-copilot
Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from