CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

creative-brief

Create or refine a creative brief that bridges discovery and execution. Use this skill whenever the user is starting a new project, kicking off a website, beginning a brand build or redesign, briefing a designer or developer or AI agent, or trying to align a team before building. Triggers on creative brief, design brief, brand brief, project kickoff, kicking off, briefing the team, project intake, design direction, brief the designer, brief the dev, where do we start, how do we start, write a brief, project overview, scope this project, align on direction. Also triggers when the user has a vague idea and needs to make it concrete enough to hand off, even if they do not say 'brief' explicitly.

Quality

90%

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.

The body is a tightly written, highly actionable instruction skill: a complete output framework, ready-to-use elicitation prompts, a validated workflow with stress-test feedback loops, and clean one-level-deep disclosure into real bundle files. The only nit is mild duplication of the frontmatter description in the intro and 'When to use' sections.

Suggestions

Trim the intro line and 'When to use' bullets, which duplicate trigger scenarios already present in the frontmatter description loaded at invocation time.

Consider moving the intake prompts (about 20 lines) into a references/intake-questions.md file, keeping only the top two or three inline, to further slim the always-loaded body.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific guidance (ten required inputs, failure patterns, intake prompts) and wastes no tokens teaching concepts Claude already knows, but two spots could be trimmed: the intro sentence "Bridges discovery and execution. Translates 'we want a website'..." and the 'When to use' bullets largely restate trigger scenarios already in the frontmatter description. That is minor trimmable redundancy matching the 4 anchor, short of the every-token-earns-its-place 5.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: a concrete ten-section output structure, a worked objective/signal example ("3 percent conversion from homepage to signup within 30 days of launch"), copy-paste intake prompts ("Pretend it is six months after launch. What number tells you it worked?"), a template path, a 1500-word limit, and a specific deliverable path (creative-brief.md in the project root). It also disambiguates edge cases like what counts as a deliverable, matching the 5 anchor's 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

The seven-step workflow (read conversation, identify gaps, run intake, draft, stress-test, deliver, optional handoff) has explicit validation checkpoints and feedback loops: a numeric intake threshold ("If you have fewer than five of these, run a quick intake first") and a stress-test step that checks the draft against the failure-pattern checklist and revises before showing the user. This matches the 5 anchor's explicit validation with error-recovery loops; the work is neither destructive nor batch, so no cap applies.

5 / 5

Progressive Disclosure

SKILL.md stays an overview while detail lives in three one-level-deep references, all of which actually exist in references/ (creative-brief-template.md, voice-and-tone-guide.md, example-brief.md). References are well-signaled both inline (section 5 links the voice guide, the workflow links the template) and in a dedicated 'Reference files' section with conditional read guidance ("Read the template before drafting. Read the voice guide if the user has not already specified a voice"). This matches the 5 anchor's clear overview with well-signaled one-level-deep references.

5 / 5

Total

19

/

20

Passed

Description

86%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 with excellent trigger coverage and an explicit what/when structure. The main gaps are modest action specificity (only 'create or refine' is stated) and slight overlap risk with sibling discovery/direction skills via terms like 'design direction'.

Suggestions

Surface one or two more concrete capabilities in the description itself (e.g., 'elicits missing inputs through targeted intake questions and stress-tests briefs against common failure patterns') to lift specificity beyond two actions.

Drop or narrow the 'design direction' and 'project overview' trigger terms, which collide with the sibling creative-direction and brand-discovery skills referenced in the body.

DimensionReasoningScore

Specificity

"Create or refine a creative brief that bridges discovery and execution" names the domain plus two concrete actions (create, refine), matching the 1-2 concrete actions anchor. It is not a 4 because the description does not list several specific actions (eliciting missing inputs, stress-testing against failure patterns, template-based output all appear only in the body), and not a 2 because the stated actions are concrete rather than generic.

3 / 5

Completeness

The description explicitly answers both questions: what ("Create or refine a creative brief that bridges discovery and execution") and when ("Use this skill whenever the user is starting a new project, kicking off a website, beginning a brand build or redesign, briefing a designer or developer or AI agent, or trying to align a team before building") with concrete trigger phrases. This matches the anchor for a clear, explicit what-and-when; a 4 would require the 'when' to be less explicit or specific.

5 / 5

Trigger Term Quality

The trigger list is comprehensive and natural: "creative brief, design brief, brand brief, project kickoff, kicking off, briefing the team, project intake, ... where do we start, how do we start, write a brief, project overview, scope this project", plus the catch-all for users with a vague idea who never say 'brief'. This exceeds the 'a few natural terms missing' bar of a 4 with synonyms and scenario phrasings users would actually say.

5 / 5

Distinctiveness Conflict Risk

"Creative brief" / "brand brief" / "brief the designer" form a clear niche, but the trigger terms "design direction" and "project overview" overlap with sibling skills (the body itself routes aesthetic direction to creative-direction and early research to brand-discovery). That is minor overlap risk with closely related skills, matching the 4 anchor rather than the minimal-conflict 5 or the still-overlapping 3.

4 / 5

Total

17

/

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/creative-brief/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.