Content pillars

Skill agentreacher/skills/skills/content-pillars

Reusable agent skills for planning, packaging, and scheduling social media campaigns.

Install

npx -y skills add agentreacher/skills --skill content-pillars

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.0 KB, 382 tokens by cl100k_base, as published. Nobody here has run it

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

Extract the audience tensions: pains, ambitions, objections, status anxieties, and buying triggers.
Define 4-7 pillars: each pillar needs a name, purpose, audience question, post formats, proof source, and example angles.
Balance the mix: include education, belief, proof, product, objection, and community where relevant.
Add boundaries: say what does not belong in each pillar so the calendar does not drift.
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

## 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."

What ships with it: 1 file

242 B alongside SKILL.md

agents/

openai.yaml242 B

Gives 0 of the 12 instructions most marketing audience skills give in 382 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

Apply Poppins font to headingsin 41 of 690, across 6 files
Apply Lora font to body textin 41 of 690, across 6 files
Use Arial fallback for headingsin 39 of 690, across 4 files
Use Georgia fallback for body textin 39 of 690, across 4 files
Maintain text hierarchy and formattingin 39 of 690, across 4 files
Use accent colors for non-text shapesin 38 of 690, across 3 files
Use RGB values for precise color matchingin 38 of 690, across 3 files
Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
Use active voice instead of passive voicein 26 of 690, across 10 files
Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
Prioritize clarity over clevernessin 22 of 690, across 8 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.