CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

narrative-resonance-monitor

Use when the user asks to "measure how our narrative is landing", "track echo rate against our canon lexicon", or "check how AI answer engines describe our brand"; produces a resonance report — echo rate (overlap of market language with the narrative-registry canon lexicon, method declared), AI-answer perception via tavily.py --answer (proxy-labeled), share-of-voice on a locked competitor panel (reusing share-of-voice-tracker), and resonance signals from bluesky.py / gdelt.py / pageviews.py — every number labeled Measured / proxy / User-provided, feeding the TALE E dimension and the upstream of the E1 evidence-integrity veto. Not for rebuilding share-of-voice machinery — use share-of-voice-tracker; not for own-site GA4/GSC analytics — use performance-monitor; not for scoring TALE profile result — use narrative-quality-auditor; not for adjudicating claims — use offer-claims-registry. 回声率/AI回答感知/份额之声/共鸣信号

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable measurement workflow with genuine validation checkpoints (NEEDS_INPUT stop, method-declared-first rule, trend-restart guard, gap-noting) — its workflow clarity is a model for instruction-only skills. The main cost is token efficiency: the proxy-labeling discipline and propose-request boilerplate are repeated far beyond what enforcement requires, and the closing sections duplicate each other's links.

Suggestions

State the Measured/proxy/User-provided labeling rule once in the Skill Contract and refer back to it from steps 3, 4, and 7 instead of restating it ~8 times; likewise collapse the three verbatim repeats of the `operation: propose` / `registry-events.py` boilerplate into one line — this would cut roughly a quarter of the body without losing any rule.

Add one fully concrete example per core operation: a sample `tavily.py --answer` invocation with a real brand query, and a worked echo-rate snippet showing a declared corpus and matching rule with the resulting number, making the guidance copy-paste ready.

Merge Reference Materials and Next Best Skill into a single section (narrative-drift-monitor, narrative-quality-auditor, and message-test-designer each appear in both), and distinguish which referenced files ship inside the skill bundle from those living in the parent repo, since none are present alongside SKILL.md here.

DimensionReasoningScore

Conciseness

The proxy-labeling rule is restated roughly eight times ("every number labeled Measured / proxy / User-provided" appears in the Skill Contract, Data Sources, steps 3, 4, and 7, and Termination; "via an authorized `operation: propose` request to `registry-events.py`" is repeated verbatim three times), and Reference Materials duplicates the sibling-skill links already given in Next Best Skill. It is not the 2 anchor because nothing explains concepts Claude already knows — all redundancy is the skill reiterating its own discipline — but it exceeds the 4 anchor's "minor instances" of trimming, fitting "mostly efficient but could be tightened".

3 / 5

Actionability

Concrete, executable guidance throughout: exact script invocations ("scripts/connectors/tavily.py --answer", gdelt.py, bluesky.py, pageviews.py), exact memory paths ("memory/narrative-registry/canon.md", "memory/narrative/narrative-resonance-monitor/YYYY-MM-DD-<topic>.md"), matching-rule options ("exact phrase / stem / semantic"), and three copy-paste Quick Start invocations. It is not the 5 anchor because no example command carries real arguments (e.g., a sample tavily query) and there is no worked echo-rate computation; not the 3 anchor because the guidance is executable as written, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

The seven numbered steps form a clear sequence with explicit checkpoints and failure handling: "If no current non-forked canon exists, stop with `NEEDS_INPUT`", "state the corpus ... and the matching rule ... **before** computing", "If the panel changed since the last read, flag it as a **trend restart**", "if not, note the gap rather than filling it with a proxy dressed as Measured", plus a "Done when" checklist in the contract. It is not the 4 anchor because validation checkpoints are explicit with defined stop/restart conditions, not merely present with minor gaps.

5 / 5

Progressive Disclosure

Clean overview structure (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep, purpose-labeled references (tale-benchmark.md, stimulus-binding.md, CONNECTORS.md, SECURITY.md, skill-contract.md) and no bulky reference material inlined. It is not the 5 anchor because no bundle files exist alongside SKILL.md — every referenced path ("../../../references/...", "scripts/connectors/...") resolves only in the parent repo and cannot be verified — and Reference Materials overlaps Next Best Skill on three sibling-skill links; it clears the 3 anchor because all references are clearly signaled and content is appropriately split.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete actions with named scripts and methods, natural bilingual trigger phrases, complete what/when/when-not coverage, and explicit conflict-avoidance redirects. The only critique — it packs all of this into one ~200-word sentence — is a density concern, and no anchor in this rubric penalizes it.

DimensionReasoningScore

Specificity

The description lists four concrete, fully-specified actions — "echo rate (overlap of market language with the narrative-registry canon lexicon, method declared)", "AI-answer perception via tavily.py --answer (proxy-labeled)", "share-of-voice on a locked competitor panel (reusing share-of-voice-tracker)", and "resonance signals from bluesky.py / gdelt.py / pageviews.py" — with named scripts and declared methods. It is not the 4 anchor because coverage of the skill's outputs is complete (including the Measured/proxy/User-provided labeling discipline), not left with minor gaps.

5 / 5

Completeness

It explicitly answers both questions: what ("produces a resonance report — echo rate ... AI-answer perception ... share-of-voice ... and resonance signals ... every number labeled Measured / proxy / User-provided") and when ("Use when the user asks to ..." with three concrete trigger phrases), and additionally supplies explicit when-not boundaries. It is not the 4 anchor because both what and when are fully explicit with concrete trigger phrases rather than a when that "could be more specific".

5 / 5

Trigger Term Quality

Natural quoted trigger phrases users would actually say — "measure how our narrative is landing", "track echo rate against our canon lexicon", "check how AI answer engines describe our brand" — plus bilingual synonyms ("回声率/AI回答感知/份额之声/共鸣信号") covering both English and Chinese phrasings. It is not the 4 anchor because synonyms in both languages are present and the natural terms comprehensively span the skill's four measurement types.

5 / 5

Distinctiveness Conflict Risk

Four explicit disambiguation redirects — "Not for rebuilding share-of-voice machinery — use share-of-voice-tracker; not for own-site GA4/GSC analytics — use performance-monitor; not for scoring TALE profile result — use narrative-quality-auditor; not for adjudicating claims — use offer-claims-registry" — carve a clear measurement niche. It is not the 4 anchor because conflict risk is explicitly and actively minimized against every adjacent skill, not merely mostly distinct.

5 / 5

Total

20

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 29 suspicious

Warning

referenced_paths_exist

Referenced path issues: 9 missing, 9 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/evaluate/narrative-resonance-monitor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.