CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audience-belief-mapper

Use when the user asks to "map what our buyers believe", "capture the objections we keep hearing", or "find the switching forces that move the beachhead"; produces a belief map of the beachhead — held beliefs and mental models, the recurring objections and their reframes, and the JTBD four forces (push of the problem, pull of the new, anxiety of switching, habit of the present) — each item sourced from interviews or win-loss notes (User-provided) and labeled Measured / User-provided / Estimated, with any unverified quote or comparative claim marked "[needs source]" and routed to the claims candidates, never adjudicated here. Not for demographic or persona profiling — use audience-mapper; not for the positioning canvas — use positioning-truth-tracer. 受众信念/异议地图/切换四力/流失语言

Quality

84%

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

67%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-contracted, genuinely actionable instruction skill: concrete output shapes, exact memory paths, source labels, explicit stop conditions, and a done-when checklist. Its main costs are token redundancy — the claims-routing boilerplate and cross-skill links are repeated many times over — and heavy dependence on external files that are not present in this bundle for the details it delegates (propose-request format, handoff-summary shape).

Suggestions

State the claims-routing protocol once (e.g., in a short 'Claims routing' note or a referenced protocol file) and refer to it as 'per the claims-routing note' elsewhere — the phrase "via an authorized `operation: propose` request to `registry-events.py`" currently appears six times.

De-duplicate the cross-skill references: strategic-narrative-designer and audience-mapper are each linked 4–5 times across the Scope guard, Skill Contract, Reference Materials, and Next Best Skill; one Reference Materials entry plus the Next Best Skill section would cover it.

Inline the minimal concrete detail for the delegated operations — one example of an `operation: propose` request body for `registry-events.py` and the handoff-summary shape (or a short template) — so the skill is executable without the external files that are absent from this bundle.

DimensionReasoningScore

Conciseness

The body is information-dense and never explains concepts Claude already knows (the JTBD forces are framed in one compact parenthetical, not tutored), but it is noticeably padded by repetition: the boilerplate "via an authorized `operation: propose` request to `registry-events.py`" appears verbatim six times, the opening paragraph largely restates the frontmatter description, and strategic-narrative-designer/audience-mapper links are each repeated four-to-five times across Scope guard, Skill Contract, Reference Materials, and Next Best Skill. This sits at the 3 anchor ('could be tightened') — the duplicated boilerplate and cross-references are more than the 4 anchor's 'minor instances', but not the pervasive padding of the 2 anchor.

3 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: exact table columns ("objection · frequency-source · reframe candidate"), exact memory paths (`memory/narrative/audience-belief-mapper/YYYY-MM-DD-<topic>.md`), the Measured/User-provided/Estimated labeling scheme, and three copy-paste Quick Start invocations. It falls short of the 5 anchor because key executable details are delegated to files not shown — the propose-request format for `registry-events.py` and the handoff-summary shape ("Emit the standard shape from skill-contract.md") are invoked but never specified, leaving gaps a 5 would close.

4 / 5

Workflow Clarity

The seven numbered Instructions are clearly sequenced (anchor → extract beliefs → objections table → four forces → verbatim language → claims sweep → assemble) with real checkpoints: step 1's stop-and-route gate ("if no persona evidence exists, stop and route to audience-mapper") and an explicit "Done when" checklist. It misses the 5 anchor because there are no per-step verification or fix-and-retry loops (e.g., how to verify a frequency count against the notes before it enters the table); it exceeds the 3 anchor because the gate and done-when checklist are explicit rather than implicit.

4 / 5

Progressive Disclosure

Good structure in a single well-sectioned file, with a dedicated Reference Materials section that signals each external file's purpose (one level deep, clearly labeled). However, the bundle ships no reference/script/asset files — every link (`../../../references/tale-benchmark.md`, `../../../CONNECTORS.md`, `scripts/connectors/tavily.py`, sibling SKILL.mds) points outside the bundle and resolves to nothing here, and some inline material (the repeated claims-routing protocol) reads as content that belongs in one referenced file. This fits the 4 anchor ('references mostly clear; minor organization gaps') better than the 5 anchor's cleanly split, self-contained bundle.

4 / 5

Total

15

/

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: explicit 'Use when' triggers in the user's own words, a fully concrete account of what the skill produces, a clear sourcing/labeling contract, and explicit disambiguation from adjacent skills. Its only weakness is density — it packs sourcing policy and claims-routing detail into one long sentence, which is padded relative to what a trigger description strictly needs, though no dimension anchor is violated by that.

DimensionReasoningScore

Specificity

The description lists multiple concrete, comprehensive actions with no vague filler: "produces a belief map of the beachhead — held beliefs and mental models, the recurring objections and their reframes, and the JTBD four forces (push of the problem, pull of the new, anxiety of switching, habit of the present)", plus concrete labeling ("labeled Measured / User-provided / Estimated") and claims routing ("marked '[needs source]' and routed to the claims candidates"). Coverage of the skill's outputs is complete, matching the 5 anchor rather than the 4 anchor's 'minor gaps'.

5 / 5

Completeness

Both halves are explicit: an explicit trigger clause ("Use when the user asks to ...") with concrete trigger phrases, a clear 'what' (the belief map and its three components), and even explicit exclusions ("Not for demographic or persona profiling — use audience-mapper; not for the positioning canvas — use positioning-truth-tracer"). This is the 5 anchor verbatim in structure; the 4 anchor's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

It quotes natural phrases users would actually say — "map what our buyers believe", "capture the objections we keep hearing", "find the switching forces that move the beachhead" — and covers synonyms (belief map, mental models, objections, reframes, win-loss notes, beachhead, persona profiling, positioning canvas) plus bilingual terms. This matches the 5 anchor's comprehensive natural-term coverage; the 4 anchor ('a few natural terms missing') understates it.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (belief/objection/four-forces mapping for a beachhead) and explicitly disambiguates the two nearest neighbors by name (audience-mapper for persona profiling, positioning-truth-tracer for the positioning canvas), giving minimal conflict risk. Not the 4 anchor, since overlap risk is addressed by name rather than merely 'minor'.

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

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/trace/audience-belief-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.