content-brief

A planning template and method for preparing search-optimised articles before a writer starts work.

In plain words
What is it for?
Use it to research primary and supporting keywords, analyse search results, find unanswered topics, create article headings, and record writing and search requirements.
Why use it?
It gives a content project a shared plan covering keywords, reader intent, competing pages, structure, length, readability, and links.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/nicepkg/ai-workflow/content-brief
Any agent
npx skills add nicepkg/ai-workflow --skill content-brief
Clone the repo
git clone --depth 1 https://github.com/nicepkg/ai-workflow

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 959 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.00959
Opus 5 $0.00014 $0.00479
Sonnet 5 $0.00006 $0.00192
Haiku 4.5 $0.00003 $0.00096

Measured 3d ago against content hash 93dee0433333, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

content-brief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

workflows/content-creator-workflow/.claude/skills/content-brief/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Content Brief

When to Use

  • Preparing briefs for content writers
  • Planning new content pieces
  • Documenting SEO requirements for articles
  • Aligning content with keyword research

Brief Creation Methodology

Step 1: Keyword Research

  1. Identify primary keyword (highest priority)
  2. Identify 3-5 secondary keywords
  3. Extract People Also Ask questions
  4. Note search intent (informational/commercial/transactional)

Step 2: SERP Analysis

  1. Analyze top 10 ranking pages
  2. Note average word count
  3. Identify common content format (listicle, guide, etc.)
  4. Find content gaps (topics competitors miss)

Step 3: Outline Creation

  1. Create H1 with primary keyword
  2. Plan H2s to cover required topics
  3. Plan H3s for detailed sections
  4. Map keywords to specific sections

Step 4: Requirements Definition

  1. Set word count target (based on competitors + 20%)
  2. Define E-E-A-T requirements
  3. Specify internal linking targets
  4. Set readability target (Flesch 60-70)

Brief Template

---
type: content-brief
created_by: {agent_or_command}
created_at: {timestamp}
keyword: "{keyword}"
session_id: {session_id}
session_path: {session_path}
status: complete
---

# Content Brief: {Title}

## Target Keyword
- **Primary**: {keyword}
- **Secondary**: {keyword2}, {keyword3}, {keyword4}
- **Questions to Answer**:
  1. {PAA question 1}
  2. {PAA question 2}
  3. {PAA question 3}

## Search Intent
- **Type**: Informational | Commercial | Transactional
- **User Goal**: {what user wants to accomplish}

## Content Specifications
- **Word Count**: {min}-{max} words
- **Format**: {article, listicle, guide, comparison}
- **Tone**: {professional, conversational, technical}
- **Target Audience**: {description}

## Required Sections
1. **{H2: Section topic}** - {brief description of what to cover}
2. **{H2: Section topic}** - {brief description}
3. **{H2: Section topic}** - {brief description}
4. **{H2: Section topic}** - {brief description}

## Featured Snippet Opportunity
- **Type**: {paragraph, list, table}
- **Target Query**: {question to answer}
- **Format**: {how to structure the answer}

## Competitor Analysis
| Competitor | Word Count | Unique Angle | Gap |
|------------|------------|--------------|-----|
| {site1} | {count} | {angle} | {what they miss} |
| {site2} | {count} | {angle} | {what they miss} |
| {site3} | {count} | {angle} | {what they miss} |

## E-E-A-T Requirements
- **Experience**: {specific examples to include from first-hand experience}
- **Expertise**: {depth of coverage required, technical accuracy needs}
- **Authority**: {sources to cite, data to include}
- **Trust**: {claims to verify, transparency requirements}

## Internal Linking
- Link to: {list of existing content to link}
- Anchor text suggestions: {list}

## SEO Requirements Checklist
- [ ] Keyword in title and H1
- [ ] Keyword in first 100 words
- [ ] 1-2% keyword density
- [ ] Minimum 3 internal links
- [ ] At least 1 external authoritative link
- [ ] Meta title: 50-60 characters
- [ ] Meta description: 150-160 characters with CTA
- [ ] Flesch Reading Ease: 60-70

Read the full file on GitHub · 125 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 125 lines · 28 tokens per session scan A 93dee0433333

Subscribe to this mod's changes

content-brief is a skill published in the GitHub repository nicepkg/ai-workflow (283 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 959 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

notion

Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.

elizaOS/eliza · 69 tokens

agentic-supply-chain-detection

Detect agentic supply-chain risks: compromised dependencies, malicious plugins/tools/models, and untrusted update sources.

Tencent/AI-Infra-Guard · 0 tokens

skill-vetter

Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.

netease-youdao/LobsterAI · 42 tokens

ondb

A logical analysis and reasoning tool for AI. Use when decomposing documents into structured knowledge, querying entities and relations, validating consistency, or indexing files. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", "analyze this document", entity CRUD, or cross-skill…

x-cmd/x-cmd · 71 tokens

finding-protocol

Operational-tier finding template — minimal fields for sub-agent decision support. Heavyweight deliverable promotion lives in skills/decepticon/final-report.

PurpleAILAB/Decepticon · 32 tokens

babysit

Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…

kirodotdev/KiroCrew · 137 tokens