Claude Code Content Team

A modular, skill-based content system that gives founders and small teams a repeatable workflow for researching, ideating, and drafting content across multiple platforms.

Four skills work together as a content pipeline:

Skill	What It Does
/research	Gathers structured insights on any topic with citations
/talking-points-builder	Extracts categorized talking points from research or any source
/new-content-ideas	Acts as an editor — prioritizes talking points into what to create
/crafter	Drafts platform-ready content for LinkedIn, X, Threads, or TikTok

/research ──► /talking-points-builder ──► /new-content-ideas ──► /crafter

---

Choose Your Setup Path

Path 1 — Skills in Claude Code (simpler)

Runs entirely inside Claude Code. No web server, no API key, no coding. Claude guides you through setup interactively.

What you need: Claude Code installed, this project folder downloaded.

How to set up: Open the guided setup prompt — copy the prompt, paste it into Claude Code, and answer the questions. Claude creates your config files and adds the skills to your settings automatically.

---

Path 2 — Web App (more polished)

A Next.js browser interface with a proper UI for running each stage of the workflow. Requires Node.js and an Anthropic API key.

What you need: Node.js v18+, an Anthropic API key.

How to set up: See the app setup guide.

---

Manual Setup Guide (Skills Path)

Step 1: Get the Files

Download or clone this repository to your local machine:

git clone https://github.com/YOUR-USERNAME/Claude-Code-Content-Team.git

Or download as a ZIP and unzip it somewhere you can find it.

---

Step 2: Fill In Your Config Files

The Config/ folder contains two template files. Copy each one and fill in your own details.

2a. Copy the templates

cp Config/content-profile.template.yaml Config/content-profile.yaml
cp Config/writing-style.template.yaml Config/writing-style.yaml

Or on Windows:

copy Config\content-profile.template.yaml Config\content-profile.yaml
copy Config\writing-style.template.yaml Config\writing-style.yaml

2b. Edit Config/content-profile.yaml

Fill in your brand, audience, content pillars, and topics. Every field has a comment explaining what to put there.

Key fields to focus on:

• brand.name and brand.tagline — who you are
• audience.primary — a one-paragraph description of your target reader/viewer
• audience.pain_points — the problems they're trying to solve
• content_pillars — 3–5 themes your content always returns to
• platforms.primary — your main publishing platform

2c. Edit Config/writing-style.yaml

Fill in how you want to sound. Key fields:

• tone — 3–5 words describing your voice
• do / avoid — specific rules the skills will follow when drafting
• platform_rules — character limits and style notes per platform

These files stay on your machine and are not shared. The .gitignore already excludes them.

---

Step 3: Add the Skills to Claude Code

Open your Claude Code settings file. On Mac/Linux:

~/.claude/settings.json

On Windows:

C:\Users\YOUR-USERNAME\.claude\settings.json

Add the skills block below. Replace /full/path/to with the actual path to where you saved the project:

{
  "skills": [
    {
      "name": "research",
      "path": "/full/path/to/Claude-Code-Content-Team/Skills/research.md",
      "description": "Research topics with structured citations"
    },
    {
      "name": "talking-points-builder",
      "path": "/full/path/to/Claude-Code-Content-Team/Skills/talking-points-builder.md",
      "description": "Extract talking points from source material"
    },
    {
      "name": "new-content-ideas",
      "path": "/full/path/to/Claude-Code-Content-Team/Skills/new-content-ideas.md",
      "description": "Prioritize talking points for content creation"
    },
    {
      "name": "crafter",
      "path": "/full/path/to/Claude-Code-Content-Team/Skills/crafter.md",
      "description": "Draft platform-specific content"
    }
  ]
}

If your settings.json already has other content, add the skills block alongside existing keys — do not replace the whole file.

Restart Claude Code after saving.

---

Step 4: Test the Workflow

Open Claude Code in your project directory and try each skill in sequence:

/research [any topic relevant to your niche]

Take the output and pass it to:

/talking-points-builder [paste the research output here]

Then:

/new-content-ideas [paste the talking points output here]

Then pick a Priority 1 idea and draft it:

/crafter [paste the talking point] for LinkedIn

---

Step 5 (Optional): Add Perplexity for Better Research

The /research skill works out of the box using Claude's built-in web search. If you want deeper, more current research results with stronger citations, you can connect Perplexity.

What Perplexity adds

• Real-time web results with citations already embedded
• Better coverage of recent news and niche topics
• More reliable sourcing than general web search

How to set it up

1. Get a Perplexity API key at perplexity.ai

2. Add the Perplexity MCP server to your Claude Code settings:

{
  "mcpServers": {
    "perplexity": {
      "command": "npx",
      "args": ["-y", "server-perplexity-ask"],
      "env": {
        "PERPLEXITY_API_KEY": "your-api-key-here"
      }
    }
  }
}

3. Restart Claude Code.

Once configured, the /research skill will automatically detect Perplexity and use it instead of standard web search. No changes to the skill file are needed.

Without Perplexity, /research still works well using Claude's built-in WebSearch and WebFetch. Perplexity is an upgrade, not a requirement.

---

How the Skills Work Together

/research

Conducts focused research and returns structured findings.

• Input: Topic, URL, or question
• Output: Key insights, trends, best practices, data points, and sources with links

/research What are the latest trends in remote work tools?

---

/talking-points-builder

Extracts talking points from any source material — research output, articles, transcripts, or documents.

• Input: Pasted text, URL, document, or /research output
• Output: Talking points organized across 7 editorial categories (Educational, Myth-Buster, Spicy Take, Head Nod, Data Nugget, Story Spark, Trend-Inspired Angle)

/talking-points-builder [paste text, URL, or research output]

---

/new-content-ideas

Acts as an editor deciding what gets made. Evaluates talking points against your Content Profile.

• Input: Output from /talking-points-builder
• Output: Ideas sorted into Priority 1 (create now), Priority 2 (strong contenders), Priority 3 (hold), and Not Recommended

/new-content-ideas [paste talking points output]

---

/crafter

Generates a single platform-ready first draft from a selected talking point.

• Input: A talking point + target platform
• Output: One clean draft respecting platform constraints

Platform	Target Length	Hard Max
LinkedIn	900–1,400 chars	1,800 chars
X	220–260 chars	280 chars
Threads	300–450 chars	500 chars
TikTok	75–110 words	30–45 sec script

/crafter [talking point] for LinkedIn

To adjust after the first draft:

/crafter same idea but for TikTok
/crafter make it shorter
/crafter adjust the tone — less formal

---

Project Structure

Claude-Code-Content-Team/
├── Skills/
│   ├── research.md                      # Research skill
│   ├── talking-points-builder.md        # Talking points extraction skill
│   ├── new-content-ideas.md             # Content prioritization skill
│   └── crafter.md                       # Content drafting skill
├── Config/
│   ├── content-profile.template.yaml    # Template — copy and fill in
│   ├── writing-style.template.yaml      # Template — copy and fill in
│   ├── content-profile.yaml             # Your personal config (not shared)
│   └── writing-style.yaml              # Your personal config (not shared)
├── content-team-ui/                     # Optional web app
│   └── README.md                        # App setup guide
├── SETUP-PROMPT.md                      # Guided setup prompt for skills path
├── README.md
└── CLAUDE.md

---

Resources

• Claude Code Documentation
• Claude Code Skills Guide
• Claude Code MCP Guide