the-council
Skill23 starsChanged 18 days agoMITView on GitHub
Turns a set of hook verdicts (from the viewer panel, the four failures check or user feedback) into the top 3 changes, ranked, with exact before and after words. Use when you have many notes on a hook and need to decide what to change first.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- DantesPeak85/the-counciltheir own version, first seen Oct 4, 2026
- emaddawood1991-tech/claude-ai-skillstheir own version, first seen Aug 23, 2026
- bytesofbree/skills-labtheir own version, first seen Jul 17, 2026
- IvanIvMa/claude-skillstheir own version, first seen Jun 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- bytesofbree/skills-lab★ 6same name
- DantesPeak85/the-council★ 3same name
- IvanIvMa/claude-skills★ 1same name
- emaddawood1991-tech/claude-ai-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- four-failures-checkSkill
- hook-formatsSkill
- hook-masterSkill
- lock-inSkill
- niche-tunerSkill
- viewer-panelSkill
- viral-scoutSkill
- visual-matchSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
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 33
If a change came from a misleading request (a fake stat, a promise the video can't keep), it goes under "Not doing" with the honest swap.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The Council
Notes pile up. The Council decides. It takes the panel's verdicts and the failures found, and returns three changes, ranked, each with the exact before and after.
How to rank
Score each possible change on three things, then rank:
- Who it keeps. How many of the viewers who matter for this video it turns from swipe to stay. The two "who matter most" viewers count double.
- Can the footage pay it off. A change that needs footage or proof the creator doesn't have drops to the bottom or out.
- Cost. Reorder or cut existing footage is cheapest. New text is cheap. A reshoot is dearer. Say which it is.
Fix in this order when it's a tie: delay, then confusion, then irrelevance, then disinterest. A clear, viewer-first opening with weak curiosity still beats a curious one nobody understands.
Output
1. [Change]. Before: "[exact]" After: "[exact]". Keeps: [viewers]. Cost: [cut / reorder / text / reshoot].
2. ...
3. ...
Not doing: [the tempting change that loses, and why, in one line].Rules
- Three changes, not ten. If there is only one real problem, say so and give one.
- Each change is a specific edit, not advice. "Be more engaging" is not a change.
- If a change came from a misleading request (a fake stat, a promise the video can't keep), it goes under "Not doing" with the honest swap.
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.