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.

79

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

100%

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

A well-structured instructional skill: concise, actionable, with a sequenced workflow that includes a stress-test checkpoint and well-organized one-level-deep reference files. It avoids verbosity and leaves detailed material to clearly signaled references.

DimensionReasoningScore

Conciseness

Lean instructional body with no conceptual padding (no 'what a brief is' lecture), assumes Claude's competence, and self-imposes tight budgets ('two pages, not ten', 'under 1500 words'). Every section earns its place, matching the 'lean and efficient' anchor rather than the 'could be tightened' 2.

3 / 3

Actionability

Gives concrete executable guidance: ten defined brief sections, specific elicitation prompts, a precise deliverable spec ('Homepage with hero, three feature blocks, testimonial carousel, and contact CTA'), and a fillable template. As an instruction-only skill the guidance is fully actionable, matching the top anchor.

3 / 3

Workflow Clarity

The 7-step workflow includes an explicit validation checkpoint (step 5 'Stress-test... check the brief against the failure patterns... If any apply, revise before showing the user') with a feedback loop. Not a 2 because the checkpoint and revise loop are explicit rather than implicit.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview with three well-signaled, one-level-deep references (creative-brief-template.md, voice-and-tone-guide.md, example-brief.md), all verified present in references/. Content is appropriately split and easy to navigate, matching the top anchor rather than the 'could be better organized' 2.

3 / 3

Total

12

/

12

Passed

Description

100%

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 that concretely states the skill's purpose and supplies an explicit 'Use when' clause with a broad, natural set of trigger terms. Its clear niche and internal cross-referencing keep conflict risk low.

DimensionReasoningScore

Specificity

Names concrete actions ('Create or refine a creative brief') plus specific scenarios (kicking off a website, beginning a brand build, briefing a designer/developer/AI agent, aligning a team), matching the 'lists multiple specific concrete actions' anchor. It is not a 2 because coverage is comprehensive rather than partial, and uses correct third-person voice.

3 / 3

Completeness

Explicitly states what ('Create or refine a creative brief that bridges discovery and execution') and when with explicit triggers ('Use this skill whenever...'). Matches the 'clearly answers both what AND when with explicit triggers' anchor; not a 2 because the when-clause is explicit, not implied.

3 / 3

Trigger Term Quality

Packs natural phrasing users would actually say ('creative brief, design brief, brand brief, project kickoff, kicking off, briefing the team, where do we start, how do we start, write a brief, scope this project'), giving good coverage of common variations. Not a 2 because it covers the natural vocabulary rather than missing common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (creative briefs bridging discovery and execution) with distinct triggers, and the body cross-references adjacent skills (design-standards, pm-spec-writing, brand-discovery) to reduce overlap. Unlikely to conflict, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

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.