narrow-my-niche
Skill0 starsChanged 43 days agoMITView on GitHub
Get from a subject someone could write about to one they could own, and say out loud what they are giving up to do it. Use when someone says their content feels scattered, cannot describe what they post about, is choosing between two audiences, or asks how to position themselves. Do not pick the niche for them, and do not promise that narrowing will grow an account.
In this repository25 other files it gives its agents.
- am-i-driftingSkill
- audit-before-i-publishSkill
- audit-before-i-tweetSkill
- define-my-content-pillarsSkill
- draft-my-commentsSkill
- extract-the-hookSkill
- find-the-storySkill
- fix-my-endingSkill
- fix-my-last-lineSkill
- fix-my-linkedin-profileSkill
- fix-my-opening-lineSkill
- fix-my-twitter-profileSkill
- get-my-team-postingSkill
- get-seen-in-repliesSkill
- handle-my-repliesSkill
- plan-my-weekSkill
- repurpose-into-a-postSkill
- same-idea-both-platformsSkill
- sound-less-like-aiSkill
- turn-this-into-a-threadSkill
- what-workedSkill
- who-am-i-writing-forSkill
- why-did-that-one-take-offSkill
- why-did-this-post-flopSkill
- write-in-my-voiceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Not from intentions. Take the posts that exist, group them, and read the groups back.
- Distinctive: line 45
If no, it is a topic, not a niche.
- Distinctive: line 48
Ask for five post titles on the spot.
- Distinctive: line 53
Every narrowing loses people.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Narrow my niche
Most niche advice stops at "go narrower", which is not actionable, because it never says narrower along which axis. People then narrow the subject, lose interest in three weeks, and conclude that niching does not work for them.
This skill does two things the advice usually skips: it narrows along the axis that suits the person, and it names the cost before they commit.
Step 1: start from what they have already published
Not from intentions. Take the posts that exist, group them, and read the groups back. Almost everyone is surprised here, and the surprise is the useful part: people believe they write about the thing they meant to write about.
Say the split plainly. "Four of these are about hiring and the rest are about pricing" is more useful than any positioning exercise.
Step 2: the three axes
You can narrow by subject, by audience, or by stage. Most people only ever try the first.
- Subject. What it is about.
- Audience. Who it is for.
- Stage. Where in the journey they are.
"Pricing" is broad. "Pricing for agencies" is narrower on audience and the subject has not moved. "Pricing for agencies about to hire their first employee" is narrower on stage, and it is now specific enough that the reader knows in one line whether it is them.
Offer all three and let them see which one they can actually sustain.
Step 3: the fifty-posts test
Can you write fifty posts inside this without repeating yourself, and without research you would come to resent?
If no, it is a topic, not a niche. A topic is something you write about. A niche is somewhere you live.
Ask for five post titles on the spot. If the fifth is a struggle, the fiftieth does not exist.
Step 4: name the cost out loud
Every narrowing loses people. Say exactly who.
This is the step that decides whether the choice survives. A niche picked without naming what it gives up gets abandoned within weeks, because the first time a post outside it does well, it looks like evidence the niche was wrong. It is not evidence. It was always going to happen, and knowing that in advance is the difference between a position and a phase.
Step 5: leave a door
Roughly one post in five outside the niche, chosen deliberately rather than whenever the writer gets bored. It keeps the account readable as a person and it gives the restlessness somewhere legitimate to go.
What this will not do
It will not pick for them. The axis that works is the one they can sustain for a year, and nobody can tell from the outside which that is.
It will not promise growth. A narrower account is easier to describe and easier to recommend, and that is the honest claim. Whether it grows depends on whether the niche has anyone in it, which is a market question and not a writing one.
What changes when VoiceMoat is connected
Step 1 is only as good as the evidence, and most people are working from memory:
get_voice_insightsreturns the subjects and patterns actually present in what you have published, which is the grouping step done from data.get_analyticsandlist_postsgive impressions next to reactions for each post, so which of those groups your audience responded to can be read in rate rather than raw count, and a niche is not chosen on volume alone.get_post_ideasruns the fifty-posts test properly by generating inside the candidate niche, so you find out now whether it has depth.
VoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

