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.

71

Quality

86%

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

The canonical home for this skill is brand-discovery in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 methodology skill: a four-dimension framework with concrete counts, sources, and outputs, a clear workflow, and clean one-level-deep progressive disclosure to real reference files. It falls short of top marks only on minor redundancy, missing inline worked examples, and absent validation checkpoints in the workflow.

Suggestions

Consolidate the per-dimension output specs (segment counts, competitor depth, territory counts) into one place — they currently appear both in the dimension sections and again in the workflow steps.

Add one inline worked example of a positioning territory statement (the statement / why it works / who resonates / risk fields filled in) so the per-territory documentation format is copy-paste ready.

Insert a validation checkpoint into the workflow (e.g., after audience research, confirm the 1-3 segments with the user before proceeding to competitor and territory work) to catch wrong-direction discovery early.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific guidance (four dimensions with sources, outputs, and failure patterns) and avoids explaining concepts Claude already knows, but there is minor redundancy — each dimension's output is stated both in its section and again in the workflow steps, and a few aphorisms ("The third is most often forgotten and most often the actual competitor") could be trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and specific — "5 to 8 interviews if possible", "3 to 8 competitors deep, including indirect and status-quo competitors", "3 to 5 distinct territories", per-competitor documentation fields, and a numbered report structure with a referenced template — but there is no inline worked example of a territory statement or competitor matrix row, which keeps it short of fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with scope calibration ("1 week for a startup pre-launch. 4 to 6 weeks for a major rebrand") and a substantive failure-patterns section, but there are no explicit validate/retry checkpoints (e.g., confirming segments with the user before generating territories), which the score-5 anchor requires.

4 / 5

Progressive Disclosure

The body is an overview that delegates heavy material to two well-signaled, one-level-deep references (references/discovery-report-template.md and references/interview-guide.md, both present in the bundle), each linked inline in the workflow and again in a dedicated Reference files section.

5 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: explicit what and when, a comprehensive natural trigger list with synonyms, and clear boundary framing that distinguishes upstream discovery from downstream brief/ideation work. The only minor weakness is that capabilities are expressed as covered topics rather than discrete actions.

DimensionReasoningScore

Specificity

"Run upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration" names the domain and enumerates several specific coverage areas, but the capabilities are framed as topics covered rather than the multiple discrete concrete actions (extract, fill, merge) of the score-5 anchor.

4 / 5

Completeness

It explicitly answers both what ("Run upstream brand discovery covering...") 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 and an additional edge-case trigger ("when a creative brief is requested but the upstream inputs... are not yet clear").

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-language coverage including synonyms and colloquial phrases users would actually say.

5 / 5

Distinctiveness Conflict Risk

The upstream-discovery niche is clear and explicitly disambiguated from downstream skills ("Also triggers when a creative brief is requested but the upstream inputs... are not yet clear"), giving it distinct triggers with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.