seo-guard
Skill1 starsChanged 4 months agoMITView on GitHub
Audit a site for SEO + AI-search visibility and apply only safe, high-quality fixes — keeping llms.txt, meta, hreflang, sitemaps, and structured data consistent. Self-improving: reads run history, logs after. Use when the user says "SEO pass", "check SEO", "don't break SEO", "update llms.txt", or ships site copy/structure changes. Agentic OS (Level 1).
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 17
Never change a live URL/slug without a 301 — broken canonicals tank rankings.
- Very specific: line 18
Keep llms.txt in sync with sitemap + nav after any page add/rename.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
seo-guard
Safe SEO + AI-visibility guardrail. Audits, then fixes only what's low-risk.
Loop (every time)
- Before — read
<vault>/agentic-os/runs/seo-guard.md; applylesson:. Standing lessons:- Never change a live URL/slug without a 301 — broken canonicals tank rankings.
- Keep
llms.txtin sync with sitemap + nav after any page add/rename. - Multilingual: every page needs correct
hreflang+ self-referencing canonical per locale.
Audit checklist (report first, fix second)
<title>(≤60ch) + meta description (≤155ch) present, unique, per locale.- One
<h1>; logical heading order. - Canonical +
hreflangcorrect for every locale. sitemap.xml+robots.txt+llms.txtpresent, current, mutually consistent.- JSON-LD structured data valid (Org/Article/Breadcrumb as fits).
- OG/Twitter cards, alt text on images, no broken internal links.
Fix policy
- Auto-fix (safe): missing/duplicate meta, alt text, llms.txt drift, sitemap staleness, OG tags.
- Propose only (risky): URL/slug changes, redirects, canonical retargeting, content rewrites → list, don't apply.
After
Append run: site, issues found/fixed/proposed, PASS/FAIL, lesson:.
Output
Two tables: Fixed and Needs your OK. Never silently change URLs or redirects.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Abdox-menara/guard-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 repository6 other files it gives its agents.
- deploy-verifySkill
- episode-packageSkill
- localize-humanizeSkill
- skill-onboardSkill
- verify-swarmSkill
- video-cost-estimateSkill
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.

