keywords
Skill0 starsChanged 33 days agoMITView on GitHub
Research and prioritize SEO keywords, search intent, topic clusters, competitor keyword gaps and keyword-to-page mappings. Use when asked what to rank for, keyword opportunities, long-tail keywords, a content calendar, or a keyword plan. Uses owned Apify keyword/SERP Actors with approved budgets, or supplied exports offline. Does not invent volume or organic difficulty.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vishal1610kamal/second-braintheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 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.
In this repository6 other files it gives its agents.
- content-briefSkill
- content-refreshSkill
- link-buildingSkill
- rank-trackingSkill
- site-auditSkill
- vibesearchSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 8
Read shared rules. Use CLI guidance and Actor contracts for live work.
- Distinctive: line 18
If the user has an authorized Search Console export, use its clicks, impressions and query/page positions as first-party observations over …
≈ “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
Keyword research and content plan
Read shared rules. Use CLI guidance and Actor contracts for live work.
- Reuse the site's product, audience, goal and market. Get seeds from the actual product, customer questions and approved competitor pages. A list of 3–5 meaningful seeds is usually enough to start. Use the provided data immediately when live collection isn't authorized.
- Plan bounded expansion with
dataforseo-keyword-research(mode: keyword_ideas). Usekeyword-search-volume-apionly when metrics enrichment adds value; itsfree_tiermode name does not mean the Apify run has no charge. Check provider requirements and pricing. Useseo-domain-keyword-scraper(ranked_keywords) for a specified competitor, andscrape-google-serpfor a small shortlist's intent. Prepare inputs from the exact templates in inputs. - Normalize keywords without collapsing different languages or meanings. Deduplicate within the same market/source window. Preserve supplied numbers, nulls and row references. Separate brand and non-brand terms. A missing value is Unknown, not zero.
- Classify informational, navigational, commercial and transactional intent as editorial inference backed by query/SERP evidence. Retain forums, videos, directories and shopping results when they explain real search intent; do not remove them to make a term look easy.
- Cluster by shared user need and actual result overlap where observed. Map each cluster to an existing verified URL or a proposed new page. Flag possible cannibalization for review; intent similarity alone isn't proof. Don't assign ten pages the same primary intent.
- Prioritize High/Medium/Low by business relevance, intent, available demand evidence, current foothold, realistic ability to contribute and effort. Explain the reasons. Don't manufacture organic difficulty from advertising competition or a universal “opportunity score.” Keep keywords with missing demand in a validation queue if demand is decision-critical.
- Deliver the columns in report template: keyword/cluster, intent, demand metric and source/date, organic difficulty if actually supplied, current page/new page, business fit, priority, original contribution, next check. Include 3–5 first actions and a short content calendar; treat dates as proposed editorial slots.
If the user has an authorized Search Console export, use its clicks, impressions and query/page positions as first-party observations over the stated window. They are not keyword monthly search-volume estimates. VibeSearch has no bundled Search Console integration.
Done when a writer/owner can identify what to target, which page owns each intent, why it matters, and what evidence is still missing. Hand a chosen cluster to content-brief.
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.

