CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

creative-direction

Walk the user through four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) and produce a structured aesthetic brief that downstream content, copy, design, and art-direction skills consume as required input. The aesthetic depth layer, distinct from `creative-brief` (operational kickoff: scope, audience, deliverables, constraints). Use when a project needs aesthetic coherence across many small decisions and the user has only a vague feeling, or when multiple downstream aesthetic-producing skills need a shared brief. Triggers on creative direction, aesthetic direction, set the aesthetic, define the visual direction, what's the vibe, what's the tone, the four axes. Does NOT fire for a general kickoff brief (use `creative-brief`), tactical single-piece work, already-documented direction, purely functional output, or locked production-stage work.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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-crafted instruction-only skill body: a tight framework with four well-defined axes, a concrete sequenced workflow with a confirm checkpoint, and a real, well-signaled reference bundle one level deep. It stops short of top marks because some duplication between body and reference file, abstract spots in the workflow, and the absence of a final brief-validation step leave minor gaps on every dimension.

Suggestions

Deduplicate the axis coverage: keep only a one-line summary of each axis's positions in the body and move the full position lists to axes-explained.md, which already covers them in depth.

Consolidate the Functional + Provocative tension guidance into one place (either Workflow step 4 or Failure patterns) instead of repeating it in both.

Add a final workflow step that validates the completed brief against the Required inputs (project name, audience, goal) and confirms it with the user before handoff to downstream skills.

DimensionReasoningScore

Conciseness

Mostly lean, aphoristic prose that assumes Claude's competence ('Frameworks produce competent output. Coherent output requires a brief.') with no padding explaining known concepts. Not a 5 because of minor duplication: the Functional + Provocative tension example appears in both Workflow step 4 and Failure patterns, and 'When NOT to use' restates boundary guidance already in the frontmatter description.

4 / 5

Actionability

Provides a concrete 7-step workflow, enumerated positions per axis, a numbered 6-part output structure, and specific examples ('No testimonial walls. No stock photography. No exclamation marks.'). Not a 5 because several steps remain abstract ('present the positions, surface tradeoffs', 'Write a one-paragraph synthesis') and the worked example is deferred entirely to a reference file rather than covering common cases inline.

4 / 5

Workflow Clarity

The Workflow section gives a clearly sequenced 1-7 process with a genuine checkpoint in step 4 ('Flag tensions and ask the user to confirm or reconsider') and a Failure patterns section covering error recovery. Not a 5 because no step validates the finished brief against the Required inputs or with the user before handoff; not a 3 because the sequence and confirm-checkpoint are explicit and this is not a destructive or batch operation.

4 / 5

Progressive Disclosure

Three real, one-level-deep reference files (axes-explained.md, brief-template.md, example-aesthetic-brief.md — all verified present and substantive), each described in a dedicated Reference files section and linked at point of use (brief-template in Workflow step 6). Not a 5 because the body inlines the full axis-position taxonomy while axes-explained.md re-covers the same positions with added depth, creating moderate overlap that could be split more cleanly.

4 / 5

Total

16

/

20

Passed

Description

87%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: it names the concrete capability (four enumerated directional axes producing a structured aesthetic brief), gives explicit 'Use when' triggers including natural user phrases, and cleanly separates itself from sibling skills with both positive triggers and a 'Does NOT fire for' boundary. The only gaps are a slightly thin action list and a few missing synonyms in trigger coverage.

DimensionReasoningScore

Specificity

Lists several specific concrete actions — 'Walk the user through four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition)' and 'produce a structured aesthetic brief that downstream content, copy, design, and art-direction skills consume' — with the axes enumerated and the output artifact named. Not a 5 because it rests on only two verbs of action rather than a comprehensive action list; not a 3 because the actions are explicitly enumerated and specific, not generic.

4 / 5

Completeness

Explicitly answers both what ('Walk the user through four directional axes... produce a structured aesthetic brief...') and when ('Use when a project needs aesthetic coherence across many small decisions and the user has only a vague feeling'), with concrete trigger phrases and negative boundary guidance. Matches the score-5 anchor.

5 / 5

Trigger Term Quality

Good natural trigger coverage: 'Triggers on creative direction, aesthetic direction, set the aesthetic, define the visual direction, what's the vibe, what's the tone, the four axes' includes casual phrases users would actually say. Not a 5 because common synonyms like 'look and feel', 'mood', 'visual style', or 'brand personality' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with minimal conflict risk: it differentiates from siblings ('distinct from `creative-brief` (operational kickoff: scope, audience, deliverables, constraints)') and lists explicit negative triggers ('Does NOT fire for a general kickoff brief (use `creative-brief`), tactical single-piece work...'). Unlikely to fire for the wrong skill.

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

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