CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

narrative-baseline-mapper

Use when the user asks to "map what our surfaces say today", "inventory our current messaging", or "find the gap between what we say and what we mean"; produces the narrative baseline — a surface-by-surface inventory of what every owned touchpoint (homepage, pricing, docs, decks, social bios, email footers) claims RIGHT NOW, each line labeled Measured / User-provided / Estimated, plus a per-surface gap read vs the intended message and the drift-baseline snapshot the Evaluate phase measures future drift against. Not for authoring the canon — use message-system-architect; not for scoring the surfaces or running the vetoes — use narrative-quality-auditor. 现状叙事盘点/各触点口径/意图差距/漂移基线

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./narrative/trace/narrative-baseline-mapper/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, genuinely actionable instruction skill with a clear seven-step workflow, explicit output contract, and good handoff hygiene. Its weaknesses are noticeable internal repetition (the propose-request protocol and the handoff list each stated 3–4 times), the absence of any worked example of the deliverable, and heavy reliance on referenced files that are not present in the skill bundle.

Suggestions

State the `operation: propose` → `registry-events.py` submission rule once (e.g., in the Skill Contract) and reference it from steps 5 and the Save Results section instead of repeating the full phrase four times.

Add a short worked example: one inventory table row (surface · current line · as-of date · label) and one gap read with its exact quote and classification, so the deliverable format is shown, not just described.

Ship the referenced files inside the skill bundle (references/tale-benchmark.md, scripts/connectors/firecrawl.py, wayback.py, CONNECTORS.md, SECURITY.md) or trim the reference list to what the bundle actually contains, so cited paths resolve.

DimensionReasoningScore

Conciseness

The phrase 'via an authorized `operation: propose` request to `registry-events.py`' is repeated four times, and the scope/handoff list (category-narrative-mapper, positioning-truth-tracer, offer-claims-registry) is restated in the intro, the Scope guard, the Skill Contract, Reference Materials, and Next Best Skill. Mostly efficient — no explaining of concepts Claude already knows — but the repetition is unnecessary padding that could be consolidated into one stated rule.

3 / 5

Actionability

Guidance is concrete and executable: exact labels (Measured / User-provided / Estimated), exact gap classifications (aligned / drifted / contradictory / silent), concrete memory paths ('memory/narrative/narrative-baseline-mapper/YYYY-MM-DD-<topic>.md'), named connector scripts (firecrawl.py, wayback.py), and a Done-when checklist. It falls short of 5 because there is no worked example of an inventory line or a gap read with its supporting quote — the deliverable format is described, never shown.

4 / 5

Workflow Clarity

Seven numbered steps in a clear order with an evidence checkpoint ('Quote the exact line that earns the classification; a gap read without the quote is an assertion, not evidence') and a done-when checklist. Not 5 because there is no error-recovery path (e.g., what to do when a surface cannot be scraped or the user supplies no intended message beyond step 3's single fallback), leaving minor validation gaps.

4 / 5

Progressive Disclosure

References are one level deep and clearly annotated (each Reference Materials entry states its purpose), but none of the ~10 cited files — ../../../references/tale-benchmark.md, scripts/connectors/firecrawl.py, ../../../CONNECTORS.md, ../../../SECURITY.md, or the sibling SKILL.md paths — exist in the bundle (no references/, scripts/, or assets/ directories). Navigation cannot resolve from the skill as shipped, so the structure is only partially usable.

3 / 5

Total

14

/

20

Passed

Description

92%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, highly specific description that explicitly answers what, when, and what-not, with natural quoted trigger phrases and explicit de-confliction against sibling skills. The only weaknesses are length (a single ~130-word run-on sentence plus a duplicated Chinese summary tail) and a few missing natural synonyms for the trigger space.

DimensionReasoningScore

Specificity

The description names multiple concrete deliverables with comprehensive coverage: 'a surface-by-surface inventory of what every owned touchpoint (homepage, pricing, docs, decks, social bios, email footers) claims RIGHT NOW, each line labeled Measured / User-provided / Estimated, plus a per-surface gap read vs the intended message and the drift-baseline snapshot'. It exceeds anchor 4 ('several specific actions; minor gaps') because both the inputs, outputs, and their labels are enumerated.

5 / 5

Completeness

Both parts are explicit: the 'what' ('produces the narrative baseline — a surface-by-surface inventory... plus a per-surface gap read... and the drift-baseline snapshot') and the 'when' ('Use when the user asks to...') with concrete trigger phrases. It also adds negative scope ('Not for authoring the canon... not for scoring the surfaces'), matching the anchor-5 example's structure exactly.

5 / 5

Trigger Term Quality

It quotes natural user phrasings — '"map what our surfaces say today", "inventory our current messaging", or "find the gap between what we say and what we mean"' — which is strong, but common synonyms a user might say ('messaging audit', 'brand consistency', 'copy inventory', 'what does our website say') are missing. Anchor 4 ('good keyword coverage; a few natural terms missing') fits better than 5's 'comprehensive coverage of natural terms including synonyms'.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (current-state surface inventory) and explicitly de-conflicts with sibling skills: 'Not for authoring the canon — use message-system-architect; not for scoring the surfaces or running the vetoes — use narrative-quality-auditor'. Minimal trigger overlap, matching anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

19

/

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: 27 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/trace/narrative-baseline-mapper/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.