CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

narrative-registry

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 记录/语气与命名规范

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

An efficiently written, well-structured protocol skill whose procedure is clearly sequenced with meaningful validation gates. Its weaknesses are that the central write operation is delegated to reference files that are not present in this bundle, leaving the body not fully self-sufficient in executable detail, and that progressive disclosure relies entirely on unresolvable external paths.

Suggestions

Include a minimal executable example of the core operation in the body — one registry-events.py invocation (query and append/propose) with its key flags — so the skill remains actionable even when the protocol reference is unavailable.

Ship the referenced files (registry-event-protocol.md, runtime-invocation.md) inside the skill bundle (e.g. a references/ directory with bundle-relative paths) instead of ../../ paths that only resolve in the source repository.

Add an explicit error-recovery loop after the final verification step (e.g. 'if verify narrative fails, fix the offending event fields and re-run') to close the feedback-loop gap in the workflow.

DimensionReasoningScore

Conciseness

Lean and dense throughout: no concept explanations Claude already knows, no padding; every section (Skill Contract, Data Sources, Procedure, Downstream Dependency, Save Results) carries operational content only. It assumes competence aggressively, bordering on terse, so no dimension of verbosity applies.

5 / 5

Actionability

Concrete elements exist (memory/events/narrative.ndjson, the AARON_SKILLS_ROOT resolution snippet, 'run verify narrative', expected_revision/upsert semantics), but the skill's core operation — appending events via registry-events.py — has no invocation example in the body, and the protocol reference that would supply it is not present in the bundle. Not 4 because the missing write-path details are the skill's primary action, not a minor gap; not 2 because the procedural semantics given are specific and directive.

3 / 5

Workflow Clarity

A clearly sequenced 9-step procedure with real checkpoints: confirm authorization and read current revision before write (step 3), validate internal references and claim IDs (step 6), regenerate views and run 'verify narrative' (step 9), plus explicit rejection handling for stale proposals (step 8). Not 5 because there is no explicit validate→fix→retry feedback loop for failed verification; not 3 because validation checkpoints are present, not merely implied.

4 / 5

Progressive Disclosure

The body is well organized with clearly labeled one-level-deep references (Runtime Reads, Reference Materials, Next Best Skill), but none of the referenced files ship in the bundle — references/, scripts/, and assets/ are absent and every path (../../references/registry-event-protocol.md, ../offer-claims-registry/SKILL.md, ../../SECURITY.md) resolves outside it. Not 4 because the most operationally critical references are unverifiable/missing, breaking the navigation the structure promises; not 2 because the in-body structure and signaling are genuinely good.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description with explicit what/when structure, concrete trigger phrases, bilingual synonyms, and explicit disambiguation from sibling skills. Its only weakness is that the 'what' leans on internal system vocabulary ('append-only narrative stream', 'derived views') that a first-time reader must decode.

DimensionReasoningScore

Specificity

Lists several concrete actions ('record/query the brand narrative canon, tagline, message hierarchy, voice/naming rules, or a canon re-version') though 'curates complete versioned canon events through the append-only narrative stream and derived views' frames capability in system-architecture terms rather than user-facing actions. Not 5 because coverage is described partly in internal jargon; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ('curates complete versioned canon events through the append-only narrative stream and derived views') and when ('Use when the user asks to record/query the brand narrative canon, tagline, message hierarchy...'). The when clause carries concrete trigger phrases, matching the top anchor; score 4 would require the when to be less explicit than it is.

5 / 5

Trigger Term Quality

Good natural keyword coverage — 'tagline', 'message hierarchy', 'voice/naming rules', 'canon' — reinforced with Chinese synonyms ('品牌叙事台账/canon 记录/语气与命名规范'). Not 5 because common variations like 'positioning', 'brand story', or 'messaging' are absent; not 3 because the terms present are ones users of this domain would naturally say.

4 / 5

Distinctiveness Conflict Risk

Clear niche (brand narrative canon registry) with explicit negative scoping: 'Not for TALE scoring — use narrative-quality-auditor; not for authoring the system — use message-system-architect'. This actively routes away overlapping triggers, minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 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: 10 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

protocol/narrative-registry/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.