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

89%

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

The canonical home for this skill is creative-direction in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 instruction-only skill: concrete and executable workflow guidance, specific framework content with named positions and heuristics, and exemplary progressive disclosure backed by a verified one-level-deep bundle. The deductions are minor — some content is duplicated across sections (When NOT to use vs. Failure patterns, Workflow vs. Failure patterns) and the workflow's start and end lack explicit validation checkpoints.

Suggestions

Consolidate duplicated content: the "develop taste" caution appears in both "When NOT to use" and "Failure patterns", and the Functional + Provocative tension example appears in both Workflow step 4 and "Failure patterns" — keep each point in one place to tighten conciseness.

Add an explicit input-completeness check at the end of Workflow step 1 (confirm project name, description, audience, and goal before walking the axes) and a final step that reviews the completed brief against the template's six sections before handoff.

The blockquote about assembling worked examples from a reference brand library is repeated nearly verbatim in both the body and references/axes-explained.md; keep it only in the reference to remove redundancy.

DimensionReasoningScore

Conciseness

Largely lean — no generic concept explanations Claude already knows, and every section (when/not-when, inputs, axes, workflow, failure patterns, output format) is functional. Matches anchor 4 ("Efficient; minor instances of over-explanation that could be trimmed") rather than anchor 5: the "develop taste" point appears in both "When NOT to use" and "Failure patterns", and the Functional + Provocative tension is explained in both Workflow step 4 and "Failure patterns".

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a 7-step workflow with named actions ("present the positions, surface tradeoffs, and capture the user's selection plus reasoning"), four named positions per axis with per-axis choice heuristics, concrete tension examples (Functional + Provocative, Authority + Functional), a concrete rejection-list example ("No testimonial walls. No stock photography. No exclamation marks."), and a real template and worked example in the bundle. Matches anchor 5's "specific examples cover the common cases" for a non-code skill.

5 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced and includes one explicit feedback checkpoint ("Flag tensions and ask the user to confirm or reconsider"), plus the failure-patterns list functions as a process checklist. But validation of input completeness before the axis walk and a final check of the brief against the template's six sections are implicit rather than explicit steps — anchor 4's "most checkpoints present; minor validation gaps", not anchor 5's explicit validation steps throughout.

4 / 5

Progressive Disclosure

The body is a clear overview (one-line positions per axis with choice heuristics) and all three referenced files — references/axes-explained.md, references/brief-template.md, references/example-aesthetic-brief.md — exist as real, substantive files referenced at the right moments (template cited in Workflow step 6) with descriptive annotations in the "Reference files" section. Verified the bundle structure: references are one level deep with no nested references, and the split is appropriate (depth and brand examples in the reference, structure in the template, a full worked example separately). Matches anchor 5.

5 / 5

Total

18

/

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: a concrete two-part capability statement with the four axes enumerated, explicit use-when conditions, natural trigger phrases including question-form triggers, and an explicit negative-trigger list with a named boundary against `creative-brief`. It maintains third-person voice and avoids padding despite its length. The only gap is a few missing common synonyms in the trigger list.

DimensionReasoningScore

Specificity

Names two concrete, well-specified 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 as required input" — noticeably more concrete than anchor 3's bare two-action example, but stopping short of anchor 5's "multiple specific concrete actions; comprehensive coverage" since only two top-level actions are given (input gathering and tension-surfacing are not stated).

4 / 5

Completeness

Explicitly answers what ("Walk the user through four directional axes... and 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, or when multiple downstream aesthetic-producing skills need a shared brief"), plus concrete trigger phrases and an explicit "Does NOT fire for..." exclusion list. Matches anchor 5's "clearly and explicitly answers both what AND when with concrete trigger phrases"; anchor 4 would require the when to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"Triggers on creative direction, aesthetic direction, set the aesthetic, define the visual direction, what's the vibe, what's the tone, the four axes" covers natural phrasings users would actually say, including question forms like "what's the vibe". Matches anchor 4 ("Good keyword coverage; a few natural terms missing") rather than anchor 5, since common synonyms such as "look and feel", "visual identity", "mood", or "brand aesthetic" are absent.

4 / 5

Distinctiveness Conflict Risk

Claims a clear niche as "The aesthetic depth layer, distinct from `creative-brief` (operational kickoff: scope, audience, deliverables, constraints)", with distinctive triggers and negative triggers ("tactical single-piece work, already-documented direction, purely functional output") that steer adjacent use cases away. Matches anchor 5 ("Clear niche with distinct triggers; minimal conflict risk"); anchor 4's minor overlap risk with a closely related skill is largely defused by the explicit creative-brief boundary and the framing of art-direction skills as downstream consumers.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/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.