vcxcvii
UserOpen-source SEO and AEO agent. Ranks every finding by distance to revenue, checks the live SERP before briefing anything, and records whether the fix worked.
Categories
Indexed Skills (27)
beat-my-competitors
Tear down named competitors on the same tiering rules used for this site, so the comparison is like for like, then produce a joint content-gap table ranked by the tier weight of what is missing. Use this skill whenever the user asks to: - Run a competitor analysis or content gap analysis - Understand how their site compares to a named competitor - Find what a competitor covers that they do not - Tear down a specific competitor's site or positioning Trigger even for casual requests like "how do we compare to ironclad", "what is our competitor doing that we're not", "content gap analysis", "teardown lexion.com", or when a user names a rival and asks how they stack up.
brief-my-writer
Turn one blueprint node into a complete content brief: the revenue argument, the buyer's own words that must appear, the proof to cite, the internal links, the schema, and what the piece will not say. Refuses to brief a node whose SERP has never been checked. Use this skill whenever the user asks to: - Write a content brief for a page or topic - Spec out an article before writing it - Turn a keyword or cluster into something a writer can execute against Trigger even for casual requests like "write a brief for this", "brief for <topic>", "spec this article", "what should this page cover".
can-i-actually-rank
Check whether a candidate keyword is actually winnable by reading the live SERP, then apply five commercial filters. Ends every candidate in QUALIFY, CONDITIONAL or KILL, kills freely, and never treats vendor authority scores as evidence. Use this skill whenever the user asks to: - Check whether they can rank for a keyword before building content - Qualify or kill a list of keyword candidates - Understand what format Google actually rewards for a query - Decide whether a topic is worth the effort Trigger even for casual requests like "can we rank for this", "check the SERPs for these keywords", "is this winnable", "should we bother with this keyword", "qualify this list".
check-before-i-publish
Run the 10 blocking preflight gates before a page ships, and the 8 postflight gates on their own verification windows after. Never overrides a failing gate; a fail always names the specific fix. Use this skill whenever the user asks to: - Check if a page is ready to publish - Run a preflight or postflight check - Confirm whether something shipped actually worked Trigger even for casual requests like "ready to publish?", "check before I ship this", "preflight this page", "did it work", "postflight check".
explain-this-number
Explain what a search, analytics or AI-visibility metric actually means, how it is commonly misread, and what to say instead. Reference only: it decides nothing and writes nothing, and every other Rainmaker skill cites it rather than restating a definition. Use this skill whenever the user asks to: - Understand what a metric means: sessions, impressions, average position, INP, key events - Work out why two tools disagree, most often GA4 against Search Console - Check whether a number in a report is being read correctly - Sanity-check a claim someone made using a metric - Understand an AI-search term: citation, extractability, entity, llms.txt Trigger even for casual requests like "what does average position actually mean", "why doesn't GA4 match Search Console", "is domain authority real", "what's INP", "our CTR dropped, is that bad", or when a user pastes a number from a dashboard and asks whether it is good.
find-my-quick-wins
Find the rankings closest to paying off: striking-distance queries, pages competing with each other, and impressions that are not converting into clicks. Reads Search Console snapshots the core already pulled. Use this skill whenever the user asks to: - See how their rankings are doing, or what is close to page one - Find quick wins or low-hanging fruit in search - Check whether two pages are competing for the same query - Understand why impressions are up but clicks are not - Review which queries are slipping Trigger even for casual requests like "what's close to ranking", "any quick wins", "are we cannibalising ourselves", "our traffic dropped, what happened", or when a user pastes a query and asks how they rank for it.
follow-the-money
Show where effort has actually gone versus where money is actually made, by comparing the share of pages, sessions and key events per tier, and assign every cluster the tier its content should occupy. Use this skill whenever the user asks to: - Understand what actually makes money on their site - Find out which pages matter versus which just exist - Rebalance where content effort goes - Check whether their declared conversion pages actually convert Trigger even for casual requests like "what actually makes money here", "where should we focus", "we have 400 blog posts, are they doing anything", "is our pricing page actually converting".
get-cited-elsewhere
Drill from cited domains to the specific URLs driving citations to the actual quoted answer text, then turn every finding into an action with an honest plausibility by how editable the placement actually is. Use this skill whenever the user asks to: - Find where they should get mentioned or cited - Build a citation or link-building strategy - Understand who AI engines trust in their category - Get listed on review sites or directories Trigger even for casual requests like "where should we get mentioned", "citation strategy", "who do AI engines trust in our space", "link building", "get us listed somewhere".
get-mentioned-by-ai
Check whether AI assistants mention this site when answering the questions its buyers actually ask, decomposed per engine and per market rather than reported as one aggregate, and mine the cited sources into a target list. Use this skill whenever the user asks to: - Check if they show up in ChatGPT, Perplexity or other AI answers - Understand their AEO or AI-search visibility - Find out why a competitor wins the AI comparison answers - Set up llms.txt or improve AI readability - Audit schema markup for AI extraction Trigger even for casual requests like "am I showing up in ChatGPT", "do LLMs cite me", "AEO check", "GEO audit", "should I add llms.txt", or when a user asks why an AI answer named a competitor instead of them.
know-my-buyer
Interview the site owner about who buys, in their own words, grounded in a real diagnosis rather than generic questions, and write the shared business context every other skill reads. Refuses to run without a diagnosis. Use this skill whenever the user asks to: - Get grilled or interviewed about their business - Figure out who they are actually for, or sharpen their positioning - Set up Rainmaker's business context for the first time - Explain their ICP, personas or buyer language Trigger even for casual requests like "grill me", "who are we actually for", "I don't know what to write about", "set up my business context", "our positioning is vague, help", or on first run after `rainmaker audit`.
make-it-sound-human
Cut a draft before adding to it, kill banned phrasing, replace abstraction with the specific numbers already in the data, and name the weakest paragraphs rather than silently rewriting everything. Use this skill whenever the user asks to: - Punch up, edit, or improve a draft - Make writing sound less generic or less like AI wrote it - Tighten a piece that reads flat Trigger even for casual requests like "punch this up", "make this better", "edit my draft", "this reads flat", "does this sound like a person wrote it".
make-me-quotable
Generate llms.txt and JSON-LD schema from real, sourced facts only, output as a diff against what already exists, and flag schema types competitors use in cited pages that this site is missing. Use this skill whenever the user asks to: - Set up llms.txt - Add or audit structured data / schema markup - Make their site more readable to AI assistants - Improve extractability for answer engines Trigger even for casual requests like "add llms.txt", "make my site AI readable", "add schema markup", "get quoted by AI more".
map-my-site
Turn the keyword plan into the whole intended site as a tree: one intent per URL, a parent for every node, titles and metas generated as a consistent set, permutations gated against doorway-page risk, and a publish rate bounded by what the site has demonstrated it can get indexed. Use this skill whenever the user asks to: - Plan their site structure or URL architecture - Decide how to organise services, locations, or product pages - Check whether their site is scaling permutations safely - Understand how many pages they can realistically publish per month Trigger even for casual requests like "site structure", "how should we organise the site", "map my site", "should each city get its own page", "how many pages can we publish a month".
pick-my-battles
Turn account intelligence into content clusters across seven signal types, not just pain points, with a balance check and a completeness gate that refuses a fourth simultaneous cluster while any existing one is under 40 percent covered. Use this skill whenever the user asks to: - Build a content strategy or topic map - Decide what to write about next - Find content gaps against a competitor - Understand which topic clusters they should own Trigger even for casual requests like "what should we write about", "content strategy", "topic clusters", "what should we own in search".
put-it-on-autopilot
Generate GitHub Actions workflows for the recommended cadence, calling `rainmaker routine` and `rainmaker report`, and print the exact secrets the user needs to set before the workflow can run. Use this skill whenever the user asks to: - Set up automation, cron, or scheduled runs - Run Rainmaker weekly or monthly on autopilot - Configure GitHub Actions for their SEO work Trigger even for casual requests like "set up automation", "run this weekly", "put this on a cron job", "autopilot my SEO checks".
revive-old-pages
Classify every URL with search history into refresh, rewrite, consolidate or kill, excluding anything still inside its own shipped verification window so a fix is never judged before it has had time to work. Use this skill whenever the user asks to: - Find content decay, or which pages are dying - Decide whether to refresh, rewrite or delete old content - Clean up an old blog or content library Trigger even for casual requests like "what should I update", "content decay check", "which posts are dying", "should we refresh or rewrite this", "clean up our old blog posts".
say-it-their-way
Diff the site's messaging against the vocabulary buyers actually use in search and in their own words, then rewrite the one-liner and differentiators using only vocabulary that is actually attested. Use this skill whenever the user asks to: - Sharpen their messaging or positioning - Rewrite their one-liner or homepage headline - Check whether their copy sounds like their buyers or like their category - Update pain points after new interviews or search data Trigger even for casual requests like "our copy feels generic", "sharpen our messaging", "rewrite our one-liner", "does this sound like a buyer wrote it or like a vendor did".
show-me-progress
Render the mandatory five-section report for a chosen window, refusing any window longer than available snapshot history rather than extrapolating a partial period into a full one. Use this skill whenever the user asks to: - Get a monthly report, weekly pulse, or quarterly review - Show progress to a client or their team - See what changed in a given period Trigger even for casual requests like "monthly report", "how did we do this month", "progress report", "show the client", "weekly pulse".
show-up-in-communities
Find where the buyer's question is already being asked in communities, draft an answer that would stand on its own with the product name removed, and track it honestly given that most community platforms offer no native click-level attribution. Use this skill whenever the user asks to: - Find where their audience is talking, like Reddit or forums - Draft a community answer or comment - Decide whether to post in a specific subreddit or forum - Track whether community activity is producing anything Trigger even for casual requests like "should we post on Reddit", "where is our audience talking", "draft a forum answer", "is our Reddit activity working".
spread-one-piece-everywhere
Repurpose a proven page into two derivative formats, bounded so it never becomes a content treadmill: only pages that are live, indexed, past their verification window, and inside a cluster above 40 percent completeness. Use this skill whenever the user asks to: - Repurpose a post into video, social, or a newsletter - Get more distribution out of an existing page - Turn one piece of content into several formats Trigger even for casual requests like "repurpose this", "turn this into a video", "get more mileage out of this post", "distribute this piece further".
stop-losing-visitors
Find where arriving traffic leaks before it converts, using behavioural data the core already pulled, and rank the leaks by how close the page sits to revenue rather than by how dramatic the metric looks. Use this skill whenever the user asks to: - Understand why visitors leave, bounce or drop off - Investigate rage clicks, dead clicks or scroll depth - Find conversion leaks on pages that already get traffic - Work out whether a page has a traffic problem or a page problem Trigger even for casual requests like "why do people leave my pricing page", "we get traffic but no demos", "is my page broken for real users", or when a user shares a page and asks why it is not converting.
unblock-my-money-pages
Find what is technically stopping the pages closest to revenue from working, ordered by distance to money rather than by severity. Reads the diagnosis the core already wrote; it never re-crawls. Use this skill whenever the user asks to: - Audit their site, or find what is broken - Work out why a page is not indexed or not showing in search - Check canonicals, redirects, orphan pages or crawl problems - Review technical SEO before or after a release - Understand which technical issues are actually worth fixing Trigger even for casual requests like "what's broken on my site", "why isn't my pricing page showing up", "is anything blocking Google", "run a technical audit", or when a user pastes a URL and asks why it is not ranking.
what-actually-worked
Answer three questions in order: what did we believe, what did we do, what actually happened: and always include a mandatory "What did nothing" section, since a retrospective containing only wins is a defect. Use this skill whenever the user asks to: - Run a retrospective on their SEO or content work - Understand what is actually working versus what isn't - Find out if a past fix paid off - Update strategy based on what happened Trigger even for casual requests like "what's working", "did the work pay off", "retrospective", "where do we stand", "what should we stop doing".
what-changed-in-search
Check what changed in search or answer engines recently, always fetched live and never answered from training data, then show what it means for this specific site in measured counts with a control check before blaming anything on it. Use this skill whenever the user asks to: - Understand a recent Google core update or algorithm change - Explain a traffic drop or spike - Check whether something the site shipped or an external update caused a metric to move Trigger even for casual requests like "what changed in search", "was there a core update", "did Google change something", "why did our traffic drop", "is this the algorithm or something we did".
what-to-target-next
Turn qualified clusters into a specific keyword plan, slotted as new, refresh, consolidate or kill, capped at the site's own authority budget. Use this skill whenever the user asks to: - Build a keyword plan or content calendar - Decide which specific queries to target next - Understand whether a page needs a refresh or a rewrite Trigger even for casual requests like "keyword plan", "what should I target next", "which queries should we go after", "plan next month's content".
write-the-page
Write a draft from a brief, matching the site's real voice samples rather than a description of the voice, covering every standalone claim, and passing the slop check on itself before returning. Use this skill whenever the user asks to: - Write a draft, an article, or a page from a brief - Turn a brief into actual copy Trigger even for casual requests like "write the draft", "write this article", "draft <slug>", "turn this brief into a page".
rainmaker
Start or resume Rainmaker as a host-native, interactive SEO and AEO workflow. Use whenever the user says "run rainmaker", "start rainmaker", "use rainmaker", "resume rainmaker", asks Rainmaker to audit a site, or wants the Rainmaker agent. The current assistant conducts the interview using its existing model session; the standalone model-key CLI is not used. Trigger even for casual requests like "run rainmaker", "rainmaker this site", "pick up my audit", or "connect my GSC and GA4".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.