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.
Scanned 5/30/2026
Install via CLI
openskills install ComeOnOliver/skillshub---
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."
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.