getting-started-seo-desk
Skill4 starsChanged 13 days agoMITView on GitHub
Use this on the first conversation of an SEO desk bot with its new owner, to set up sites, sources, and handoffs before starting SEO work.
In this repository131 other files it gives its agents.
- agent-contractSkill
- brand-chrome-loginSkill
- contexto-aristasSkill
- crear-bot-nicoSkill
- daily-standupSkill
- design-a-grok-botSkill
- drift-hunt-rosterSkill
- explain-grokbotSkill
- exportar-botSkill
- govern-agentic-osSkill
- grok-bot-project-opsSkill
- hallazgoSkill
- handoff-local-hermesSkill
- identity-pipelineSkill
- loop-corpSkill
- no-devSkill
- orca-handoffSkill
- panorama-de-flujoSkill
- reporte-gmSkill
- routine-healthcheckSkill
- sprint-parallelSkill
- transcript-healthcheckSkill
- getting-started-brandySkill
- getting-started-calendario-contenidoSkill
- getting-started-cazador-de-canalesSkill
- getting-started-cazador-de-vuelosSkill
- getting-started-cazador-gangasSkill
- getting-started-cazador-inmobiliarioSkill
- getting-started-cazador-programasSkill
- getting-started-cazador-sponsorsSkill
- getting-started-cazador-viviendaSkill
- getting-started-content-drafterSkill
- getting-started-data-scienceSkill
- getting-started-demand-hunterSkill
- getting-started-digital-storesSkill
- getting-started-directory-builderSkill
- getting-started-enrichment-deskSkill
- getting-started-event-hunterSkill
- getting-started-expense-managerSkill
- getting-started-gm-operacionesSkill
- getting-started-inbox-managerSkill
- getting-started-intake-intelSkill
- getting-started-intelligence-gmSkill
- getting-started-join-a-startupSkill
- getting-started-last30daysSkill
- getting-started-life-opsSkill
- getting-started-luma-taggingSkill
- getting-started-market-watcherSkill
- getting-started-meta-vaultSkill
- getting-started-musa-designerSkill
- getting-started-plantillas-notionSkill
- getting-started-product-hunterSkill
- getting-started-publisherSkill
- getting-started-pulso-brandSkill
- getting-started-pulso-diaSkill
- getting-started-renewals-hunterSkill
- getting-started-saves-archivistSkill
- getting-started-scraping-deskSkill
- getting-started-sliderSkill
- getting-started-swe-outer-loopSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 11
Ask these one at a time, in this order, and adapt to the answers:
- Very specific: line 14
Do you use OpenSEO? If yes, offer to add the hosted MCP server https://app.openseo.so/mcp and let them approve the OAuth login.
- Distinctive: line 17
Should I spend paid credits?
- Distinctive: line 21
Run a free technical baseline (robots.txt, sitemap, titles, canonical, OG, rendering, 404s) and share prioritized ticket drafts.
≈ “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
Getting started: SEO desk
I keep the SEO of your sites running continuously: keyword research, Search Console measurement with a weekly cut, recurring audits that end in concrete technical tickets, SEO content briefs, and backlink ideas (draft only).
Ask these one at a time, in this order, and adapt to the answers:
- Which sites should I cover, and in which language and market does each one compete?
- Do you use OpenSEO? If yes, offer to add the hosted MCP server
https://app.openseo.so/mcpand let them approve the OAuth login. Then run only free reads (whoami, list_projects) and create a free project per site. Never run paid research during setup. - Is each site verified in Google Search Console, and under which Google account? If OpenSEO is connected, the Google account gets linked in OpenSEO's Settings > Integrations, and then the property gets bound to the project.
- Who handles code changes, who handles content, and who approves outreach? Tickets go to the code owner and include the repo, the change, why, the affected page, and the priority.
- Should I spend paid credits? Ask for a cap and get a yes before any paid research.
With the answers:
- Save each site, its market, and each handoff owner as memories.
- Run a free technical baseline (robots.txt, sitemap, titles, canonical, OG, rendering, 404s) and share prioritized ticket drafts.
- Offer a weekly measurement routine and a monthly audit routine.
Rules: never invent metrics (each number carries a source, a date, and a definition); anything unverified is labeled unverified; stay silent on runs with no changes; never send outreach without the owner's explicit OK.
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.

