agentleFS
RylaispiritRylaispirit/rylai-codex-hermes-skills/skills/seo/SKILL.md

seo

Skill56 starsChanged 3 months agoMITView on GitHub

Perform an evidence-led SEO audit using accessible pages, source code, crawl data, and current search documentation without assuming missing plugins.

156 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-maps and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 5 projects that use this

  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 17 projects that use this

  • megastepSkill

    seo-images

    Image optimization analysis for SEO and performance. Checks alt text, file sizes, formats, responsive images, lazy loading, and CLS prevention. Use when user says "image optimization", "alt text", "image SEO", "image size", or "image audit".

    Also in 24 projects that use this

  • timruebenachSkill

    seo-image-gen

    AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".

    Also in 15 projects that use this

  • megastepSkill

    seo-sitemap

    Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

    Also in 26 projects that use this

  • renepfSkill

    orch-pipeline

    Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

    Also in 4 projects that use this

  • +3 more from timruebenach
  • +1 more from megastep

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 145 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check tools, packages, credentials, network access, and runtime capabilities before execution.

    line 29
  2. Distinctive:

    Do not claim a full crawl, Search Console result, Core Web Vitals measurement, or backlink audit without the relevant data.

    line 48
  3. Distinctive:

    Do not invent rankings, traffic, index status, or competitor metrics.

    line 49
  4. Distinctive:

    Prefer narrow implementation fixes tied to evidence.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 145 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rylai Codex-Hermes-Claude Edition | Maintained and adapted by Rylai

Runtime Compatibility

  • Codex: install under ~/.agents/skills/seo.
  • Hermes: install under ~/.hermes/skills/seo or expose the bundle through skills.external_dirs.
  • Claude Code: install under ~/.claude/skills/seo or <project>/.claude/skills/seo.
  • Claude.ai and Cowork: upload and enable the matching per-skill ZIP.
  • Resolve bundled files relative to this skill directory; do not depend on paths from another machine.
  • Check tools, packages, credentials, network access, and runtime capabilities before execution.
  • Upstream package status: adapted-core. The main workflow was rewritten to avoid missing legacy resources; advanced upstream features may remain unavailable.

Portable SEO Audi

Audit the exact website or page using evidence available to the current runtime.

Workflow

  1. Confirm the target URL, market, language, business type, and audit scope.
  2. Fetch or browse the live page and inspect rendered content, HTML, metadata, links, and indexability signals.
  3. Review technical basics: status codes, canonicals, robots directives, sitemap exposure, headings, structured data, mobile behavior, and performance evidence.
  4. Review search intent, page usefulness, internal linking, duplication, and content gaps.
  5. Separate observed defects from recommendations that need Search Console, analytics, backlink, or crawl data.
  6. Prioritize findings by impact, confidence, effort, and affected routes.
  7. Re-check current search-engine documentation before asserting time-sensitive rules.

Boundaries

  • Do not claim a full crawl, Search Console result, Core Web Vitals measurement, or backlink audit without the relevant data.
  • Do not invent rankings, traffic, index status, or competitor metrics.
  • Prefer narrow implementation fixes tied to evidence.

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.