SEO
Search Console, PageSpeed, SerpAPI and Open Page Rank behind one read-only seo skill, plus wordpress-rest for site content.
The SEO pack shows how a site does in search. Ask in plain words ("how's my site ranking", "is this page fast") and the seo skill picks the playbook. Everything is read-only against the services it queries: it never publishes or edits a site.
What it gives you
| Playbook | Ask | Source | You get |
|---|---|---|---|
| audit | "Run the SEO audit", "why did traffic drop", seo audit | All of the below | Four audit rules, findings ranked by impact, a Markdown report, matches threaded into open tasks |
| console | "What queries bring traffic", "is this page indexed", seo console | Search Console API | Queries, impressions, clicks, CTR, average position, indexing status |
| speed | "Is this page fast", "Core Web Vitals", seo speed <url> | PageSpeed Insights | Lighthouse plus Core Web Vitals (LCP, CLS, INP, FCP, TBT, SI) for any public URL |
| serp | "What's ranking for this query", seo serp <query> | SerpAPI | Live Google SERP: organic, AI overview, shopping, people-also-ask, knowledge graph |
| rank | "Domain authority", seo rank <domain> | Open Page Rank | A free domain-authority proxy, 0 to 10, for trend tracking |
wordpress-rest is its own skill in the same pack: posts, pages, custom types, categories, tags, media, and modified dates for the site at GSC_SITE_URL through the public WP REST API, for SEO work or anything else. The audit reads the same API for modified dates when the site runs WordPress.
What it needs
| Playbook | Needs |
|---|---|
| audit | A Google OAuth client and GSC_SITE_URL; SERPAPI_KEY is optional, and without it the audit skips its SERP checks |
| console | A Google OAuth client and GSC_SITE_URL |
| speed | A Google OAuth client |
| serp | SERPAPI_KEY |
| rank | OPENPAGERANK_API_KEY |
A playbook whose credential is missing says which one and stops. wordpress-rest needs only the site URL. A typical personal setup runs on free tiers; quotas and prices are on Accounts and costs.
Switch it on
Run configure-skills and pick SEO. It asks about each keyed playbook in turn, grants the tools for the ones you want, and tells you which lines to add. Then set up the accounts behind them.
Google Search Console and PageSpeed. One free Cloud project covers both:
<HOME>/.state/secrets/google/google-oauth-client.json.GSC_SITE_URL in <HOME>/.claude/settings.local.json (https://example.com/ or sc-domain:example.com).google_auth tool once. A browser consent flow mints tokens that are cached and shared across the Google tools.SerpAPI. Sign up at serpapi.com and copy the key from the dashboard. The free tier covers a weekly audit of a small site.
Open Page Rank. Sign up at domcop.com/openpagerank and generate the free key.
Both keys go in your editor, never in chat:
# <HOME>/.state/secrets/.env
SERPAPI_KEY=...
OPENPAGERANK_API_KEY=...With GSC_SITE_URL set, the walk also lets wordpress-rest call that one site without asking each time.
The weekly loop
Configure the keys once. Run seo audit weekly. The audit pulls 28 days of Search Console data, runs PageSpeed on the top pages, applies the rules, and writes the report to the project's audits/ folder. Findings that match an open task get threaded onto it.
For content drafting and EEAT scoring, pair it with a third-party skill library: aaron-he-zhu/seo-geo-claude-skills (20 skills) or coreyhaines31/marketingskills (23 playbooks). Both install through configure-skills; see Packs.
Where it's used
- Reach and see: the capability group this pack belongs to.
- Skills: the
seoandwordpress-restskills.
Browser
Screenshots, styled PDFs, pages as Markdown, recordings and scripted flows on a browser the plugin installs for you, plus web search with an optional key.
Slack
Read-only Slack through your own account. A pulse across your channels, the replies you owe, threads where someone outside the workspace is waiting, and channels you joined that the agent doesn't know about yet. It never posts and never reads DMs.