Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Creative Intake

ASecurity

Creative brief intake: 7 required questions (purpose, audience, platform, tone, references, outcome, constraints), conversational technique.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsexpress

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill creative-intake --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Creative Intake?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Creative Intake
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-creative-intake/badge)](https://www.skillsdirectory.com/skills/aicodedecode-creative-intake)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: creative-intake
description: Creative brief intake: 7 required questions (purpose, audience, platform, tone, references, outcome, constraints), conversational technique.
---

# Creative Intake

Before the research stage, gather user intent through targeted questions.
Do NOT start production on a vague brief.

## Required Questions (ask conversationally, not as a survey)

1. **Purpose**: What is this video FOR? (educate, sell, inspire, document, entertain)
2. **Audience**: Who will watch it? (age, expertise, context — "my team" vs "YouTube public")
3. **Platform**: Where will it live? (YouTube, internal Slack, social media, presentation, website)
4. **Tone**: What should it FEEL like? (serious, playful, cinematic, raw, warm, provocative)
5. **References**: Any videos you admire or want this to feel like?
6. **Outcome**: What should the viewer DO or FEEL after watching?
7. **Constraints**: Budget ceiling? Timeline? Must-include content?

## How to Ask

Don't dump all 7 questions at once. Start with purpose and audience,
then let the conversation flow. Fill in gaps naturally.

If the user gives a detailed brief, skip questions they've already answered.

Identify what the user has already told you. If they said "I want a
cinematic brand film for Instagram," you already have purpose (inspire/sell),
platform (Instagram), and tone (cinematic). Ask what's missing.

## Handling Vague Briefs

When the user says something like "make me a video about X":

1. Acknowledge the topic — show you understood.
2. Ask the single most important missing question first (usually purpose or audience).
3. Based on their answer, ask the next most important gap.
4. Stop asking when you have enough to start research. You don't need perfect answers — research will fill in details.

## Handling Detailed Briefs

When the user provides a multi-paragraph brief or a document:

1. Summarize what you understood (1-2 sentences).
2. Call out any gaps: "I have a clear picture of the audience and tone, but I'd love to know — is there a specific outcome you're hoping for?"
3. Confirm the platform and constraints if not stated.

## Output

Produce an `intake_brief` (informal, not schema-validated) that the
research stage uses as its starting context. Include:

- Direct quotes from the user where their language reveals intent
- Explicit answers to each of the 7 questions (mark any that were inferred vs stated)
- Any reference videos/images the user mentioned
- Constraints that must be honored (budget, timeline, must-include)

The intake_brief is passed as context to the research-director, not as a
formal artifact. It exists to prevent the research stage from inventing
intent that the user never expressed.

## Handling Reference Video Input

When the user provides a video URL or file as their starting point:

1. **Read the video-reference-analyst skill** (`skills/meta/video-reference-analyst.md`)
   and follow its protocol. Do not proceed with standard creative intake.

2. The VideoAnalysisBrief replaces the need for most intake questions — it provides
   tone, structure, pacing, audience signals, and style information directly from the
   reference.

3. The remaining intake questions are:
   - What topic/subject for YOUR version? (if different from reference)
   - How long?
   - Narration yes/no?
   - Budget ceiling?

4. Do NOT ask "what should it feel like?" — the reference video IS the answer to that
   question. Extract tone from the VideoAnalysisBrief instead.

## What NOT To Do

- Do not present a numbered survey. This is a conversation, not a form.
- Do not ask questions the user already answered in their initial message.
- Do not delay production unnecessarily — if the brief is clear, move on.
- Do not invent answers for questions the user didn't address. Mark them as "not specified" and let the research stage handle ambiguity.
- Do not assume the user wants an explainer. Many users want cinematic, animation, or source-led work. Listen for signals.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →