agentsclimarketplace

Speckit.seo

Skill wedabro/bro-skills/.agents/skills/speckit.seo

bro-skills - Spec-Driven Development CLI

Install
npx -y skills add wedabro/bro-skills --skill speckit.seo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Technical SEO Lead - Optimize Meta Tags, Sitemap, Core Web Vitals, Schema.org.

SKILL.md

1.3 KB, 354 tokens by cl100k_base, as published. Nobody here has run it

🎯 Mission

Ensure all public pages meet Technical SEO standards and are ready for AI Search (GEO).

πŸ“₯ Input

  • Source code (pages, layouts, components)
  • .agent/knowledge_base/seo_standards.md (checklist)

πŸ“‹ Protocol

Step 1: Audit Technical SEO

  • Is each page <title> unique, ≀60 characters?
  • Each page has <meta description> , ≀160 characters?
  • Standard heading hierarchy (1 <h1> per page, H1β†’H2β†’H3)?
  • Canonical URLs set for every page?
  • Structured Data (JSON-LD) correct schema?

Step 2: Core Web Vitals

  • LCP < 2.5s, INP < 200ms, CLS < 0.1
  • Images: WebP/AVIF, lazy loading, explicit width/height
  • Fonts: font-display: swap

Step 3: Crawlability

  • robots.txt does not block CSS/JS
  • sitemap.xml auto-generate
  • Reasonable internal linking structure
  • Custom 404 page

Step 4: Output

Report at .agent/memory/seo-audit-report.md :

  • Issues: πŸ”΄ Critical / 🟑 Warning / 🟒 Info
  • Fix suggestions for each issue
  • Total Score (0-100)

πŸ“€ Output

  • File: .agent/memory/seo-audit-report.md

πŸ”— Handoffs

  • @speckit.geo : After Technical SEO passes β†’ switch to GEO audit
  • @speckit.implement : Fix detected issues

Gives 1 of the 12 instructions most seo skills give in 354 tokens

Counted across 454 of the 460 authors here whose files we hold, read 2026-08-06

  • implement structured data using JSON-LDhere, and in 30 of 454, across 26 files
  • write unique meta descriptions under 160 charactersin 27 of 454, across 20 files
  • verify one H1 exists per pagein 24 of 454, across 15 files
  • maintain a single h1 per pagein 24 of 454, across 15 files
  • use JSON-LD format for all schema markupin 23 of 454, across 15 files
  • use descriptive anchor text for internal linksin 21 of 454, across 16 files
  • add descriptive alt text to imagesin 19 of 454, across 15 files
  • read product marketing context before auditingin 19 of 454, across 10 files
  • write unique title tags under 60 charactersin 19 of 454, across 14 files
  • add unique title and meta description per pagein 19 of 454, across 17 files
  • Reference the sitemap in robots.txtin 19 of 454, across 18 files
  • verify core web vitals meet thresholdsin 17 of 454, across 9 files

Said here and by no other author read

  • ensure robots.txt allows css and js

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.