Agent skill
content-pillars
Define 3-5 content pillars for a brand. Each pillar gets a name, description, why it matters to the ICP, 10 starter topic ideas, recommended formats, and posting frequency. Use when user wants to "define content pillars", "organize my content strategy", "what should I post about", or needs a strategic content framework.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/content-pillars
SKILL.md
Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work
- BUSINESS.md — their business, products, positioning, brand voice, content strategy
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all context silently. Do not reference or summarize files unless asked.
Content Pillars
Purpose: Define 3-5 strategic content pillars that organize all content production around the user's expertise, audience needs, and business goals. Pillars ensure every piece of content serves a strategic purpose.
When to Activate
Use this skill when:
- User wants to define or refine their content pillars
- User asks "what should I post about?" or "how do I organize my content?"
- User needs a strategic content framework
- User wants to stop creating content randomly
What Makes a Good Pillar
A content pillar is NOT a topic — it's a strategic category. Each pillar should:
- Map to expertise — Something you can speak about with authority
- Serve the ICP — Addresses a real need your audience has
- Support the business — Leads toward your products/offers
- Be inexhaustible — Enough sub-topics for months of content
- Be differentiated — Your angle, not the generic industry take
Process
Step 1: Analyze the Intersection
Identify pillars at the intersection of three circles:
- What the user is an expert in (from USER.md / BUSINESS.md)
- What the ICP needs and cares about (from ICP.md)
- What supports the user's business goals
Step 2: Define 3-5 Pillars
For each pillar, provide:
- Name (short, memorable — 2-4 words)
- Description (one sentence — what this pillar covers)
- Why it matters to the ICP (connection to their pain/aspiration)
- How it supports the business (which product/offer it leads toward)
- 10 starter topics (specific ideas within this pillar)
- Best formats (newsletter, thread, video, LinkedIn, etc.)
- Recommended frequency (how often to publish in this pillar)
Step 3: Create the Pillar Map
Visual overview showing how pillars relate to each other and to the business.
Output Format
# Content Pillars: [Brand/Business Name]
---
## Pillar Overview
| # | Pillar | Description | ICP Connection | Business Goal |
|---|--------|-------------|----------------|---------------|
| 1 | [Name] | [Description] | [Why ICP cares] | [What it sells] |
| 2 | [Name] | [Description] | [Why ICP cares] | [What it sells] |
| 3 | [Name] | [Description] | [Why ICP cares] | [What it sells] |
| 4 | [Name] | [Description] | [Why ICP cares] | [What it sells] |
| 5 | [Name] | [Description] | [Why ICP cares] | [What it sells] |
---
## Pillar 1: [Name]
**Description:** [What this pillar covers]
**Why it matters to your audience:** [Connection to ICP needs]
**Business alignment:** [How it leads to products/offers]
**Recommended frequency:** [X posts per week/month]
### Best Formats
- [Format 1 — e.g., weekly newsletter deep-dives]
- [Format 2 — e.g., Twitter threads]
- [Format 3 — e.g., LinkedIn personal stories]
### 10 Starter Topics
1. [Specific topic idea]
2. [Specific topic idea]
3. [Specific topic idea]
4. [Specific topic idea]
5. [Specific topic idea]
6. [Specific topic idea]
7. [Specific topic idea]
8. [Specific topic idea]
9. [Specific topic idea]
10. [Specific topic idea]
---
## Pillar 2: [Name]
[Same structure...]
---
## Pillar 3: [Name]
[Same structure...]
---
[Continue for all pillars...]
---
## Content Mix Recommendation
**Weekly publishing cadence:**
| Pillar | Mon | Tue | Wed | Thu | Fri |
|--------|-----|-----|-----|-----|-----|
| [Pillar 1] | Newsletter | | LinkedIn | | |
| [Pillar 2] | | Thread | | Note | |
| [Pillar 3] | | | | | LinkedIn |
| [Pillar 4] | | | Tweet | | |
**Pillar ratio:** [e.g., 40% Pillar 1, 25% Pillar 2, 20% Pillar 3, 15% Pillar 4]
---
## Pillar Map
[Visual representation showing how pillars connect]
[Pillar 1: Core Expertise]
↕
[Pillar 2] ← [YOUR BRAND] → [Pillar 3] ↕ [Pillar 4: Lifestyle/Behind Scenes] ↓ [Business Goal / Product]
---
## Anti-Pillars (What NOT to Post About)
- [Topic to avoid #1 — why]
- [Topic to avoid #2 — why]
- [Topic to avoid #3 — why]
Quality Checklist
- 3-5 pillars defined (not too few, not too many)
- Each pillar has a clear name and one-sentence description
- ICP connection is specific (not "they'll find it interesting")
- Business alignment is clear (each pillar leads somewhere)
- 10 specific topic ideas per pillar (not vague)
- Format recommendations match the pillar's strengths
- Frequency is realistic for the user's capacity
- Content mix recommendation included
- Pillar map shows relationships
- Anti-pillars defined (what NOT to post about)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?