CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brand-discovery

Run upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration. Use this skill at the very start of a brand or website project when the user needs to understand who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand. Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff. Also triggers when a creative brief is requested but the upstream inputs (audience, competitors, problem space) are not yet clear.

Quality

90%

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

86%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 instruction-only skill: concrete checklists, counts, named tools, and a clean two-file bundle keep it actionable and easy to navigate. The gaps are modest — duplicated counts across sections and no explicit verification step inside the workflow itself.

DimensionReasoningScore

Conciseness

The body teaches domain-specific methodology Claude does not already know (interview counts, competitor layers, territory criteria) with no basic-concept padding. Minor trimming is possible: counts are duplicated between the framework and workflow sections ('5 to 8 interviews', '3 to 8 competitors', '3 to 5 territories' each appear twice) and a few editorial asides ('costs 10x downstream', 'where the puck is going') go beyond instruction — anchor 4, not 5, and clearly above 3's unnecessary-explanation level.

4 / 5

Actionability

The guidance is fully actionable for an instruction-only skill: specific quantities ('5 to 8 interviews', '3 to 8 competitors', '3 to 5 territories', '1 to 3 named segments'), a six-point per-competitor checklist, a five-point per-territory checklist, named tools (Similarweb, Ahrefs), an explicit report structure, and a linked fillable template. Per the scoring notes, the absence of code is not penalized when the guidance is this concrete — anchor 5.

5 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with scope-setting first, a failure-patterns checklist, and an anti-fabrication clause for missing data. However, no explicit validation/verification step sits inside the sequence itself (e.g., checking the report against failure patterns before handoff), and there is no validate-then-proceed loop — anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'), not anchor 5. The destructive/batch cap does not apply since this is a research/writing skill.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview of the four-dimension framework, with detail correctly split into two real, verified, one-level-deep reference files (discovery-report-template.md and interview-guide.md), each linked with a description in a 'Reference files' section and one additionally linked from the relevant workflow step — anchor 5.

5 / 5

Total

18

/

20

Passed

Description

91%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 what-and-when with a comprehensive, synonym-rich trigger list and explicit boundary handling against downstream brief skills. The only weaknesses are unnamed concrete deliverables and a few overly broad trigger terms that slightly raise conflict risk with sibling research skills.

DimensionReasoningScore

Specificity

The description lists several specific actions ('audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration') plus four concrete understanding goals ('who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand'). Minor gaps in coverage remain — concrete deliverables (segments, competitor matrix, territories) are never named — matching anchor 4 rather than the comprehensive, deliverable-level action list of anchor 5.

4 / 5

Completeness

It explicitly answers 'what' ('Run upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration') and 'when' ('Use this skill at the very start of a brand or website project when the user needs to understand...') with concrete trigger phrases, exactly matching anchor 5.

5 / 5

Trigger Term Quality

'Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff' provides comprehensive natural-term coverage including synonyms (audience/market/customer research) and phrasings a user would naturally say ('who is this for', 'kickoff'), matching anchor 5; file extensions are inapplicable to this file-less domain.

5 / 5

Distinctiveness Conflict Risk

The upstream-discovery niche is clear and the description even disambiguates the creative-brief boundary case ('Also triggers when a creative brief is requested but the upstream inputs... are not yet clear'). However, broad triggers like 'market research', 'customer research', 'intake', and 'kickoff' carry minor overlap risk with closely related research skills, fitting anchor 4 ('mostly distinct; minor overlap risk') rather than anchor 5's minimal conflict risk.

4 / 5

Total

18

/

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

rampstackco/claude-skills

Path

skills/brand-discovery/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.