CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

narrative-quality-auditor

Use when the user asks to "audit our brand narrative" or "is this message on-canon"; runs separate typed TALE truth, system, or effectiveness profiles and never averages them into one composite. Checks differentiation, canon, landing consistency, and evidence integrity. Not for launch readiness — use launch-readiness-auditor; not for social operations — use social-quality-auditor. 品牌叙事分层审计/发布前一致性放行

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./narrative/evaluate/narrative-quality-auditor/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 auditor overview with genuinely concrete procedures, typed item/veto IDs, fail-closed runtime handling, and explicit validation checkpoints. Its main weaknesses are that the skill's core outputs (exact report header, deterministic scorer invocation) are delegated to reference files missing from this bundle, and most referenced paths — including a duplicated reference list — do not resolve in the standalone structure.

Suggestions

Inline or bundle the minimal typed conversation header template and the scorer invocation command (currently delegated to the missing auditor-runbook.md and runtime-invocation.md) so the report and scoring path are executable from the bundled files alone.

Consolidate the duplicate reference listings (Runtime Reads and Reference Materials overlap on three files) and resolve or clearly mark the ../../../references/* paths so navigation from a standalone install does not dangle.

Fold the orphaned numbered fragments (§2 Worked Examples, §3 Guardrails, §5 Translation) into the surrounding Instructions/Report sections and renumber coherently to remove the missing §1/§4 discontinuity.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no space is spent explaining concepts Claude already knows — but it is not fully lean: the "never average / no overall composite" rule is stated four times (intro, Quick Start, full-mode bullet, Report section) and the reference files are listed twice (Runtime Reads and Reference Materials overlap on three files). These are minor instances that could be trimmed, matching the efficient-with-minor-trimming anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

There is substantial concrete guidance — profile procedures with exact item IDs (T1–T10, A1–A10/L1–L10, E1–E10), named vetoes (TALE-T1/A1/L1/E1), the AARON_SKILLS_ROOT resolution command, a worked-examples table with raw scores and verdicts, a persistence path template, and the validate-audit-artifact.py step — but key details are delegated to files absent from the bundle: the required "exact typed conversation header" lives in ../../../references/auditor-runbook.md and scorer invocation in ../../../references/runtime-invocation.md, neither of which exists here. This matches the concrete-but-incomplete/missing-key-details anchor rather than 4, where gaps would be minor.

3 / 5

Workflow Clarity

The sequence is clear and well-checkpointed: runtime reads → declare target/profile/scope → per-profile procedure → veto verification → typed report → Validation Checkpoints checklist → validated persistence with a revalidate-after-write loop, plus a fail-closed error path (missing scorer → NOT_SCORED/UNDECIDED, not a skip). It misses 5 because the mid-document orphaned numbered fragments ("§2 TALE Worked Examples", "§3 TALE Guardrails", "§5 TALE Translation", with §1 and §4 absent) break the document's flow, and the actual scorer-execution steps are delegated to an external runbook.

4 / 5

Progressive Disclosure

The body is a genuine overview and the bundled fallback references/auditor-runtime.md is a real, clearly signaled one-level-deep file — but scored against the actual bundle structure, 7 of the 8 referenced paths do not resolve (auditor-runbook.md, scoring-semantics.md, tale-benchmark.md, runtime-invocation.md, measurement-protocol.md via ../../../references/, plus four sibling SKILL.md links), and the reference list is duplicated across two sections. Some structure and clear signaling, but the organization leaves most navigation dangling, fitting the middle anchor better than the mostly-clear anchor at 4.

3 / 5

Total

14

/

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: explicit "Use when" triggers with natural quoted phrases, a clear multi-action capability statement, and exemplary negative-scope disambiguation against sibling skills. The only weakness is that the concrete actions stop short of naming the outputs (verdicts/gate decisions) the profiles produce.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "runs separate typed TALE truth, system, or effectiveness profiles and never averages them into one composite" and "Checks differentiation, canon, landing consistency, and evidence integrity" — matching the anchor for several specific actions with minor gaps. It falls short of 5 because it never states what the audit produces (verdicts, gate decisions, profile reports), leaving coverage incomplete.

4 / 5

Completeness

Both halves are explicit and concrete: what it does ("runs separate typed TALE truth, system, or effectiveness profiles... Checks differentiation, canon, landing consistency, and evidence integrity") and when to use it ("Use when the user asks to 'audit our brand narrative' or 'is this message on-canon'"), with concrete trigger phrases and explicit exclusions. This matches the top anchor exactly; 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It includes natural quoted trigger phrases a user would actually say — "audit our brand narrative" and "is this message on-canon" — plus boundary terms like "launch readiness" and "social operations". A few natural variations are missing (e.g., "brand story", "positioning review", "messaging consistency"), so it fits the good-but-not-comprehensive anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (narrative truth/system/effectiveness auditing) and it explicitly redirects wrong-skill triggers — "Not for launch readiness — use launch-readiness-auditor; not for social operations — use social-quality-auditor" — minimizing conflict risk with sibling auditors. This is a clear match for the clear-niche/minimal-conflict anchor.

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/evaluate/narrative-quality-auditor/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.