agentleFS
brayandiazcbrayandiazc/project-starter-template-es-ai/.claude/skills/seo-audit/SKILL.md

seo-audit

Skill15 starsChanged 2 months agoMITView on GitHub

Audita los metadatos SEO de una página o ruta (title, description, canonical, Open Graph, robots) frente a las convenciones de SEO del proyecto y enumera lo que falta o está mal. Úsalo cuando la persona pida revisar/auditar el SEO, revisar las meta tags o verificar que una página esté lista para buscadores (p. ej. "audita el SEO de la página de precios", "revisa las meta tags de esta ruta").

185 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use openseo-release-notes, community-led-growth 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.
  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • JwuthriSkill

    openseo-review-web-content

    Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 14 projects that use this

  • +4 more from nicepkg
  • +3 more from Jwuthri

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 0

    Distinctive

    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
  1. Very specific:

    NO reescribas la metadata de forma silenciosa a menos que la persona lo pida — informa primero los hallazgos.

    line 21

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

Audita los metadatos SEO de la página/ruta que indique la persona.

  1. Lee docs/conventions/seo.md para conocer las tags requeridas del proyecto, los formatos de valor (p. ej. longitud del title, longitud de la description), las reglas por tipo de página y qué páginas deben indexarse frente a noindex.
  2. Identifica los archivos fuente de la página/ruta y dónde se define su metadata.
  3. Verifica cada ítem requerido frente al documento de convenciones:
    • <title> — presente, único, dentro de la regla de longitud.
    • meta description — presente, dentro de la longitud, descriptiva.
    • URL canónica — presente y correcta.
    • Open Graph / tags sociales — og:title, og:description, og:image, etc. según se requiera.
    • directivas robots — correctas para este tipo de página (p. ej. noindex en páginas privadas/utilitarias).
    • Datos estructurados, si la convención lo requiere.
  4. Produce un informe en forma de lista de verificación: cada ítem marcado como Presente / Falta / Incorrecto, con el archivo:línea y una sugerencia concreta de corrección para cada problema.

Ejemplo de hallazgo: Falta canonical — añádelo a app/pricing/page.tsx; la convención exige uno en cada página indexable.

NO reescribas la metadata de forma silenciosa a menos que la persona lo pida — informa primero los hallazgos. Da siempre prioridad a docs/conventions/seo.md por encima de consejos genéricos de SEO.

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.