agentleFS
gaznilmuzammil12-proggaznilmuzammil12-prog/seo-skills-by-gaznil/llms.txt

seo-skills-by-gaznil

llms.txt0 starsChanged 3 months agoMITView on GitHub

A complete, de-duplicated library of 81 SEO and content Agent Skills for Claude. Covers technical SEO, on-page, AI search (GEO/AEO/LLMO), ecommerce, international, backlinks, local, measurement, and a full blog content pipeline. Every skill does exactly one job no other skill in the set does. Installs into Claude Code, Claude Desktop, and any agent that reads the Agent Skills format. MIT licensed. Free. Install: npx skills add gaznil/seo-skills-by-gaznil Most SEO skill collections are either a single oversized skill or a large…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
llms.txt
# SEO Skills by Gaznil

> A complete, de-duplicated library of 81 SEO and content Agent Skills for Claude. Covers technical SEO, on-page, AI search (GEO/AEO/LLMO), ecommerce, international, backlinks, local, measurement, and a full blog content pipeline. Every skill does exactly one job no other skill in the set does.

Installs into Claude Code, Claude Desktop, and any agent that reads the Agent Skills format. MIT licensed. Free.

Install: `npx skills add gaznil/seo-skills-by-gaznil`

## What makes it different

Most SEO skill collections are either a single oversized skill or a large pile with overlapping coverage. This library was assembled by reading every candidate skill, then removing anything that duplicated a job another skill already did. Three verification passes were run: purpose de-duplication, name-collision checking against widely-installed packs, and dangling-reference tracing so every internal "see also" resolves to a skill that exists.

## Coverage

- AI search: ai-seo, blog-geo, serp-features, featured-snippet, entity-seo
- Strategy: seo-strategy, seo-audit, keyword-research, site-architecture, programmatic-seo, seo-cluster, competitors
- On-page: title-tag, meta-description, heading-structure, page-metadata, open-graph, twitter-cards, url-structure, canonical-tag, internal-links, schema-markup, eeat-signals, content-optimization
- Technical: site-crawlability, indexing, robots-txt, xml-sitemap, core-web-vitals, mobile-friendly, rendering-strategies, indexnow
- Ecommerce and local: seo-ecommerce, local-seo, seo-maps
- International: seo-hreflang, blog-multilingual, blog-localize, blog-translate, blog-locale-audit
- Media: seo-images, video-optimization, accessibility, blog-image, blog-chart, blog-audio
- Off-page: seo-backlinks, public-relations, directory-submissions, parasite-seo
- Content: copywriting, seo-content-brief, blog and the blog-* pipeline
- Operations: seo-drift, blog-audit, blog-seo-check, blog-cannibalization, blog-factcheck
- Measurement: google-search-console, analytics, attribution, ab-testing, cro

## Links

- Repository: https://github.com/gaznil/seo-skills-by-gaznil
- Full skill catalogue: https://github.com/gaznil/seo-skills-by-gaznil#the-81-skills
- Licence and attribution: https://github.com/gaznil/seo-skills-by-gaznil/blob/main/NOTICE.md
- Full context for AI systems: https://github.com/gaznil/seo-skills-by-gaznil/blob/main/llms-full.txt

## Not covered

Log file analysis, site migration SEO, and penalty recovery. No good implementation of these exists in the Agent Skills ecosystem as of this writing.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.