CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

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/positioning-truth-tracer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-sequenced, highly actionable orchestration skill: the seven-step workflow has explicit stop conditions, failure branches, and done-when criteria, and every read/write is pinned to concrete memory paths. Its weaknesses are verbosity — the registry-events propose-routing rule is restated nine times — and progressive disclosure, since all nine references point outside the skill's bundle, which contains only SKILL.md with no bundled reference material.

Suggestions

Consolidate the routing rule into one place: state once that all registry writes go via an authorized `operation: propose` request to `registry-events.py` (naming claims.ndjson / narrative.ndjson / launches.ndjson targets), then reference that rule from the Writes bullet, steps 2 and 4, and Save Results instead of repeating the full clause each time.

Ship the key reference material inside the skill's own bundle: add a references/ directory containing at least a propose-request event example and the connector usage notes, so the skill is self-contained and its links resolve within the bundle.

Include one compact filled-in example of the differentiation truth set output (a differentiator row with claim ID, stage scope, source ref, evidence label, and [needs source] routing) so the 'Expected output' contract is concretely grounded.

DimensionReasoningScore

Conciseness

The body carries real, non-redundant information per section with no explanations of concepts Claude already knows, but the routing boilerplate "via an authorized `operation: propose` request to `registry-events.py`" is repeated roughly nine times (the Writes bullet alone repeats it three times, and the Save Results section repeats it three more times for claims.ndjson, narrative.ndjson, and launches.ndjson). Mostly efficient but clearly could be tightened by stating the propose-only routing rule once — not level 4, since the repetition exceeds 'minor instances'; not level 2, since there is no conceptual padding.

3 / 5

Actionability

Concrete, executable instruction-level guidance: exact memory paths ("memory/narrative/positioning-truth-tracer/YYYY-MM-DD-<topic>.md"), an exact onlyness template ("[Product] is the only [category frame] that [defensible value] for [beachhead]"), an explicit stop condition ("stop with `NEEDS_INPUT` and route to positioning-mapper"), and required record fields (claim ID, stage scope, source ref, observed time/window, evidence label). Not level 5 because the propose-request event format and connector invocations (firecrawl.py/tavily.py) are never shown — copy-paste examples live behind references, leaving minor gaps.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints and feedback loops: step 1 gates on canvas existence ("If absent or incomplete, stop with `NEEDS_INPUT`"), step 5 includes an explicit failure branch ("If a named alternative can honestly claim the same sentence... sharpen the value — do not resolve the failure by softening wording"), and the 'Done when' checklist closes the loop. Writes are proposal-gated and user-confirmed, so it is not a destructive/batch skill and no cap applies; checkpoints are explicit, not implicit, which rules out level 4.

5 / 5

Progressive Disclosure

Sections are well-organized and the Reference Materials list annotates all nine references one level deep (e.g. "tale-benchmark.md — TALE framework; this skill is the Trace-phase upstream of the `T1` differentiation-integrity veto"). However, judged against the actual bundle structure, the skill ships no references/, scripts/, or assets/ files — every referenced path (../../../references/tale-benchmark.md, ../../architect/message-system-architect/SKILL.md, ../../../CONNECTORS.md, scripts/connectors/firecrawl.py) points outside the bundle and cannot be verified as a real file. Good structure, but the total dependence on unshipped external files is more than the 'minor organization gaps' of level 4.

3 / 5

Total

15

/

20

Passed

Description

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

The description is a strong example: it pairs an explicit 'Use when' clause containing natural, quotable trigger phrases with a concrete statement of what the skill does, and it explicitly fences off three sibling skills to prevent mis-triggering. The only soft spot is capability specificity — the action is one composite reconcile-and-label operation rather than an enumerated list of concrete actions.

DimensionReasoningScore

Specificity

Quotes: "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]'". It names the domain and 1-2 concrete actions (reconcile the canvas; produce/label the truth set) but does not list several distinct concrete operations, so it sits at the '1-2 concrete actions' anchor rather than the 'several specific actions, minor gaps' anchor above.

3 / 5

Completeness

Quotes: "Use when the user asks to..." (explicit when, with three concrete trigger phrases) and "reconciles the reused positioning canvas against the shippable stage and the claims ledger to produce a differentiation truth set" (explicit what). Both what and when are clearly and explicitly stated with concrete triggers, matching the top anchor; it is not the 'when could be more explicit' level below.

5 / 5

Trigger Term Quality

Quotes: "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\"" plus bilingual keywords ("定位真相/差异化校准/可交付现实/主张核对"). Natural phrasing users would actually say is present, but a few plausible variations (e.g. "audit our differentiators", "validate positioning claims") are missing — good coverage, not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Quotes: "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". It carves out a clear niche and explicitly disambiguates against each adjacent sibling skill, giving minimal conflict risk — beyond the 'mostly distinct, minor overlap' anchor.

5 / 5

Total

17

/

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: 32 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

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.