Sitebulb Skills

Official Sitebulb plugins for AI coding agents: five technical-SEO skills that work directly with your Sitebulb Desktop or Cloud audit data. Ask your assistant what to fix first, what changed since the last crawl, produce a client-ready audit document, raise dev tickets, or run your post-release check — all grounded in your real crawl data, never guesswork.

Works in Claude Code, Codex, Cursor, GitHub Copilot, and other agents that read the open SKILL.md plugin format.

Choose your plugin

There is one plugin for each Sitebulb product. Each plugin has the same five skills and connects to the MCP server of its product:

Install the plugin for the product you use. If you use both products, you can install both plugins. Then the skills ask which product to use.

Upgrading from the sitebulb plugin

The sitebulb plugin (last release 0.2.0) is replaced by sitebulb-desktop and sitebulb-cloud. If you installed sitebulb:

1. Uninstall sitebulb. If you keep it, your assistant has each skill two times.
   • Claude Code: /plugin uninstall sitebulb@sitebulb, or claude plugin uninstall sitebulb@sitebulb from a terminal.
   • Codex: in the Codex app, open the plugin and select Uninstall plugin. In Codex CLI, enter /plugins and uninstall Sitebulb in the plugin browser.
   • Cursor, GitHub Copilot and other agents: remove it in the plugin settings of your assistant. In Cursor, installed plugins are under Customize in the sidebar.
2. Install sitebulb-desktop or sitebulb-cloud for your product, as shown below.
3. If you added the Sitebulb MCP to your assistant yourself, for example as a custom connector, remove it. The new plugin connects its own server, and two connections give your assistant two sets of the same tools.

Installation

The examples install sitebulb-desktop. For Sitebulb Cloud, write sitebulb-cloud in its place.

Claude Code

/plugin marketplace add sitebulb/sitebulb-plugin
/plugin install sitebulb-desktop@sitebulb

Codex

Codex app: open Plugins from the sidebar, choose Add plugin marketplace, enter sitebulb/sitebulb-plugin as the source (Git ref main), then install Sitebulb Desktop or Sitebulb Cloud and restart Codex.

Codex CLI:

codex plugin marketplace add sitebulb/sitebulb-plugin
codex plugin add sitebulb-desktop@sitebulb

Cursor

In Cursor Agent chat:

/add-plugin sitebulb-desktop

Or search for "Sitebulb" in the plugin marketplace.

GitHub Copilot

Copilot CLI (inside the CLI, or from a shell with the copilot binary prefixed by copilot):

/plugin marketplace add sitebulb/sitebulb-plugin
/plugin install sitebulb-desktop@sitebulb

VS Code: run Chat: Install Plugin from Source from the command palette, enter sitebulb/sitebulb-plugin, and select sitebulb-desktop or sitebulb-cloud.

Other agents

Any agent that reads Claude-compatible plugin manifests installs this repo directly — for example:

droid plugin marketplace add https://github.com/sitebulb/sitebulb-plugin && droid plugin install sitebulb-desktop@sitebulb
qwen extensions install sitebulb/sitebulb-plugin:sitebulb-desktop
grok plugin marketplace add sitebulb/sitebulb-plugin && grok plugin install sitebulb-desktop

Connecting to Sitebulb

Each plugin declares its MCP server: https://desktop.mcp.sitebulb.com/mcp for Sitebulb Desktop or https://cloud.mcp.sitebulb.com/mcp for Sitebulb Cloud. When a skill first reads your audits, your assistant asks you to sign in to your Sitebulb account with OAuth. Sitebulb Desktop must be open and running on your computer for the Desktop server to read your audits.

If your assistant does not connect the server from the plugin, connect it yourself with the guide for your assistant. If a skill runs before the MCP is connected, it points you at the same guide:

→ Sitebulb MCP: Start Here

Requirements: a Sitebulb Desktop or Sitebulb Cloud licence, at least one finished audit in the project you want to work with, and python3 available to the agent (the skills bundle small stdlib-only scripts for scoring and document generation). The connection is read-only — skills can read your audits but never trigger crawls.

The skills

Both plugins have all five skills, because Sitebulb Desktop and Sitebulb Cloud give the skills the same tools. The table uses the Desktop plugin's prefix. In the Cloud plugin, the prefix is sitebulb-cloud:.

Skills trigger automatically when you ask for the matching work — you don't need to invoke them by name.

Optional integrations

Some features light up when other tools are connected:

• A PM-tool MCP (Jira, Linear, Asana, Monday, ClickUp) lets sitebulb-dev-handoff create tickets directly. Without one, it produces ready-to-paste markdown ticket bodies.
• A messaging MCP (Slack, Teams, …) lets sitebulb-release-check post breach alerts to a channel. Without one, alerts appear in chat.
• Google Analytics / Search Console connected inside Sitebulb lets sitebulb-what-to-fix-first and sitebulb-technical-seo-audit weight priorities by real traffic, and gives sitebulb-what-changed a search-performance overlay.

Licence

MIT — see LICENSE. © Sitebulb Ltd.

Contributing / maintenance

plugins/sitebulb-desktop/ and plugins/sitebulb-cloud/ must each be complete on their own: the plugin directories install, validate and package one plugin folder at a time, and refuse symbolic links and paths outside the folder. So each plugin carries a copy of the skills, the licence and the logo, generated from shared/. Edit there and run python3 scripts/sync_shared.py. Each plugin's manifests, .mcp.json and README.md are written by hand. CI enforces sync, runs the test suites, validates the manifests, and runs claude plugin validate on each plugin.