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

Content Brief

ASecurity

Create detailed content briefs. Use when: keyword targets, outline, structure, voice guidelines, SEO requirements.

847 stars
0 votes
0 copies
1 views
Added 6/9/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 6/9/2026

$npx -y skills add indranilbanerjee/digital-marketing-pro --skill content-brief --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Content Brief?

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

Security grade badge for Content Brief
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/indranilbanerjee-content-brief/badge)](https://www.skillsdirectory.com/skills/indranilbanerjee-content-brief)

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: content-brief
description: "Create detailed content briefs. Use when: keyword targets, outline, structure, voice guidelines, SEO requirements."
argument-hint: "[topic]"
---

# /digital-marketing-pro:content-brief

## Purpose

Create a production-ready content brief that a writer can execute without additional context. Includes keyword strategy, content outline, structural requirements, brand voice guidelines, and on-page SEO specifications.

## Input Required

The user must provide (or will be prompted for):

- **Topic or working title**: What the content is about
- **Content type**: Blog post, landing page, pillar page, guide, whitepaper, etc.
- **Target keyword(s)**: Primary keyword or topic cluster (or ask for research)
- **Target audience**: Who this content is for
- **Funnel stage**: Awareness, consideration, or decision
- **Competitive URLs**: Optional — existing content to outperform

## Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
2. Research keyword landscape: primary keyword, secondary keywords, related questions
3. Analyze top-ranking content for the target keyword to identify gaps and opportunities
4. Define content angle and unique value proposition versus existing results
5. Build a detailed outline with H2/H3 structure, key points per section, and word count targets
6. Specify on-page SEO requirements: title tag, meta description, URL slug, internal links, schema markup
7. Document voice and tone guidelines specific to this piece
8. Define success metrics: target ranking, traffic, engagement, conversions

## Output

A structured content brief containing:

- Target keyword map (primary, secondary, LSI, questions to answer)
- Content outline with heading hierarchy and key points per section
- Word count target and content format specifications
- Brand voice and tone guidance for this specific piece
- On-page SEO checklist (title, meta, headers, links, schema)
- Visual/media requirements — specify whether visuals are AI-generated and which model (see guidance below)
- Internal and external linking strategy
- Success metrics and measurement plan

### Visual/media spec — AI generation guidance (May 2026)

If the piece includes AI-generated images, infographics, or short video, the brief must specify:

- **Model**: `Nano Banana Pro` for high-fidelity stills with on-image text (best text rendering in any image model as of May 2026), `Gemini Omni` for connected hero-image + cutdown-video + audio packages, or alternatives (Midjourney, Firefly, gpt-image-1) for concept work.
- **Provenance marking**: All AI assets shipped to EU readers must carry C2PA Content Credentials. Default to "sign all AI visuals" — the cost of running `/digital-marketing-pro:c2pa-metadata` post-production is trivial vs the Article 50 penalty exposure.
- **Deepfake / synthetic-human flag**: If the visual includes a photoreal human (real or synthetic), call this out — synthetic humans typically need a visible disclosure under EU Article 50 draft guidelines (May 2026).
- **Editorial-responsibility owner**: For long-form on health, finance, elections, or public-safety topics, name the human editor who will sign off. AI-written copy on these topics requires the editorial-responsibility carve-out to skip an "AI-assisted" byline disclosure — see `skills/context-engine/compliance-rules.md` §1.1b.i.

## Agents Used

- **content-creator** — Outline structure, angle, voice guidelines, content strategy
- **seo-specialist** — Keyword research, on-page SEO requirements, competitive content analysis

Attribution

indranilbanerjeeindranilbanerjee
View sourceSee grades on GitHubMore from indranilbanerjee →
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 →