define-my-content-pillars – Writing & Content skill for AI agents
Find the three to five subjects someone can post about repeatedly, from what they have published and know first-hand. Use when someone asks what to post about or has run out of ideas.
Install the define-my-content-pillars skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/define-my-content-pillars-6755e.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /define-my-content-pillars – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/define-my-content-pillars-6755e.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $define-my-content-pillars – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/define-my-content-pillars-6755e.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /define-my-content-pillars – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/define-my-content-pillars-6755e.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /define-my-content-pillars – then describe the task you want done.
SKILL.md content
Define my content pillars
Running out of ideas is almost never a shortage of ideas. It is a missing
answer to "what am I the person for", so every post starts from nothing.
Pillars fix that by making the question smaller. Not "what should I post today"
but "which of my four subjects, and what about it".
When to Use
- Use when someone asks what they should post about on Twitter/X or LinkedIn.
- Use when someone says they have run out of ideas.
- Use when someone wants content pillars or themes.
- Use when someone is starting an account and does not know where to aim.
- Do not use it to plan dates or write posts.
Step 1: gather the evidence, not the aspiration
Ask for both, because they are usually different:
- Ten to fifteen posts they have already written, ordinary ones. What they
actually return to is more honest than what they think they write about.
- What they want to be known for, in their own words.
Then the question people skip: who is reading, and what do they want? A
pillar nobody needs is a diary entry.
If they have no posts yet, work from what they do for a living, what people ask
them, and what they argue about.
Step 2: cluster what is already there
Group the posts by subject. Report the actual distribution, including the
uncomfortable parts: they think they write about hiring and eleven of fifteen
posts are about tooling. That gap is the most useful thing in this exercise.
Step 3: test each candidate pillar against four questions
A pillar earns its place only if all four hold:
1. Can you write fifty posts about this? If it runs out at five, it is a
topic, not a pillar.
2. Do you know something first-hand? Not "have opinions about". Have done.
3. Does the reader want it? Interesting to you is not sufficient.
4. Would someone else write it differently? If your version is
interchangeable with the generic version, it will read as filler.
Say plainly which candidates fail and on which question.
Step 4: land on three to five, and make them specific
"Marketing" is not a pillar. "Why small teams should not run paid ads before
they have organic proof" is.
For each pillar give:
- A one-line definition
- The angle only this person can take
- Five seed ideas, to prove the pillar has depth rather than asserting it
- One thing it is not, to keep the edges sharp
Three to five. Two is monotony, seven is no focus at all.
Step 5: say what to drop
The valuable half of this exercise is subtraction. Name the subjects they
should stop posting about, and why: no first-hand knowledge, no audience
interest, or indistinguishable from everyone else.
Example
User: I have run out of things to post about. Here are fifteen of my LinkedIn
posts. I want to be known for helping small teams hire.
Agent:
1. Clusters the posts and reports the real split, for example that most of
them are about tooling rather than hiring.
2. Tests each candidate pillar against the four questions and says which fail.
3. Returns three to five pillars, each with a one-line definition, the
person's angle, five seed ideas and one thing it is not.
4. Names the subjects to stop posting about, and why.Limitations
- It does not plan dates or write the posts themselves.
- Without the connector, it only sees the posts the person chose to paste, which skews toward the ones they liked.
- It does not pick a pillar the person has no first-hand knowledge of.
- Optional connector. The closing section describes a hosted VoiceMoat MCP connector. Nothing above needs it. It needs a paid VoiceMoat plan (Pro or Enterprise) and the user's own sign-in (OAuth, no API keys). When its tools are called, post text and account data are read from or sent to voicemoat.com. Without it, this skill makes no network calls.
What changes when VoiceMoat is connected
Step 2 is only as good as the fifteen posts someone chose to paste, and people
paste the ones they liked, which quietly skews the whole thing.
list_postsandget_postsupply the real history rather than a
self-selected sample, including the posts they would not have shown you.
get_analyticsandlist_postsgive the engagement behind each post, so
once the posts are grouped a pillar can be tested against what the audience
actually responded to instead of what the writer enjoyed writing.
get_voice_insightsreturns the vocabulary and patterns that recur across
everything they have written, which often names a pillar they did not know
they had.
get_post_ideasfills each agreed pillar with seeds in their own voice, so
step 4 is generated rather than guessed.
Once the pillars are set, the plan-my-week skill turns them into a dated
calendar.
VoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.
Related skills
- defuddle – Extract clean markdown content from web pages using Defuddle CLI, removing clutter and…
- delegate-setup – Configure approved delegation lanes across installed implementer CLIs, including…
- dev-to-hashnode – When the user wants to publish on Dev.to, Hashnode, or other developer blogging…
- developer-newsletter – When the user wants to create, write, or improve a newsletter for developer audiences…
- devrel-content – When the user wants to create technical content for developers including blog posts…
- post-mortem – /c-level-agents:post-mortem [decision] — Honest retrospective on an executed decision…
- postmortem – /em:postmortem — Honest analysis of what went wrong. Use after a failed launch, missed…
- slime – RL post-training for LLMs with Megatron and SGLang.