SEO skills for Claude

Each skill turns a job I repeat for different clients into a fixed process with a consistent deliverable. A few of mine:

• client-profile: an interview that researches the site first, then saves positioning, competitors and buyer questions as a Markdown file and a synced spreadsheet
• semantic: works a list of NLP terms into an existing post with sentence-level edits only. A check script fails the edit if the heading outline changes or the post grows more than 15%
• site-map-builder: a colour-coded sitemap workbook built from a JSON spec
• sitemap-schema-generator: reads a sitemap, classifies every page and writes JSON-LD for each
• AI-search gap analysis: classifies the sources AI answers cite and turns the gaps into an update-or-create plan
• table: turns a screenshot of a table into clean semantic HTML

I make the same kinds of deliverables for different clients: profiles, briefs, sitemaps, schema and audits. Writing each process down once keeps the output consistent. Every skill in the bundle states what it needs and reports a missing dependency instead of filling the gap with made-up data.

• Each skill is a folder with a SKILL.md, plus scripts, references and assets where needed.
• Scripts handle the formatting. Claude writes a JSON spec and Python builds the workbook from it.
• Client-facing skills read the client's profile first, so rewrites and briefs stay within what the client actually offers.
• On my machine, each skill is linked into Claude Code's skills folder so it runs as a slash command.
• For Cowork, 23 skills ship as one plugin, with script paths resolved at run time. The bundle also includes open-source SEO and blog skills I use alongside my own.

Packaging matters as much as the prompt. A skill folder isn't a command until it's linked into the folder Claude Code scans, and the plugin uploader rejects a zip without a plugin manifest at its root. Cowork also gets a copy, not a link, so every edit to a source skill means rebuilding and reinstalling the bundle.