CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-voice-extractor

Analyze a company's published content to extract their brand voice, writing style, and tone guidelines. Reads 10-20 of their best content pieces and produces a brand voice profile covering tone, vocabulary level, sentence structure, formatting patterns, CTAs, and target persona. Useful before writing outreach, content, or campaigns that should match a client's existing voice.

61

Quality

77%

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 ./skills/brand/capabilities/brand-voice-extractor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable instruction-only skill with a clear process and a complete deliverable template, but it pays for that inline: the body is overlong for SKILL.md, restates analytical dimensions Claude would apply on its own, and offers no validation handling for its batch fetch step.

Suggestions

Move the full brand voice profile template (~100 lines) into a references/output-template.md file and keep only the section headings and one short example inline in SKILL.md, cutting the body to a true overview.

Add validation guidance to Phase 2: what to do when a WebFetch fails or returns nav/footer-only content (retry once, substitute another URL from the inventory, and confirm at least 10 usable pieces before proceeding to analysis).

Deduplicate the selection guidance — the Phase 1 diversity bullets, the selection heuristic, and the '15 pages is the sweet spot' tip repeat the same guidance — and trim Phase 3's dimension checklist to only non-obvious items (e.g., banned patterns, voice evolution across content age) that a model would not weigh by default.

DimensionReasoningScore

Conciseness

The ~50-line Phase 3 checklist of analytical dimensions (formality, sentence length, POV, header styles) largely enumerates what a competent model would already consider, and the selection guidance is stated three times (Phase 1 diversity bullets, the selection heuristic, and the Tips section). Mostly efficient but could be tightened — anchor 3, not 4, because the redundancy and self-evident checklists go beyond minor trimmable instances.

3 / 5

Actionability

Gives exact sample counts ('8-10 blog posts, 2-3 landing pages, 2-3 case studies'), a concrete 4-phase process, and a complete copy-paste-ready output template. The absence of code is explicitly justified ('This skill has no code script. It's an agent-executed skill'), so per the instruction-skill scoring note it is not penalized — the guidance is fully executable for its type.

5 / 5

Workflow Clarity

The four phases are clearly sequenced, but the workflow batch-fetches 10-20 URLs with no verification checkpoints: no guidance on fetch failures, paywalled/JS-heavy pages, or a minimum-content check before analysis. Per the rubric's cap for batch operations without validation, workflow clarity cannot exceed 3 despite the clear sequence.

3 / 5

Progressive Disclosure

Headers are well organized, but no bundle files exist and the ~100-line output template is inlined in SKILL.md where a references/ template file belongs; at ~215 lines the under-50-line simple-skill exception does not apply. Some structure with content that should be separate kept inline matches anchor 3 rather than anchor 4's 'most content appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

80%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: concrete, comprehensive, third-person, with an explicit use-context. The main gaps are absent natural trigger synonyms and a 'when' clause that describes contexts rather than user-trigger phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with specifics: 'extract their brand voice, writing style, and tone guidelines', 'Reads 10-20 of their best content pieces', 'produces a brand voice profile covering tone, vocabulary level, sentence structure, formatting patterns, CTAs, and target persona'. Coverage is comprehensive and in third person, matching the anchor 5 example rather than the minor-gaps anchor 4.

5 / 5

Completeness

The 'what' is explicit and detailed, and a 'when' is present ('Useful before writing outreach, content, or campaigns that should match a client's existing voice'), so it exceeds anchor 3's merely-implied 'when'. However the 'when' is not phrased as concrete user triggers ('Use when the user asks to match a brand's voice'), keeping it at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('brand voice', 'writing style', 'tone', 'outreach', 'campaigns', 'match a client's existing voice') but misses common synonyms and phrasings like 'tone of voice', 'house style', or 'write like them'. Good coverage with a few natural terms missing fits anchor 4; it is not anchor 5's comprehensive synonym/extension-level coverage.

4 / 5

Distinctiveness Conflict Risk

'Brand voice', 'tone guidelines', and 'match a client's existing voice' define a clear niche distinct from generic content or writing skills, with only minor overlap risk against copywriting/content-strategy skills. It is mostly distinct (anchor 4) but not the minimal-conflict clarity of anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.