About

SEO.party is a library of community skills for OpenSEO: SKILL.md workflows for Claude Code, Codex, Cursor, and the rest, each with what it does and how far it has been reviewed.

What this is

A skill is a folder with a SKILL.md file that teaches an agent one job, such as finding pages that lost clicks in Search Console. Skills live on GitHub. We index them, snapshot every file at a commit, and check them. We never host or edit the source.

Built for OpenSEO

Every skill here gets its data from the OpenSEO MCP tools, so you need OpenSEO connected to your agent, through the MCP server or the plugin. Once it is connected, every skill works. We only list skills that use OpenSEO.

Three tiers

TierMade byReviewed byYou install
OfficialOpenSEOA person, at a pinned commitThe reviewed commit
VerifiedA community authorA person, at a pinned commitThe reviewed commit
CommunityA community authorAutomated checks onlyThe latest commit that passed the checks

Only we set tiers, and nobody can pay for one. Under an Official or Verified badge, the page, the install commands, the API, and the MCP tools all serve the commit a person reviewed. When the author pushes a change, the reviewed version keeps serving until the new one is reviewed. Skills we take down show as Delisted (hidden, with installs left alone) or Critical (removed for a security problem; uninstall it).

How listing works

Anyone signed in can submit a public GitHub URL, and we find every skill in the repo. Credit stays with the repository's GitHub owner: every skill, whoever submitted it, is listed under that owner's GitHub name. Each version goes through the automated checks in the rulebook: a Block, such as a skill that never uses OpenSEO, must be fixed before listing. Passing lists the skill in the Community tier. Verified also needs an open source license and a person's review at a pinned commit.

Listing is free and never sold. Editors pick featured skills by hand, never from counts.

How installs are counted

One install per person per skill per day (UTC), across the install and copy buttons on this site, raw file and zip downloads through the API, the discovery index the skills CLI reads, and MCP skill loads. We tell people apart by a salted hash of their account, or of their IP address and browser; we never store either in the clear. Crawlers and update checks are not counted. GitHub stars belong to the skill's repository; they are shown separately and never added to installs.

Operator policy

What we may change about a listing, and when:

  • We never edit a skill's files or publish a changed copy under the author's name. What you install is the author's commit.
  • We may change a listing's tier and tags, delist it, or mark it critical. Takedowns appear in the public revocation list with the reason.
  • Ownership follows GitHub. We move a listing to a new owner only when its repository is transferred, or on a valid legal request, and we log the change.
  • We do not fork skills. If a source repository disappears, the listing keeps the snapshot we indexed, credited to its author, until the author asks us to remove it.