agentleFS
akp-allianceakp-alliance/npx-skills-add-coreyhaines31-marketingskills/.claude/skills/schema-markup/SKILL.md

schema-markup

Skill4 starsChanged 8 months agoNo licenceView on GitHub

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.

68 other projects use a version of this, 25 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use keyword-cannibalization, broken-links and 5 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.
  • keuperaSkill

    keyword-cannibalization

    Detect and fix cases where several pages on the same site compete for the same query, splitting signals and suppressing all of them. Use whenever the user mentions keyword cannibalization, pages competing with each other, the wrong page ranking for a query, rankings that keep swapping between URLs, duplicate topics, or has published many posts on similar subjects. Also use when a page won't rank despite being good, or when Search Console shows several URLs alternating for one term.

    Also in 3 projects that use this

  • akii-technologies-ltdSkill

    broken-links

    Find and fix broken links — three modes with different scale ceilings. `local` audits any local repo (HTML/MD/MDX, no size limit) via Glob/Grep + per-link verification. `page` checks one live URL deeply (~30-100 outbound links per run). `site` requires the Ahrefs site-audit MCP for true multi-page crawl — without it, refuses and tells the user how to get there. Use when the user asks to "check broken links", "find dead links", "fix 404s", "link checker", "broken link audit", "redirect chains", "find dead URLs", "link validation", "mixed content". Accepts a mode modifier (`--mode=local|page|site`); auto-detects from the target if unspecified.

    Also in 3 projects that use this

  • JakeLabateSkill

    internal-link-audit

    Audit a website's internal linking structure for SEO. Crawls pages to find broken internal links, orphan pages, redirect chains, deep pages, missing or weak anchor text, and internal link distribution issues. Use when the user asks to audit, analyze, or improve internal links, site structure, link equity, or crawlability of a website.

    Also in 3 projects that use this

  • tifetolaSkill

    on-page-seo

    Also in 3 projects that use this

  • danielimadSkill

    technical-seo-audit

    Analyses a website crawl export (Screaming Frog, Sitebulb, or Ahrefs Site Audit) and returns a prioritised list of technical SEO issues. Finds redirect chains and loops, duplicate title tags and meta descriptions, pages Google cannot index or render, broken internal links, and orphan pages. Trigger when the user uploads or points to a crawl file, a CSV or XLSX of URLs with status codes, or asks for a technical SEO audit, a crawl analysis, or to "find redirect chains".

    Also in 4 projects that use this

  • LangChainSkill

    content-brief

    Turn a vague or multi-asset design ask into a brief. Pull what is already known, ask at most two questions with reasons, decide the rest and say what you decided.

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.