seo-audit SKILL.md skillB
seo-audit in coreyhaines31/marketingskills is at v2.2.5 (Nov 9, 2026), graded B.
mdr add coreyhaines31/marketingskills/seo-audit@v2.2.5This copy is 13 versions behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
seo-audit from mppyxx/claude-power-pack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mppyxx/claude-power-pack
- Path
extras/seo-audit/SKILL.md- Versions recorded
- 1
- Latest version
- v1.1.0, committed Oct 8, 2026
- Size
- 10,723 bytes
- Repository stars
- 5
- License
- a license file GitHub does not identify
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SEO Audit You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before auditing, understand: 1. **Site Context** - What type of site? (SaaS, e-commerce, blog, etc.) - What's the primary business goal for SEO? - What keywords/topics are priorities? 2. **Current State** - Any known issues or concerns? - Current organic traffic level? - Recent changes or migrations? 3. **Scope** - Full site audit or specific pages? - Technical + on-page, or one focus area? - Access to Search Console / analytics? --- ## Audit Framework ### Schema Markup Detection Limitation **`web_fetch` and `curl` cannot reliably detect structured data / schema markup.** …
Read the whole file at its exact version.
How to install
mdr add mppyxx/claude-power-pack/seo-audit@v1.1.0Pins v1.1.0 in mdr.lock, 13 versions behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2cvjawbqvtilnxdu/a6e064274364a743faeebe24c767ead7c5259cd71025aee784b2414c2e014918.json
Then /plugin install seo-audit@markdownregistry-2cvjawbqvtilnxdu in Claude Code. It installs v1.1.0, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add mppyxx/claude-power-pack/seo-audit@sha256:a6e064274364a743The older copy line above pins the label v1.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2cvjawbqvtilnxdu)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest coreyhaines31/marketingskills/seo-audit, and what changed since a6e0642? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of seo-audit from somewhere else? Ask it: where did my seo-audit come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 8, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: v2.2.5 of seo-audit in coreyhaines31/marketingskills (skills/seo-audit/SKILL.md), graded B.
This copy: byte for byte that file's version v1.1.0, which it committed on Mar 28, 2026, before this repository did; graded B, 13 versions behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/seo-audit/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10723 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
mppyxx/claude-power-pack · 5 stars · license a license file GitHub does not identify · pushed 2026-11-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2cvjawbqvtilnxdu GET https://markdownregistry.com/api/v1/resolve?ref=mppyxx/claude-power-pack/seo-audit GET https://markdownregistry.com/api/v1/blob/a6e064274364a743faeebe24c767ead7c5259cd71025aee784b2414c2e014918
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from mppyxx/claude-power-pack
Every file in mppyxx/claude-power-pack