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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
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.
## Pillar System
| Pillar | Purpose | Audience Question | Formats | Proof Source | Ratio |
| --- | --- | --- | --- | --- | --- |
## Example Angles
### [Pillar]
- [post angle]
## Boundaries
- [what to avoid]
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."
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
The English summary is being prepared. Showing the original description.
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
The English summary is being prepared. Showing the original description.
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
The English summary is being prepared. Showing the original description.
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
The English summary is being prepared. Showing the original description.
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
The English summary is being prepared. Showing the original description.