Content Pillars logo

Content Pillars

Organization
social-media-skills
content-pillars

Use 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.

Overview

Publishersocial-media-skills
Repositoryskills
Skill namecontent-pillars
Stars
215
Forks
44
Bundled files
5
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by social-media-skills on GitHub. Read the source before you install it.

Installation

Install the Content Pillars AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/social-media-skills/skills/tree/main/skills/content-pillars
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/social-media-skills/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/content-pillars .claude/skills/content-pillars
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Content Pillars in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Content Pillars on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Content Pillars is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Content Pillars

Content 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.

When to use this

  • After brand-profile, before planning content at any scale.
  • When the user doesn't know "what to post about," or their feed feels random.
  • When 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.

Step 0 — Read the foundation first

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.

Step 1 — Mine the brand profile for raw material

Pull the candidate sources (see references/deriving-pillars.md):

  • Positioning + point of view → the signature pillar (the thing the brand wants to be known for; the hill it will die on).
  • Audience jobs-to-be-done / pains → audience-relevant pillars (their problems, not your features).
  • Proof + expertise → credibility pillars (what the brand can authoritatively teach).
  • The human / brand story → a connection pillar.
  • Offers / product → at most one conversion-linked pillar, used sparingly.

Step 2 — Generate candidate pillars

From each source, draft candidate themes. Aim wide first (8–12 candidates), phrased as subjects, not formats — "small-business money mistakes," not "educational posts."

Step 3 — Test and select 3–5

Run each candidate through the pillar test (references/what-makes-a-pillar.md):

  1. Ownable — can you say why this brand specifically is credible or distinctive here?
  2. Relevant — does the target audience genuinely care?
  3. Strategic — does it advance a real goal (awareness, trust, conversion)?
  4. Sustainable — can you brainstorm 10+ post ideas from it right now?

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.

Step 4 — Define each pillar

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.

Step 5 — Balance the mix

A healthy pillar set has:

  • One signature pillar — the differentiator, the brand's distinct POV. Every brand needs one.
  • Supporting pillars — audience problems, credibility, connection.
  • At most one conversion-linked pillar, used as the minority (promotion rides on the value the others create — see the mix logic in batch-content-plan).

Spread the pillars across goals so the brand isn't all-teaching or all-selling.

Step 6 — Write the artifact

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.

Quality bar — self-check

  • Are the pillars themes, not intents or formats? (No "educational" as a pillar.)
  • Is each one ownable — with a reason this brand is credible/distinctive on it?
  • Is each audience-relevant, not just brand-interesting?
  • Could each generate 10+ post ideas (sustainable)?
  • Is there exactly one signature pillar, and is promotion a minority?
  • Are there 3–5, not eight vague ones?
  • Does each pillar trace back to something real in the brand profile?

Edge cases

  • User lists generic buckets ("educational, BTS, promo") → explain those are intents/formats, and convert them into real themes derived from the brand.
  • Too many candidate topics → narrow to the 3–5 that best pass the pillar test.
  • Brand with no obvious distinctive theme → mine the POV and audience pains harder; if there's truly no differentiation, the signature pillar becomes voice + a consistent angle, and you say so honestly.
  • Personal brand / creator → pillars are person-led (what they're known for, their journey, their craft); keep them tied to the person, not a faceless topic list.
  • Multiple audiences (e.g., nonprofit: beneficiaries + donors) → some pillars may serve different audiences; note which.
  • Multi-product / broad business → resist one pillar per product; pillars are audience themes, not a catalog.

Related skills

  • 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.
  • The content skills (caption-writer, reels-script, …) — each post is tagged to a pillar.

References

  • 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Content Pillars AI skill do?

Use 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-pil...

Why use Content Pillars on TypingMind?

Because you install it once and use it with any model. Content Pillars is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Content Pillars in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/social-media-skills/skills/tree/main/skills/content-pillars. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Content Pillars?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Content Pillars?

As many as you like. As long as a model supports skills, you can use Content Pillars with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Content Pillars AI skill free?

Yes. It is published on GitHub by social-media-skills under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇