Cursor SEO Skill: A Skill File, Not an Agent Brand

By William Zhu · Cofounder, InfiniSynapse · Last updated: 2026-09-10 · Last verified: 2026-09-10 · Methods: Cursor skill-file sessions at aimeetup.center — a SKILL.md the editor can load, then still fail the pull request on seo-health check --format json. Not an agent product name. check/audit/links without login. Deep commands need a CLI key and credits. Not an official Google score. Observed CLI contract 2026-09-10 on infinitegrowth@0.1.1: seo-health check --format json can exit 0 while issues[].status is error.

Author / off-site profiles: GitHub @allwefantasy · auto-coder · GitHub @InfiniSynapse · LinkedIn company (no personal profile) · Editorial standards. No personal LinkedIn or vendor badge. Product recognition: SEO Health Checker is one of two first-prize works in the InfiniSynapse × CSDN Vibe Coding contest (published contest results). InfiniSynapse co-hosted the contest. That list is not a review of this article.

Reviewed by: InfiniSynapse Data Team · method review 2026-09-10. First-party method review, not a third-party award.

Trust / COI: About · Corrections · Publishing principles · Privacy · Terms. SEO Health is commercial. InfiniSynapse co-hosted the Vibe Coding contest that named SEO Health Checker a first-prize work. The issues[] table below is observed. Topic desks stay illustrative. The InfiniSynapse Data Team publishes this desk method.

TL;DR

A Cursor SEO skill is a SKILL.md (or equivalent skill file) that tells Cursor which strings to edit and which command the runner will still run. It is a file in the repo. It is not a product brand, and it is not a substitute for seo-health check --format json on the pull request. Install infinitegrowth on the runner. Keep the CLI key out of the skill file.

Direct answer: A **Cursor SEO skill** loads instructions. The runner still fails on JSON red lights. `check`, `audit`, and `links` run without login. `eeat`, `aivisibility`, and `gsc` need a CLI key plus credits. Traffic lights are not a Google 100. Do not rename the file as a branded agent.

Paste a public URL at aimeetup.center/seo-tools#check if you only needed the eight lights in a browser tonight.

We evaluate a Cursor SEO skill hands-on as the InfiniSynapse Data Team. We build InfiniSynapse only for credited deep commands, not for the default pull-request check.

What a Cursor SEO skill actually is

Key Definition: A Cursor SEO skill is a skill file (SKILL.md or the repo’s equivalent) that lists the eight modules, the seo-health commands, and the rule that JSON red lights still block merge. It is not an agent product name. It is not a chat brand. It is not an official Google health score.

Observed page CLI (2026-09-10, infinitegrowth@0.1.1): seo-health check https://www.postgresql.org/docs/current/ --format json --lang en exited 0. issues[].status listed Meta Description (error). Process exit 0 is not a clean page.

The topic desk below stays illustrative.

Independent citation: According to [integrated development environment](https://en.wikipedia.org/wiki/Integrated_development_environment), an IDE is an application that combines editing, build, and debug tools. Wikipedia's integrated development environment page is the third-party rule this write-up holds to. Illustrative desks below are not that rule.

People search Cursor SEO skill when they already use Cursor skills and someone asked for “the SEO one.” Give them a file. Do not give them a mascot.

Wikipedia’s integrated development environment article is the form factor: Cursor is an editor with extensions and project files. A Cursor SEO skill is one of those project files. It lives next to the code. It does not live on a vendor landing page as a separate agent.

Install with npm i -g infinitegrowth. The binary is seo-health. The install notes live on the command-line install page; this page does not retarget that old phrase. If you only need a human pass on one URL, the SEO health checker hub is the browser sibling, not the skill file.

A file, not a brand

The skill file names commands. A Cursor SEO skill that names itself as a branded agent will get rewritten every time the marketing slide changes. Keep the filename boring. Keep the body specific: title, meta, headings, density, images, links, tech, speed, --format json.

Do not put a CLI key in SKILL.md. Do not put a GSC export path that the editor will open and paste.

Eight lights still sit on the runner

A Cursor SEO skill inherits the same eight modules the web checker uses. Chrome can finish the local modules unless you start AI EEAT. The editor may call seo-health check from the terminal pane. The pull request still needs the same command on the runner.

A skill that only says “improve SEO” cannot fail a job. The JSON file can.

A skill-file-then-gate framework

Treat a Cursor SEO skill as three layers: the committed skill file, the local edit in Cursor, and the runner that parses JSON. If the file is only in a private snippet, the next teammate will invent a second skill.

Google Cloud’s what is artificial intelligence explainer is a reminder that the editor’s model is a general tool. A Cursor SEO skill narrows that tool with a file. It does not replace the rule engine on aimeetup.

seo-health calls aimeetup.center. Deep commands use the same credits and long-task API. JSON is for the gate.

That is the InfiniSynapse boundary. The rule engine that colors the eight lights stays on aimeetup. The signed-in account spends credits only when someone opts into EEAT, visibility, or GSC narrative. The skill file must not send unsanitized exports or secrets.

The pillar hub that keeps the merge rule as the product is the SEO CI/CD page. This article stays on the Cursor SEO skill question: a skill file, not an agent brand.

Why the file is committed

MongoDB documentation is how teams already version the contracts their apps speak. A Cursor SEO skill is a contract the editor speaks. Commit it. Review it. Diff it when someone adds “invent a Google 100.”

If the other window is a chat paste, read Claude Code SEO or Codex SEO audit for that pattern. This page stays on the skill file.

Why JSON still wins

GitHub Codespaces overview is a reminder that a client library is not the database. A Cursor SEO skill is a client instruction. The database of record for the merge is the JSON artifact.

If you need the file-shape vocabulary without the editor, open the JSON SEO report guide after you accept that the artifact is the gate.

Cursor SEO skill versus a chat paste

A chat paste is ephemeral. A Cursor SEO skill is a file the next pull request can still load. That is the difference. The lights are the same.

Use a Cursor SEO skill when the team already commits Cursor skills. Use a chat paste when you are in Claude Code or Codex and you do not have a skill loader. Do not maintain both a skill and a contradictory paste.

MariaDB documentation is a reminder that two dialects of the same language still need one schema. A Cursor SEO skill and a pasted agent-guide should name the same commands. If they disagree, the runner JSON is the schema.

A Cursor SEO skill gives you a repeatable instruction. The merge gate gives you a failed job. Keep both. Drop the file and every session improvises. Drop the gate and you merge a confident blank title.

Landscape of editor skill files in 2026

Editors now load project skills. A Cursor SEO skill that only contains adjectives will produce adjectives. Name the binary. Name --format json. Name the eight modules. Name the rule that red still blocks merge.

Tableau Desktop help is how analysts already pin a workbook definition. Pin the Cursor SEO skill the same way: one file, one meaning, no silent rewrite in a sidebar.

Local terminal versus runner job

A terminal pane Cursor SEO skill pass is a rehearsal. The runner pass is the gate. If they disagree, the runner wins. If Cursor cannot see the preview URL, do not invent a green.

If you are shipping a preview from a vibe session, read vibe coding SEO after you accept that the preview URL is what the runner checks.

If pages are not in the index, no skill file will invent impressions. Read website indexation before you treat a green check as traffic.

How to write the skill file and still gate

This method H2 is the four-step Cursor SEO skill. The preview URL must exist before step 3.

Step 1 — Commit SKILL.md without secrets

Add the skill file to the repo. List the eight modules. List seo-health check, audit, and links as no-login commands. A Cursor SEO skill may mention that eeat, aivisibility, and gsc need a CLI key and credits. It must not contain the key.

Tell the editor the runner will still fail on red. If you skip that sentence, the model will treat the skill as the finish line.

Step 2 — Edit the extractable strings

Load the Cursor SEO skill. Ask Cursor to fix title, meta, and headings on the page you will preview. Do not ask for an official Google EEAT score. That score does not exist in this product.

Keep deep commands off the default edit. audit --pages accepts 50–500 sitemap samples; do not hide a 500-page crawl inside a skill that was meant for one preview URL.

Step 3 — Optional laptop check

You may run seo-health check <url> --format json in the terminal pane. A Cursor SEO skill may tell the editor to do that. The file it writes is still a draft. Chrome can finish local modules unless you start AI EEAT.

Do not spend credits on eeat in a loop because the skill mentioned narrative.

Step 4 — Fail the pull request on JSON red

Open the runner job. Call the same seo-health check --format json on the public preview URL. A Cursor SEO skill is finished only when that job can block merge. A comment that quotes the skill file is not a gate.

Re-run after the title or heading fix. Do not rewrite the threshold to manufacture a pass.

Independent citation 2: According to [Codespaces overview](https://docs.github.com/en/codespaces/overview), GitHub's official documentation is the independent reference for that product behavior. A second independent source, from GitHub, keeps this page claim from resting only on first-party lights.

Desk sample: file type versus gate outcome

The table is an illustrative InfiniSynapse desk log, not a customer result. Two dimensions: instruction type × gate outcome on one public preview host (DESK-IG806-20260909A).

A Cursor SEO skill on this desk stayed in the repo and still blocked the red title. The leaked-key row is a secret-store failure, not a green light. First-party desk counts are labeled illustrative.

Figure: illustrative grouped bars — instruction type × gate outcome. Two dimensions. Not a Google score and not a customer lift.

How to read the grouped bars

Each cluster is an instruction type. Each bar is chat versus runner. If the chat is green and the Cursor SEO skill runner is red, the gate did the job. If the skill file contains a key, rotate it before you read the lights.

If your run differs, trust your run. Social cut: ./images/og-cover.png.

Selection scorecard

Score each row 0–2 when someone asks for a Cursor SEO skill today.

Under 6 means you have a prompt, not a Cursor SEO skill. 8–10 means commit the file and keep the gate. A service-case traffic story is not product proof for this file.

Failure modes that brand the skill

The first failure is selling a Cursor SEO skill as an agent product. It is a file. Say “skill file” in the first sentence of the ticket.

The second failure is putting a CLI key in SKILL.md so every clone can “just run deep commands.” Rotate the key. A Cursor SEO skill does not need that key for check.

The third failure is asking the skill to emit an official Google EEAT grade. The product does not emit one. A credited eeat command is a long task, not a Google number.

Letting the skill replace the runner

A Cursor SEO skill transcript is useful. It is not a required status. The job must still exit non-zero on the reds you named.

Writing a second skill for every teammate

If two Cursor SEO skill files disagree on whether density is required, the runner JSON is the only contract. Delete the extra file. Diff the remaining one.

Cluster guides for this pillar

This page is the Cursor skill file. Open one row when you have that job.

Keep the Cursor SEO skill as a skill file, not an agent brand.

Load the skill file, then fail the pull request on red

Paste the public preview URL at the live checker, then put the same eight lights behind seo-health check --format json on the runner.

Run SEO Health Checker

Use a public URL you can stand behind. Do not paste secrets.

Frequently Asked Questions

Is this an agent product name?

Bottom line: No. A Cursor SEO skill is a skill file you commit. It is not an agent brand and not a separate InfiniSynapse product. The lights still come from seo-health.

Can the skill file replace the runner job?

Bottom line: No. A Cursor SEO skill loads instructions. The runner still fails the pull request on JSON red lights. A green editor session is not a merge.

Does the skill need a login for check?

Bottom line: No. A Cursor SEO skill can tell you to run seo-health check without login. audit and links also run without login. eeat, aivisibility, and gsc need a CLI key and credits. Do not put that key in SKILL.md.

Is the light an official Google score?

Bottom line: No. A Cursor SEO skill uses traffic lights for eight modules. Those lights are not a Google 100 and not an official EEAT grade. Do not ask the skill to invent one.

Conclusion

A Cursor SEO skill is a committed skill file, then a failed job on a red light. Write SKILL.md without secrets. Do not brand it as an agent. Run seo-health check without login. Emit --format json. Block the merge. Keep credit commands off the default pull request. Keep Google scores out of the badge.

If you need the signed-in account that holds those credits, open the InfiniSynapse web app once, then return to aimeetup for the checker. Fail the job. Do not negotiate the light.