CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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, highly actionable instruction skill with clear workflows, validation checkpoints, and a clean one-level reference structure. The only nit is mild redundancy between the Anti-Patterns and Interview-discipline sections.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no beginner explanations of branding or the named frameworks), but the Anti-Patterns section restates rules already in Interview discipline and When-to-Activate overlaps the frontmatter description.

4 / 5

Actionability

Provides copy-paste-ready guidance: exact laddering phrasing ('Why does that matter to you?'), concrete projective prompts, a module table with filenames, and a complete state.json schema with absolute file paths.

5 / 5

Workflow Clarity

Clear sequencing (Session start protocol, Module sequence, State write protocol) with explicit validation — saturation signal as a feedback loop, participant/path/moduleFile validation, and the terminal-module state handling that prevents a resumption bug.

5 / 5

Progressive Disclosure

The body is an overview that signals one-level-deep references via the module-sequence table, and all eight referenced files (10_purpose-why.md through 90_SYNTHESIS.md) exist in ./references/, giving easy navigation.

5 / 5

Total

19

/

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 tight, specific description that covers what and when clearly, names its methods and modules, and is well differentiated from sibling skills. Slight headroom only in trigger-term synonym coverage.

DimensionReasoningScore

Specificity

Lists many concrete actions and components — 'discover or articulate its identity', 'purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what (structured multi-session interviews across 8 modules producing a master brandbook with disk-persisted state) and when ('Use when a brand needs to discover or articulate its identity') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Strong natural branding vocabulary ('brand', 'identity', 'positioning', 'voice', 'narrative', 'brandbook') but misses common synonyms a user might say such as 'rebrand', 'brand strategy', or 'branding'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — multi-session structured brand-identity interviews with named frameworks and a brandbook output — making it unlikely to fire for unrelated skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
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.