niche-tuner
Skill23 starsChanged 18 days agoMITView on GitHub
Tunes a hook to one niche and one viewer, using the words that audience actually uses, stakes the right size, proof they trust and lines the platform and regulator allow. Use when a hook is clear but sounds generic, or when it is for a regulated or local business.
In this repository8 other files it gives its agents.
- four-failures-checkSkill
- hook-formatsSkill
- hook-masterSkill
- lock-inSkill
- the-councilSkill
- viewer-panelSkill
- viral-scoutSkill
- visual-matchSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 25
If you don't have their words, use the plainest phrase a beginner would type into search, and list "what do your comments say?" under Check …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Niche Tuner
A hook that could fit any niche fits none. Tune it to the exact viewer.
Step 1: Name the viewer in one line
"[Who], who [situation], and wants [result] / fears [problem]." Example: "New runners in Bristol who want to finish a 5k but think their knees can't take it."
Step 2: Steal their words, not your words
Look for the viewer's own phrases in what the creator gave you: comments, DMs, questions they get asked, what people say before they book. Those words go in the hook. Only words that appear in the brief count as theirs. A phrase you think they would use is your guess: you may use it, but never put it in quotes or say commenters say it.
| Creator word | Viewer word |
| "lactate threshold" | "I get out of breath too fast" |
| "fulfilment exceptions" | "my parcel never came" |
| "colour correction" | "will it go orange" |
If you don't have their words, use the plainest phrase a beginner would type into search, and list "what do your comments say?" under Check these.
Step 3: Size the stakes
Stakes are what the viewer loses by not watching. Keep them true and the right size for the niche. A frizzy fringe, a missed parcel, a nervous first lesson. Don't inflate a small fix into a life change.
Step 4: Use proof this niche trusts
| Niche | Proof that lands | Avoid |
| Local service | What happens on the day, the price on the day, real time taken, the room, the kit | "Best in town", reviews you can't show |
| Health and clinics | What the appointment involves, what it doesn't involve | Outcome promises, "painless", "doesn't hurt", "comfortable", claims about other professionals |
| Money, software, B2B | The creator's own numbers, labelled, and a screen showing it work | Income claims, "passive", fake screenshots |
| Food, craft, hobby | The before and after on screen, the one variable changed | "Best ever", "foolproof" |
| Fitness | The plan and the effort, not the body result in a time frame | "Lose X in Y days" |
Step 5: Check the rules of the niche
- Health and clinics: no promise of results, nothing about pain or comfort ("painless", "doesn't hurt"), no claim that other professionals hide things. Their regulator and advertising rules apply; name that under Check these.
- Money and income: results are past results of specific people, never a promise.
- Ads: the platform's own ad policy applies on top.
Output
Viewer: [one line]
Their words: [2 to 4 phrases quoted from the brief, with where they came from, or "none given"]
Stakes: [one line]
Proof to show: [what's in the footage]
Tuned hook: "[exact words]"
Niche rule to check: [if any]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.