Install
openclaw skills install @social-media-skills/content-pillarsUse to define a brand's content pillars — the 3–5 recurring themes it posts about — the strategic backbone between the brand profile and the content calendar. Run when the user says "content pillars," "content buckets," "what should I post about," "content themes," "content strategy," "pillars," or before planning a batch or calendar. Reads brand-profile first and derives pillars from positioning, point of view, audience, and proof — real ownable themes, never generic "educational / behind-the-scenes / promotional" buckets (those are intents and formats, not pillars). Produces a content-pillars.md that batch-content-plan and the content skills read. Works for any business: B2B, ecommerce, local, personal brand, nonprofit.
openclaw skills install @social-media-skills/content-pillarsContent pillars are the few recurring themes a brand returns to — the strategic layer
between who the brand is (brand-profile) and what it posts this week (batch-content-plan).
Good pillars make a feed coherent, ownable, and infinitely easy to plan; their absence is why
so many brands post random things that add up to nothing.
The single most important idea in this skill — and the thing almost everyone gets wrong:
A pillar is a theme you own. It is NOT an intent or a format. "Educational," "behind-the-scenes," and "promotional" are not pillars — educational is an intent (the job a post does) and behind-the-scenes is a format/treatment. A real pillar is a subject area like "payroll without a specialist" or "the craft of coffee, demystified." Get this distinction right and everything downstream gets sharper. See
references/what-makes-a-pillar.md.
brand-profile, before planning content at any scale.batch-content-plan needs pillars and none are defined.When NOT to use this: if a current content-pillars.md exists, load it, summarize it, and
move on unless the user wants to revisit it.
Load brand-profile.md (and voice.md). Pillars are derived from strategy — positioning,
point of view, audience, proof, offers — not brainstormed from thin air. If there's no brand
profile, run brand-profile first; pillars built without it are guesses.
Pull the candidate sources (see references/deriving-pillars.md):
From each source, draft candidate themes. Aim wide first (8–12 candidates), phrased as subjects, not formats — "small-business money mistakes," not "educational posts."
Run each candidate through the pillar test (references/what-makes-a-pillar.md):
Keep the 3–5 strongest. A candidate that fails ownable or sustainable is not a pillar. Fewer, sharper pillars beat more, vaguer ones — a feed with eight themes has none.
For every selected pillar, capture: a clear name, what it covers, why the brand owns it, who
it's for, the goal it serves, 5–8 example angles/sub-topics, and the proof/assets it draws on.
This is what makes pillars usable by the planning and content skills. See
references/pillar-template.md.
A healthy pillar set has:
batch-content-plan).Spread the pillars across goals so the brand isn't all-teaching or all-selling.
Produce content-pillars.md using references/pillar-template.md. Summarize it back to the
user, flag the signature pillar, and invite one round of edits. batch-content-plan and the
content skills will read this on every task.
brand-profile — read first; supplies positioning, audience, POV, proof.audience-research — deepen audience pains that feed audience pillars.batch-content-plan — consumes pillars to build the calendar.caption-writer, reels-script, …) — each post is tagged to a pillar.references/what-makes-a-pillar.md — the definition, the pillars-vs-intents-vs-formats
distinction, the pillar test, anti-patterns.references/deriving-pillars.md — the method for mining the brand profile into pillars.references/pillar-template.md — the content-pillars.md output schema.references/examples.md — ownable pillar sets across six business types.