CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

Quality

91%

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, actionable instruction skill with a clear validated workflow and clean progressive disclosure through three real reference files. The only minor inefficiency is a redundant restatement of the reference files at the end.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding concept over-explanation, but the closing "Reference files" section restates the three references already linked inline earlier, a minor redundancy that could be trimmed. Not a 5 because of that duplicated reference listing; not a 3 because the rest is efficient and tightly written.

4 / 5

Actionability

Highly actionable for an instruction-only skill: ten required inputs, ten brief sections each with concrete fill guidance and a worked objective/signal example, specific elicit prompts, and a failure-pattern checklist with concrete pushback responses. Per the code-vs-instruction scoring note, the absence of code is not penalized because the guidance is specific and executable.

5 / 5

Workflow Clarity

A clear seven-step workflow (read context → identify gaps → run intake → draft → stress-test → deliver → hand off) with an explicit validation checkpoint ("check the brief against the failure patterns... If any apply, revise before showing the user") and a feedback loop, plus the failure-pattern list functioning as a checklist. Not lower because the sequence and gate are explicit.

5 / 5

Progressive Disclosure

SKILL.md stays a concise overview while detail (fillable template, worked example, voice frameworks) is split into three real one-level-deep reference files, each linked inline at the relevant section and summarized in a closing "Reference files" section with explicit guidance on when to read each. Navigation is easy and references are well-signaled.

5 / 5

Total

19

/

20

Passed

Description

91%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, trigger-rich description that clearly states what the skill does and when to invoke it, with comprehensive natural-language trigger terms. Minor room to improve distinctiveness by folding a brief disambiguation cue into the description itself.

DimensionReasoningScore

Specificity

"Create or refine a creative brief that bridges discovery and execution" names the domain and core actions, and the description enumerates several concrete scenarios (website, brand build, briefing a designer/developer/AI agent), leaving only minor coverage gaps. Not a 5 because the actionable verbs are limited to create/refine rather than a comprehensive set of distinct operations.

4 / 5

Completeness

It explicitly answers both what ("Create or refine a creative brief that bridges discovery and execution") and when ("Use this skill whenever..." plus a dedicated "Triggers on..." clause with concrete trigger phrases), satisfying the top anchor exactly.

5 / 5

Trigger Term Quality

An extensive list of natural trigger phrases including synonyms and casual phrasings users actually say ("creative brief", "project kickoff", "where do we start", "how do we start", "scope this project", "align on direction"), plus an explicit catch-all for vague unstated intents. Comprehensive coverage with synonyms matches the top anchor.

5 / 5

Distinctiveness Conflict Risk

The brief-writing niche is clearly scoped to bridging discovery and execution, which distinguishes it from adjacent skills, but there is minor overlap risk with closely related strategy skills (e.g. brand-discovery, pm-spec-writing) that the description does not explicitly disambiguate. Not a 5 because boundary guidance lives in the body rather than the description.

4 / 5

Total

18

/

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.

Validation15 / 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
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.