keywords
Skill9 starsChanged 6 days agoMITView on GitHub
Pull keyword data for a seed topic and turn it into a publishing queue. Use when I type /keywords.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
- vishal1610kamal/second-braintheir own version, first seen Nov 8, 2026
- khadinakbarlabs/vibeseo-plugintheir own version, first seen Oct 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
- vincentventalon/claude-code-video-editing-skill★ 6same name
- vincentventalon/my-claude-skills★ 6same name
- khadinakbarlabs/vibeseo-plugin★ 0same name
- vishal1610kamal/second-brain★ 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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Run node scripts/dfs.mjs keywords "$ARGUMENTS".
“Common” is measured: kept by at least 6 in 10 of the 4 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
Seed topic: $ARGUMENTS
- Run
node scripts/dfs.mjs keywords "$ARGUMENTS". It saves a CSV indata/. Read that CSV. - Clean it up. The raw list is full of junk:
- Word salad variants like "coffee grinder coffee grinder" or "grinder and coffee": drop them.
- Close variants of the same search (same meaning, same results) are ONE topic. Keep the clearest phrasing as the main keyword. Don't add their volumes together: close variants usually share one volume number, so adding them invents searches. Use the highest single volume.
- Drop anything that doesn't fit
site/site.md, and brand/product searches we can't serve.
- One topic = one article. Check
data/queue.csvand skip topics that are already there. - Pick the best 15 for my site. Use the site strength in
site/site.md: a new site should go after low KD informational and comparison topics first. Volume matters less than "can we actually rank and does it lead to money". - Append them to
data/queue.csv(create it if missing) with columns:keyword,volume,kd,intent,variants,status,notesandstatus=queued. - Show me the 15 as a short table, then tell me the 3 you'd write first and why, one line each.
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.

