CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

narrative-drift-monitor

Use when the user asks to "check if our surfaces have drifted from the canon", "watch for competitor repositioning", or "define when we should reposition"; produces a drift report — self-drift per flagship surface vs the narrative-registry canon over time (via wayback.py, change history Measured with as-of dates), competitor-repositioning alerts, an explicit repositioning-trigger condition set, and a D1/W1/M1 message-shift retro (intended vs actual pull-through, evidence-labeled) — feeding the TALE L drift-audit sub-items and the narrative-whiplash guardrail fact base. Not for the first-time consistency check before a surface ships — use narrative-cascade-planner; not for computing the TALE profile result or running the vetoes — use narrative-quality-auditor; not for echo-rate / AI-answer resonance measurement — use narrative-resonance-monitor. 自漂移监测/竞品重定位告警/重定位触发/叙事漂移复盘

Quality

88%

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

77%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 strong, well-structured instruction-only skill: the multi-step workflow carries validation stops and a done-when checklist at every risky point, and all detail is properly disclosed through annotated one-level-deep references. The main cost is token efficiency — governance boilerplate (propose-request routing, sole-writer statements, sibling exclusions) repeats near-verbatim across three to four sections — and the wayback.py connector is named but never shown with example arguments.

Suggestions

Consolidate the repeated registry-events.py 'operation: propose' boilerplate and the 'narrative-registry is the sole writer' statement into the Skill Contract's Writes bullet; they currently appear 3-4 times across the Scope guard, Writes, and Save Results sections.

Add a one-line example invocation of scripts/connectors/wayback.py (surface URL + snapshot range) in step 2 so change-history retrieval is executable without opening CONNECTORS.md.

Include a compact example of the drift report shape in step 7 — a sample self-drift table row with verdict and as-of date, plus one example trigger condition and its counter-rule wording.

DimensionReasoningScore

Conciseness

There is no conceptual padding or explanation of things Claude already knows, but the same governance boilerplate repeats near-verbatim 3-4 times: the "operation: propose" request to registry-events.py appears in the Scope guard, Writes, and Save Results; "narrative-registry is the sole writer" appears four times; the sibling-skill exclusions appear in the intro, Scope guard, Reference Materials, and Next Best Skill. This fits "mostly efficient but could be tightened" rather than anchor 4's "minor instances that could be trimmed", since the repetition is systematic rather than occasional.

3 / 5

Actionability

The instructions give concrete paths (memory/narrative-registry/canon.md, memory/narrative/narrative-drift-monitor/YYYY-MM-DD-<topic>.md), controlled vocabulares (matches/drifted/contradicts; retain|retest|reversion-proposal|unknown), an explicit NEEDS_INPUT stop, and provenance labels, which is mostly executable guidance for an instruction-only skill. It falls short of anchor 5 because "pull change history with scripts/connectors/wayback.py" is never shown as an actual invocation (arguments are deferred entirely to CONNECTORS.md) and no example drift-report or trigger-condition shape is given for step 7's assembly.

4 / 5

Workflow Clarity

The 7 steps are clearly sequenced (baseline → snapshot → score → competitor watch → triggers → retro → assemble) with explicit validation checkpoints: the NEEDS_INPUT stop when no canon exists, "where no archive exists, record an explicit 'no history available' note rather than guessing", the step-6 guard "do not call the message validated" without a matching result observation, a "Done when" checklist, and decision routing (no trigger → re-audit; trigger fired → reposition). Not anchor 4 because checkpoints are present at every risky point rather than leaving minor gaps.

5 / 5

Progressive Disclosure

The body is a well-organized overview (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with all references one level deep and clearly signaled — each entry in Reference Materials is annotated with what it provides (e.g., tale-benchmark.md for the L sub-items, stimulus-binding.md for retro binding). Connector recipes, binding rules, and the contract templates are appropriately deferred to reference files rather than inlined, matching the anchor-5 example pattern.

5 / 5

Total

17

/

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 trigger phrases quoted verbatim, a fully enumerated output set with methods and evidence labels, and explicit boundary routing to the three sibling skills it could be confused with. Its length reflects information density (outputs, methods, exclusions, bilingual keywords) rather than padding, so the verbosity guideline is not tripped.

DimensionReasoningScore

Specificity

The description lists multiple concrete deliverables — "self-drift per flagship surface vs the narrative-registry canon over time (via wayback.py...)", "competitor-repositioning alerts", "an explicit repositioning-trigger condition set", and a "D1/W1/M1 message-shift retro" — with methods and evidence labels attached, giving comprehensive coverage with no gaps. The 4-anchor ("minor gaps in coverage") does not apply since every output of the skill is enumerated.

5 / 5

Completeness

Both questions are answered explicitly: "what" is the four-part drift report and trigger set, and "when" is the leading "Use when the user asks to..." clause with three concrete trigger phrases plus explicit negative triggers. This matches the anchor-5 example structure (capability list + 'Use when...' with concrete triggers) exactly.

5 / 5

Trigger Term Quality

It quotes verbatim natural user utterances — "check if our surfaces have drifted from the canon", "watch for competitor repositioning", "define when we should reposition" — plus drift/repositioning/retro keywords and bilingual synonyms (自漂移监测/竞品重定位告警/重定位触发/叙事漂移复盘). Not a 4: no file extensions exist for this domain and the natural phrasings users would say are directly quoted rather than merely hinted at.

5 / 5

Distinctiveness Conflict Risk

The niche (drift monitoring of a live narrative over time) is distinct, and the description explicitly de-conflicts against the three adjacent skills — "use narrative-cascade-planner", "use narrative-quality-auditor", "use narrative-resonance-monitor" — making wrong-skill triggering unlikely. Only one dimension caveat: the domain jargon (TALE L, whiplash guardrail) presumes an ecosystem vocabulary, but that does not create overlap risk.

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: 38 suspicious

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/evaluate/narrative-drift-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.