CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/brand-discovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted skill description that clearly defines its scope (upstream brand discovery), lists concrete actions, provides explicit timing guidance ('very start of a brand or website project'), and includes a comprehensive set of natural trigger terms. The additional conditional trigger for creative briefs missing upstream inputs is a thoughtful inclusion that further clarifies when this skill should activate. Minor improvement could be made by using slightly more concise phrasing, but overall this is exemplary.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration.' It also specifies the context ('very start of a brand or website project') and what the user needs to understand.

3 / 3

Completeness

Clearly answers both 'what' (run upstream brand discovery covering audience research, competitive landscape, etc.) and 'when' (at the very start of a brand or website project, with explicit trigger terms listed and an additional conditional trigger for creative briefs missing upstream inputs).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff.' These are highly natural phrases a user would actually use.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche as an upstream/discovery-phase brand research skill, distinct from execution-phase skills like design, copywriting, or website building. The explicit scoping to 'very start of a brand or website project' and the specific trigger terms reduce conflict risk significantly.

3 / 3

Total

12

/

12

Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-organized strategic skill that clearly defines the brand discovery framework across four dimensions with appropriate sources and outputs. Its main weaknesses are the lack of concrete executable examples (sample outputs, template snippets inline) and missing validation checkpoints in the workflow. The content is moderately verbose—useful for a human reader but could be tightened for Claude's context window.

Suggestions

Add a concrete example for at least one dimension—e.g., a sample audience segment profile or a 3-row competitor matrix—so Claude has a copy-paste-ready output format to follow.

Insert explicit validation checkpoints in the workflow, such as 'Review audience segments with stakeholder before proceeding to competitor mapping' or 'Verify at least 3 competitors have sufficient data before generating territories.'

Move the detailed per-dimension breakdowns (sources, layers, methods) into a reference file and keep only summaries inline to reduce token cost and improve progressive disclosure.

Add a brief concrete example of a positioning territory statement with its proof point, audience, and risk to make the territory generation step more actionable.

DimensionReasoningScore

Conciseness

The skill is well-structured but somewhat verbose for Claude's capabilities. Sections like 'When to use' and 'When NOT to use' are helpful but could be tighter. Explanations like 'The third is most often forgotten and most often the actual competitor' and the failure patterns section add useful context but some entries explain things Claude would already understand (e.g., what demographic/psychographic means). Overall mostly efficient with some trimming opportunities.

2 / 3

Actionability

The skill provides a solid conceptual framework with clear categories, sources, and outputs for each dimension. However, it lacks concrete executable examples—no sample discovery report snippet, no example audience profile, no example competitor matrix row. The guidance is specific in structure but abstract in execution; Claude would need to interpret rather than follow copy-paste-ready templates inline.

2 / 3

Workflow Clarity

The 8-step workflow is clearly sequenced and logical. However, there are no validation checkpoints or feedback loops—no step says 'verify audience segments against data before proceeding' or 'review competitor matrix for completeness before territory generation.' For a multi-step discovery process where errors compound downstream, the absence of explicit validation gates is a notable gap.

2 / 3

Progressive Disclosure

The skill references two external files (discovery-report-template.md and interview-guide.md) and cross-references other skills (creative-brief, brand-ideation, seo-competitor). However, no bundle files were provided, so the references are unverifiable. The main content is quite long (~200+ lines) with detailed framework content inline that could potentially be split into reference files, particularly the per-dimension details.

2 / 3

Total

8

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
rampstackco/claude-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.