CtrlK
BlogDocsLog inGet started
Tessl Logo

brand-strategy

A 7-part brand strategy framework for building comprehensive brand foundations. Trigger with phrases like "create brand strategy", "build brand brief", "define brand positioning", "brand messaging", "audience architecture", "brand truth", or "go-to-market brand plan". Use when working with brand strategy.

59

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body presents a clear, well-sequenced seven-phase methodology with useful discovery questions and output specifications, but it is padded with generic boilerplate sections that don't fit a brand-strategy skill and lacks explicit phase-to-phase validation checkpoints or any progressive disclosure into reference files.

Suggestions

Remove the generic Prerequisites, Instructions, Output, Error Handling, and Resources sections, which reference APIs, credentials, and CLI tools unrelated to brand strategy and add padding.

Add an explicit validation checkpoint between phases — e.g., 'Synthesize the user's answers into the phase output, confirm it with the user, and only then proceed to the next phase.'

Move the per-phase discovery questions and output templates into a reference file (e.g., references/PHASES.md) and keep SKILL.md as a concise overview that links one level deep to each phase.

DimensionReasoningScore

Conciseness

The seven phase sections are substantive and mostly earn their tokens, but the trailing Prerequisites/Instructions/Output/Error Handling/Resources sections are generic boilerplate ('Access to the branding environment or API', 'Refresh tokens or re-authenticate') unrelated to brand strategy, and the opener's 'the same process top agencies use with Fortune 500 clients' is marketing padding.

2 / 3

Actionability

Each phase supplies concrete discovery questions and a structured output spec, which is actionable, but the closing 'Instructions' section is vague ('Apply the recommended patterns from this skill', 'Validate the changes against expected behavior') and does not map to brand-strategy work, leaving guidance incomplete.

2 / 3

Workflow Clarity

The seven phases are clearly sequenced and the Examples handle out-of-order requests ('confirm Phases 1-3 are complete or gather that context first'), but there are no explicit validation checkpoints between phases (e.g., confirm the synthesized output with the user before proceeding), so checkpoints remain implicit.

2 / 3

Progressive Disclosure

The skill is a single ~225-line monolithic file with no references/scripts/assets bundle and no signaled external files; it has clear section structure, but per-phase discovery questions and output templates that could live in separate reference files are all inline.

2 / 3

Total

8

/

12

Passed

Description

90%

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

The description is well-constructed: it states the skill's purpose, supplies a rich set of natural trigger phrases, and includes an explicit 'Use when' clause in third-person voice. Its only weakness is that it names the domain rather than listing several distinct concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('7-part brand strategy framework') and the broad action ('building comprehensive brand foundations') but does not enumerate multiple concrete actions; it lists trigger phrases rather than distinct capabilities, so it sits at the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

Explicitly answers both 'what' ('A 7-part brand strategy framework for building comprehensive brand foundations') and 'when' ('Use when working with brand strategy') with explicit triggers, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Provides strong natural-language triggers a user would actually say — 'create brand strategy', 'build brand brief', 'define brand positioning', 'brand messaging', 'audience architecture', 'brand truth', 'go-to-market brand plan' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (brand strategy) with distinct, domain-specific triggers unlikely to collide with other skills, matching the level-3 anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.