javascript-seo SKILL.md skillB
javascript-seo from 6t9xstar/one-step-seo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 6t9xstar/one-step-seo/javascript-seo@git:20261108.80f295bPins git:20261108.80f295b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 6t9xstar/one-step-seo
- Path
skills/javascript-seo/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261108.80f295b, committed Nov 8, 2026
- Size
- 5,506 bytes
- Repository stars
- 5
- License
- MIT
Diagnose client-side rendering (CSR) vs SSR/SSG visibility gaps, empty SPA shells, AI crawler raw-HTML blindness, third-party script bloat, and oversized HTML hydration payloads.
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
# javascript-seo — JavaScript Rendering, SPA/SSR Visibility & Payload Hygiene ## 1. Description & Activation Criteria Activate `javascript-seo` when the user wants to: - Audit React, Next.js, Astro, Nuxt, Vue, SvelteKit, Angular, or Vite applications for SSR/SSG vs client-side rendering (CSR) SEO & AI visibility gaps. - Diagnose why AI crawlers (`GPTBot`, `ClaudeBot`, `PerplexityBot` — which **do not execute JavaScript**) see a blank `<div id="root"></div>` shell even when the site looks fine in Chrome. - Remediate CSR shell symptoms (`O01-title-missing` P0, `O03-h1-missing` P1, `C01-thin` P1, `O10-internal` P1, `G11-semantic-content` P3) and hydration bloat (`T14-third-party` P2, `P01-html-size` P2, `T00-truncated` P2). ## 2. Inputs & Prerequisites - **Target**: Live SPA/SSR URL or local build output directory (`./dist`, `./out`, `.next/server/app`). - **Why `one-step-seo` is ideal for JavaScript SEO**: - `one-step-seo` intentionally inspects **raw HTTP HTML responses without a headless browser** — matching the exact raw HTML payload seen by `GPTBot`, `ClaudeBot`, `PerplexityBot`, social card scrapers, and first-wave search crawlers before deferred JS execution. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hgr5lloa2yuazo6f/6af78227aa752e13e0ae2bb3d07e7f9497d99f7b8df2b2b1ab2a8291fb5454fd.json
Then /plugin install javascript-seo@markdownregistry-hgr5lloa2yuazo6f in Claude Code. It installs git:20261108.80f295b, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add 6t9xstar/one-step-seo/javascript-seo@sha256:6af78227aa752e13The line at the top of this page pins the label git:20261108.80f295b, 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_hgr5lloa2yuazo6f)
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: what changed in 6t9xstar/one-step-seo/javascript-seo since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of javascript-seo from somewhere else? Ask it: where did my javascript-seo 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 Nov 8, 2026.
Watch this file (sign in, one email per new version)
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/javascript-seo/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 (5506 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
6t9xstar/one-step-seo · 5 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hgr5lloa2yuazo6f GET https://markdownregistry.com/api/v1/resolve?ref=6t9xstar/one-step-seo/javascript-seo GET https://markdownregistry.com/api/v1/blob/6af78227aa752e13e0ae2bb3d07e7f9497d99f7b8df2b2b1ab2a8291fb5454fd
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 6t9xstar/one-step-seo
Every file in 6t9xstar/one-step-seo