Skip to content
Back to skills

Content Pillars

ASecurity

Define reusable social media content pillars for a product, founder, brand, or campaign. Use when a content calendar needs durable themes, repeatable post types, and clearer editorial direction.

  • 65 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 30, 2026
ai-agentsgoreact

Security analysis

A100/100

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

Scanned May 30, 2026

npx -y skills add ComeOnOliver/skillshub --skill content-pillars --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Content Pillars?

Add the live security badge to your README. It updates with every re-scan.

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

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

Download with Pro
SKILL.md
---
name: content-pillars
description: Define reusable social media content pillars for a product, founder, brand, or campaign. Use when a content calendar needs durable themes, repeatable post types, and clearer editorial direction.
tags:
  - social-media
  - content-strategy
  - positioning
  - agentreacher-compatible
---

# Content Pillars

Create the repeatable themes that make a social calendar coherent over time. Pillars should guide what to post, what not to post, and how each idea earns attention.

## Inputs

- product, brand, or founder
- audience
- goal
- category or market
- proof points
- preferred channels
- topics to avoid

## Workflow

1. Extract the audience tensions:
   pains, ambitions, objections, status anxieties, and buying triggers.

2. Define 4-7 pillars:
   each pillar needs a name, purpose, audience question, post formats, proof source, and example angles.

3. Balance the mix:
   include education, belief, proof, product, objection, and community where relevant.

4. Add boundaries:
   say what does not belong in each pillar so the calendar does not drift.

5. Recommend a pillar ratio:
   percentage or weekly count by pillar for the next campaign period.

## Taste Rules

- Pillars are not vague categories like "thought leadership".
- Each pillar should generate at least 10 real post ideas.
- Product pillars need proof or workflow detail, not feature lists.
- Founder pillars need specific experience, not generic lessons.
- Leave room for timely posts without making the calendar reactive.

## Output Format

```md
## Pillar System
| Pillar | Purpose | Audience Question | Formats | Proof Source | Ratio |
| --- | --- | --- | --- | --- | --- |

## Example Angles
### [Pillar]
- [post angle]

## Boundaries
- [what to avoid]
```

## AgentReacher Notes

Use this before building an AgentReacher calendar so scheduled posts are organized by durable campaign themes instead of isolated ideas.

Example usage in AgentReacher: "Create content pillars for AgentReacher targeting AI founders and solo SaaS builders."

Files in this skill

  • SKILL.md2 KB
  • agents/openai.yaml242 B

Attribution

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

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.