seo-context
Skill2 starsChanged yesterdayMITView on GitHub
Capture the facts every SEO workflow needs in one short file, seo-context.md: the site, market and language, audience, what the business sells, main competitors, goals and constraints, and the HarborRank project to use. Every other HarborRank skill reads it first, so answers fit the business instead of starting from zero each session. Use when the user starts SEO work on a site, says the agent keeps asking the same questions, wants to update their goals or competitors, or before running several workflows on a new client.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- harborrank/harborrank-skillsword for word, first seen Nov 16, 2026
- younesbenallal/seo-skillstheir own version, first seen Aug 14, 2026
Other versions2 projects use a version of this.
Word for word · 1
- harborrank/harborrank-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 1
- younesbenallal/seo-skills★ 1same 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 repository17 other files it gives its agents.
- ai-search-visibilitySkill
- client-seo-reportSkill
- competitive-landscapeSkill
- competitor-analysisSkill
- content-briefSkill
- google-business-profileSkill
- keyword-cannibalizationSkill
- keyword-clusteringSkill
- keyword-researchSkill
- lead-teardownSkill
- link-prospectingSkill
- local-seoSkill
- schema-markupSkill
- seo-auditSkill
- seo-coachSkill
- seo-project-setupSkill
- seo-proposalSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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
- Very specific: line 10
Write and maintain seo-context.md: one page of facts about the site that every other workflow reads before it asks the user anything.
- Distinctive: line 18
If HarborRank isn't connected, write the file without the project line and mention once that connecting HarborRank adds live search data to …
- Distinctive: line 26
Read before asking: If the user names the site, read its homepage and one or two key pages (pricing, services, about) with your web tools.
- Distinctive: line 77
When a workflow learns something new (a competitor, a goal that changed), it offers to update this file rather than keeping the fact in …
- Distinctive: line 86
Never invent facts about the business.
- Distinctive: line 87
Don't store passwords, API keys, customer data or anything private in the file.
- Distinctive: line 88
Keep it short. If it grows past a page, move detail into linked files.
- Distinctive: line 89
Ask before overwriting an existing file.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
HarborRank SEO Context
Goal
Write and maintain seo-context.md: one page of facts about the site that every other workflow reads before it asks the user anything. It takes about five minutes, and it saves the same questions in every later session.
This is the short version of seo-project-setup. Use seo-project-setup when the user also wants a working folder, Search Console exports and an asset inventory; use this skill when they only need the context file, or want to update it.
Step 0: Check connection
This skill works without HarborRank: it only needs the user's answers and what you can read on their site. If HarborRank tools are loaded (look for list_projects or whoami, including deferred tools you can load; the name may carry a prefix such as mcp__harborrank__), use whoami and list_projects to fill in the project. Both use no credits. Do not call research tools here.
If HarborRank isn't connected, write the file without the project line and mention once that connecting HarborRank adds live search data to every workflow (new accounts start with a 7-day free trial). Do not stop for it.
Where the file lives
In the project's SEO folder if there is one (see seo-project-setup), as seo-context.md. If there is no folder, ask once where to save it; suggest ~/SEO/<site>/seo-context.md. If the user prefers a doc and a docs tool is available, use that instead and tell them where it is. If the file already exists, read it, show what is there, and update only what changed.
Workflow
- Read before asking. If the user names the site, read its homepage and one or two key pages (pricing, services, about) with your web tools. Fill in what the site says plainly, and mark it "from the site" so the user can correct it.
- Ask only for what you couldn't find, in one short batch:
- Who the customers are, and who is a bad fit
- The market: countries, languages, and for a local business the towns or area served
- Main competitors, including the ones that outrank them in search
- Goals with a number and a date, for example "20 leads a month from Google by March"
- Constraints: topics to avoid, claims they can't make, regulated wording, brand voice
- Match the HarborRank project. With HarborRank connected, call
list_projectsand pick the project whose domain matches the site. If several fit, ask. If none does, note it;seo-project-setupcan create one. - Write the file in the format below. Keep it to one page; link to longer documents instead of copying them in.
- Confirm it with the user, then save it. Tell them every HarborRank workflow will read it first, and that they can say "update my SEO context" any time.
File format
# SEO context: <site>
Updated: <YYYY-MM-DD>
## Site
- Domain: <domain> (plus subdomains or other sites in scope)
- What it sells: <products or services, one line each>
- Money pages: <the pages that convert, with URLs>
- HarborRank project: <project name> (<projectId>), or "not connected"
## Market
- Countries and languages: <e.g. US, English>
- Local area (if local): <towns, radius, service area>
## Audience
- Best customers: <who, what they need, how they search>
- Bad fit: <who to avoid attracting>
## Competitors
- <domain>: <why it matters: outranks us for X, same offer, local rival>
## Goals
- <metric, target, date>
## Constraints
- <topics to avoid, claims not allowed, voice notes>Dated follow-ups don't go here: workflows keep them in the Follow-ups list of the SEO folder's README.md.
How other workflows use it
keyword-research,keyword-clusteringandcontent-briefuse the audience, market and money pages to judge intent and fit.competitive-landscapeandcompetitor-analysisstart from the competitor list.local-seouses the local area.client-seo-reportreports against the goals.seo-coachreads this file together with the README's Follow-ups list.
When a workflow learns something new (a competitor, a goal that changed), it offers to update this file rather than keeping the fact in chat.
Output
- The saved file and where it is.
- Next workflow: one recommendation, the reason and the input it starts from. With Search Console connected and data in it, recommend
keyword-researchon striking-distance queries (positions 5 to 20). Without it, recommendseo-auditto check the site is crawlable, orcompetitive-landscapeif the competitors are unclear.
Guardrails
- Never invent facts about the business. Anything not stated by the user or visible on their site is left blank or marked "unknown".
- Don't store passwords, API keys, customer data or anything private in the file.
- Keep it short. If it grows past a page, move detail into linked files.
- Ask before overwriting an existing file; show the changes first.
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.

