search-console
Skill0 starsChanged 16 days agoNo licenceView on GitHub
Connect a client's Google Search Console and pull real ranking data — clicks, impressions, position, top queries and pages, and honest period-over-period comparisons. Use when setting up SEO reporting for a new client, or whenever someone asks how a site is doing in Google, what it ranks for, whether traffic is up, which pages are getting impressions, or asks to "run the SEO numbers", "check Search Console", "pull GSC", "how are we doing in search", "what are we ranking for", "did the redesign work". Also use when a GSC CSV/ZIP export is handed over, since the same truncation traps apply.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- advisorppc-org/advisorseo-claude-plugintheir own version, first seen Nov 1, 2026
- nowork-studio/notfair-plugintheir own version, first seen Oct 14, 2026
- nowork-studio/topranktheir own version, first seen Oct 8, 2026
- terryds/skillstheir own version, first seen Oct 3, 2026
- OpenClaudia/openclaudia-skillstheir own version, first seen Jun 11, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- nowork-studio/toprank★ 4.1ksame name
- nowork-studio/notfair-plugin★ 4.1ksame name
- OpenClaudia/openclaudia-skills★ 731same name
- terryds/skills★ 1same name
- advisorppc-org/advisorseo-claude-plugin★ 0same name
- oivanfelipe/claude-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 repository22 other files it gives its agents.
- analyticsSkill
- avoid-ai-writingSkill
- core-web-vitalsSkill
- factory-floorSkill
- marketing-ai-seoSkill
- marketing-copy-editingSkill
- owasp-securitySkill
- refactoring-uiSkill
- resend-formsSkill
- s4h-decision-premortem-analysisSkill
- session-hygieneSkill
- site-ingestSkill
- skill-forgeSkill
- skill-scoutSkill
- static-site-forgeSkill
- storybrand-messagingSkill
- top-designSkill
- ux-heuristicsSkill
- video-briefSkill
- watchSkill
- web-accessibilitySkill
- web-typographySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 5 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
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.