Ready-made AI skills

An open library of prepared workflows for common agency jobs, installed into ChatGPT, Claude or Cursor.

A skill is a set of prepared instructions for a job that comes up often. Instead of explaining a whole migration from scratch, you install a skill and your AI tool already knows the steps, the order to do them in, and the mistakes to avoid.

The skills are published as an open library on GitHub at github.com/BrightSiteHQ/brightsite-skills. You can read exactly what any of them does before installing it.

Why they help

An AI tool connected to BrightSite can do a great deal, but it does not know how you want a job done. Left to itself it will make reasonable guesses, and the guesses vary between runs.

A skill removes that variance. It encodes a method: what to check first, what to do in what order, what to confirm with you before continuing, what to leave in draft. The result is that the same job produces the same shape of output every time, whoever runs it.

For agencies this is the main appeal. A skill is how one person's approach to a job becomes the whole team's approach.

What is in the library

Skill	What it does
`migrate-wordpress-blog`	Moves a WordPress blog across, keeping addresses consistent and setting up redirects where they change.
`generate-location-pages`	Produces a page per town or service area from a list, with wording varied rather than copied.
`bulk-seo-audit`	Walks every page for missing titles and descriptions, duplicate headings, thin content and broken internal links.
`redirect-map-from-csv`	Turns a spreadsheet of old and new addresses into working redirects, which is what saves your rankings after a rebuild.
`client-handoff-checklist`	Works through what should be in place before a site is handed over.
`blog-post-from-outline`	Turns notes or a heading structure into a full draft in a consistent house style.
`visual-editor-authoring`	Builds pages that a non-technical client can actually edit in the visual editor afterwards.
`visual-editor-audit`	Checks an existing site for anything the client cannot edit, and can fix it.
`staging-redesign`	Runs a redesign on a staging copy so the live site is untouched until you promote it.
`supabase-portal`	Building a customer portal backed by Supabase.

The library grows, so check the repository for the current list.

Before you install

Your BrightSite connection needs to be working first. A skill is only instructions, and the actions still run through your connection and your role. See Connecting an AI tool, or Claude for the exact setup.

The skills expect the connection to be registered under the name brightsite, which is what the standard setup instructions use.

Installing them

Three ways, depending on your setup. All install into your AI tool, not into BrightSite.

Using npx, which works with any assistant

The simplest option, and the one to use if you are not sure:

npx skills add BrightSiteHQ/brightsite-skills

That installs into the current project. To make them available everywhere instead:

npx skills add -g BrightSiteHQ/brightsite-skills

Use npx skills list to see what you have installed, and npx skills update to pull the latest versions.

As a Claude Code plugin

If you use Claude Code, you can add the library as a plugin marketplace:

/plugin marketplace add BrightSiteHQ/brightsite-skills
/plugin install brightsite-skills@brightsite

By hand

You can also clone the repository and copy the skills directory into ~/.claude/skills/ yourself. The repository README has the exact commands.

Using one

Once installed, ask for the job in plain language. Your assistant matches the request to the skill and follows it. You do not need to name the skill, though naming it does no harm:

Migrate the WordPress blog at example.com into my Riverside Dental account.

They are early, so read before you run

The library's own status note is worth repeating. These skills were drafted against the BrightSite tool definitions and reviewed, but each one benefits from a run against a real account before you trust it with production data.

Two habits are worth keeping:

Try it on a staging site or a low-stakes site first. You learn what it produces without any risk.
Have it leave work in draft. Review, then publish yourself.

Some checks a skill performs are deliberately weaker than what you could do in the BrightSite dashboard, because not every field is exposed to AI tools. A well-written skill tells you when a check is limited and asks you to verify in the app. Do that rather than assuming it is covered.

Adapting them

Because the library is open, you can copy a skill and change it. Most agencies end up with their own versions: the same method with their house style, their checklist, their client-specific rules. That is the intended use, not a workaround.

The repository takes contributions, so a skill you improve can go back to everyone.

Last updated September 8, 2026