positioning-truth-tracer

Use when the user asks to "check our positioning against what we can actually ship", "trace which differentiators we can defend", or "reconcile the positioning canvas with the claims ledger"; reconciles the reused positioning canvas against the shippable stage and the claims ledger to produce a differentiation truth set — every differentiating claim verifiable or marked '[needs source]' — that TALE-T1 is judged against. Not for building the canvas — use positioning-mapper; not for adjudicating claims — use offer-claims-registry; not for authoring the message house — use message-system-architect. 定位真相/差异化校准/可交付现实/主张核对

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

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

A well-structured, actionable instruction skill with a clear sequenced workflow and clean one-level reference navigation. Its main weakness is conciseness: the routing convention and scope-guard boundaries are repeated verbatim several times.

Suggestions

State the 'authorized operation:propose request to registry-events.py' routing convention once (e.g., in the Skill Contract) and reference it from Instructions and Save Results instead of repeating the full phrase 5+ times.

Consolidate the sibling-skill boundaries (positioning-mapper, offer-claims-registry, message-system-architect) so they appear in one place — the Scope guard paragraph and Reference Materials list currently restate them.

Tighten the Skill Contract's Reads/Writes/Promotes bullets, which restate memory paths already named in the Instructions and Save Results sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes domain competence, but the routing boilerplate 'via an authorized operation:propose request to registry-events.py' and the sibling-skill boundaries (positioning-mapper, offer-claims-registry, message-system-architect) are restated verbatim across Reads/Writes, Instructions, Save Results, and Reference Materials — tightening would remove repeated tokens.	2 / 3
Actionability	Gives concrete, executable guidance for an instruction-only skill: exact memory paths (memory/claims/claims-ledger.md, memory/launch-registry/), a fixed labeling scheme (Measured / User-provided / [needs source]), and a copy-ready onlyness template — '[Product] is the only [category frame] that [defensible value] for [beachhead]'.	3 / 3
Workflow Clarity	A clear 7-step sequence with an explicit validation/stop checkpoint (step 1 NEEDS_INPUT → route to positioning-mapper), feedback guidance in step 5 (sharpen the value rather than soften wording), and an explicit 'Done when' checklist, satisfying the top anchor.	3 / 3
Progressive Disclosure	Well-organized into focused sections with a dedicated Reference Materials list of one-level-deep external references (tale-benchmark.md, CONNECTORS.md, SECURITY.md, sibling SKILL.md files), each given a one-line description for easy navigation; no nested-reference chains.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that delivers concrete actions, natural trigger phrasing, both what-and-when, and explicit disambiguation against sibling skills. It is dense but every clause earns its place.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'reconciles the reused positioning canvas against the shippable stage and the claims ledger to produce a differentiation truth set' with claims 'verifiable or marked [needs source]' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (reconcile canvas vs stage + ledger to produce a differentiation truth set) and when (a 'Use when the user asks...' clause with three concrete triggers), satisfying the top anchor.	3 / 3
Trigger Term Quality	Opens with natural user phrasing — 'check our positioning against what we can actually ship', 'trace which differentiators we can defend', 'reconcile the positioning canvas with the claims ledger' — giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche and adds explicit negative boundaries — 'Not for building the canvas — use positioning-mapper; not for adjudicating claims — use offer-claims-registry; not for authoring the message house — use message-system-architect' — making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

75%

Warnings & errors only

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

Criteria	Description	Result
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: 30 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/positioning-truth-tracer/SKILL.md
Commit: 4a77c48

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.