agentsclimarketplace

Super seo foundation

Skill arpitexplores/super-seo-foundation

SEO foundations: audits, technical fixes, schema, sitemaps, hreflang, images, and tooling. Use for baseline health and technical readiness.From its SKILL.md

Install
npx -y skills add arpitexplores/super-seo-foundation

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

  • 0 stars0 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.

SKILL.md

1.8 KB, 387 tokens by cl100k_base, as published. Nobody here has run it

Super SEO Foundation

Overview

Single entry point for technical SEO work. Routes requests to the correct module and asks only minimal questions.

User Intent Examples

  • "Need help with SEO Audit for my product/site."
  • "Create a plan for Google SEO Tooling."
  • "Audit or improve Schema & Technical SEO."

Capabilities

  • Full or lightweight SEO audits
  • Technical checks (crawl, index, CWV, headers)
  • Schema, sitemaps, hreflang, images
  • Google Search Console / PageSpeed / CrUX workflows

Routing Map (Modules)

  • SEO Audit -> references/modules/seo-audit.md
  • Google SEO Tooling -> references/modules/seo-google.md
  • Schema & Technical SEO -> references/modules/seo-schema.md

Default Flow

  1. If a URL is provided, run the full audit module.
  2. If no URL, ask for the URL and target market.
  3. If user asks a specific area (schema, CWV, etc.), jump to that module.

Minimal Intake Questions

Ask only what’s missing:

  • Primary URL(s)
  • Target market/region (if relevant)
  • Scope (full site vs single page) if unclear

Output Format

  • Audit summary
  • Prioritized fixes (impact/effort)
  • Validation checklist
  • Risks and next steps

Bundled References

  • references/modules/
  • scripts/
  • assets/
  • agents/

Compatibility Notes

  • If any module references slash commands or tool-specific paths, translate them into plain-language steps.
  • Keep outputs platform-agnostic unless the user specifies a specific tool, stack, or agent.

Guardrails

  • Do not claim live metrics without data.
  • Separate confirmed issues from hypotheses.
  • Make each fix actionable and testable.

What ships with it: 66 files

3122.6 KB alongside SKILL.md, 48 of them executable

agents/

examples/

26 more files not listed here. See all 66 in the repository.

Gives 0 of the 12 instructions most marketing audience skills give in 387 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • jump to specific module for channel-specific requests
  • keep outputs platform-agnostic unless specified
  • run the full audit module if a URL is provided

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 326,401. 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.