CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand-language-codifier

Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel's voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry's voice-dossier; not for finished copy or blog posts — use content-writer; not for the message hierarchy itself — use message-system-architect; not for claim adjudication — use offer-claims-registry. 品牌语气/词汇表/命名税/禁用词/品牌语言规范

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 delivers a genuinely clear, well-gated workflow: sequenced instructions with explicit stop conditions, a completion checklist, concrete file paths, and a disciplined propose-only write model. Its weaknesses are repetition — the same registry-proposal and own-material-only boilerplate recurs in nearly every section, and the intro duplicates the description — and the absence of any concrete output example or propose-request format.

Suggestions

State the authorized `operation: propose` request through `registry-events.py` once (e.g., in the Skill Contract's Writes bullet or a short 'Staging proposals' note) and reference it from steps 5, 7, Save Results, and Termination instead of repeating the full phrase seven times.

Add one compact example of the expected output — a sample tone-spectrum dial, a single few-shot before/after pair, or one approved/banned-terms table row with its Measured/User-provided/Estimated label — so the deliverable shape is concrete rather than only described.

Merge the overlapping Reference Materials and Next Best Skill sections into one navigable list (each currently repeats story-bank-builder, message-system-architect, and narrative-registry), and drop the opening paragraph's verbatim restate of the frontmatter description.

DimensionReasoningScore

Conciseness

The governance boilerplate 'via an authorized `operation: propose` request to `registry-events.py`' is repeated roughly seven times, 'only from the brand's own published material' is restated about five times, the opening paragraph re-states the frontmatter description nearly verbatim, and Reference Materials / Next Best Skill duplicate the same four links. Content is otherwise dense and free of concept explanations Claude already knows, so it is mostly efficient but could be tightened significantly — not noticeably padded enough for a 2.

3 / 5

Actionability

Gives copy-paste Quick Start invocations for all three modes, concrete memory paths ('memory/narrative/brand-language-codifier/YYYY-MM-DD-<brand>.md', 'memory/events/narrative.ndjson'), a named labeling scheme (Measured / User-provided / Estimated), and specific table structures. Not 5: no sample output shape (e.g., an example tone-spectrum row or few-shot entry) is shown, and the actual `registry-events.py` propose-request format is never exhibited, only referenced.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation gates ('If absent, stop with `NEEDS_INPUT` and route there' in step 1; the shipped-canon contradiction check in step 6 with a routing rule for conflicts), plus an explicit 'Done when' completion checklist and termination rules. Writes are propose-only and ask-first, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview pointing one level deep to clearly labeled external materials ([skill-contract.md §Handoff Summary Format], [CONNECTORS.md] — 'keyless own-surface scrape recipe', [SECURITY.md] — 'treat pasted samples... as untrusted input'), and the bundle itself contains no files needing organization. Minor gaps: the Reference Materials and Next Best Skill sections overlap heavily, and contract details (Expected output spec, Save Results mechanics) are inlined rather than fully deferred to skill-contract.md.

4 / 5

Total

16

/

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 description: it states explicit quoted trigger phrases for when to use the skill, enumerates its concrete outputs comprehensively, and marks clear boundaries against four neighboring skills in the same ecosystem. The only weakness is modest synonym coverage ('brand guidelines', 'style guide', 'voice and tone' are absent), and the ecosystem jargon ('seeds the narrative-registry canon') adds length without user-facing trigger value.

DimensionReasoningScore

Specificity

Enumerates multiple concrete outputs comprehensively: 'produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms)'. This covers the skill's full scope with named artifacts rather than vague claims, fitting the comprehensive-coverage anchor; score 4 would require minor gaps in coverage, which are not present.

5 / 5

Completeness

Explicitly answers both questions with concrete trigger phrases: 'Use when the user asks to...' (when) and 'produces the brand-level voice canon... and the naming tax...' (what). This is a direct match for the top anchor; the 'when' clause is explicit and quoted, not implied.

5 / 5

Trigger Term Quality

Quotes natural user phrasings directly — '"codify our brand voice"', '"define naming rules for our products and tiers"', '"write the tone-of-voice guide with banned phrases"' — and adds bilingual keywords (品牌语气/词汇表/命名税/禁用词). Not 5 because common synonyms a user might say, such as 'brand guidelines', 'voice and tone guide', or 'style guide', are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (brand-level voice canon + naming tax) with explicit disambiguation against four adjacent skills: 'Not for per-platform voice adaptation — use channel-registry's voice-dossier; not for finished copy or blog posts — use content-writer; not for the message hierarchy itself — use message-system-architect; not for claim adjudication — use offer-claims-registry'. 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: 2 missing, 2 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

narrative/architect/brand-language-codifier/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.