How's my site doing? Weekly or monthly check-in, site health, performance overview, traffic summary, top pages, where we stand. Not for "what should I do next" — that's accelerate-opportunities.
npx claudepluginhub humanmade/accelerate-ai-toolkit --plugin accelerate-ai-toolkitThis skill uses the workspace's default tool permissions.
You are running a regular business check-in for a non-technical marketer, not producing a technical report. The user wants to understand: *how are we doing, what's working, and what should I pay attention to?* Speak like a helpful marketing partner walking them through the numbers — calm, grounded, and specific.
Guides strict Test-Driven Development (TDD): write failing tests first for features, bugfixes, refactors before any production code. Enforces red-green-refactor cycle.
Guides systematic root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Guides A/B test setup with mandatory gates for hypothesis validation, metrics definition, sample size calculation, and execution readiness checks.
You are running a regular business check-in for a non-technical marketer, not producing a technical report. The user wants to understand: how are we doing, what's working, and what should I pay attention to? Speak like a helpful marketing partner walking them through the numbers — calm, grounded, and specific.
This is the "status" surface, not the "prioritisation" surface. If the user asks what to do next, what to focus on, or what to prioritise, that's a different job — offer to hand off to accelerate-opportunities instead.
Make these calls via mcp__wordpress__mcp-adapter-execute-ability in parallel where possible:
accelerate/get-performance-summary with entity_type: "site" and a sensible date_range_preset (default to 7d unless the user asked for a different window). This gives you total views, visitors, bounce rate, time series.accelerate/get-top-content with limit: 10 for the same date range. Top performing content.accelerate/get-traffic-breakdown with dimension: "referrer" for the same date range. Where visitors are coming from.accelerate/list-active-experiments to see what tests and personalisation rules are currently running.If the user asked about a specific time window (e.g. "this month", "last 30 days", "yesterday"), map it to the closest date_range_preset:
1h, 4h, 12h, or 24h7d30d90dUse a summary card → tables → highlights structure. No ASCII boxes. Clean markdown.
**Site review — last 7 days**
| Metric | Value | vs. previous period |
|---|---|---|
| Visitors | 2,847 | ↑ 12% |
| Page views | 8,231 | ↑ 9% |
| Bounce rate | 68% | ↓ 3% |
| Active tests | 1 | |
(Only include the "vs. previous period" column if you have comparison data. If not, omit it — don't fabricate.)
A short table of the top 5 pages with title, views, and conversion rate. Link each title if you have the URL.
A short table of the top 3–5 referrers with percentage share of traffic. Highlight any surprising source (e.g., a spike from a single referrer, high direct-traffic percentage suggesting brand awareness).
List currently active A/B tests and personalisation rules, one sentence each. If there are none, say "No tests running right now" and note that the user can ask for test ideas.
Only show this section if a learning journal exists with at least one pattern that has status: "won" or status: "lost". If the journal is missing, unreadable, or all patterns are inconclusive/mixed, skip this section entirely.
Derive the site slug from get-site-context using the site slug derivation rule in accelerate-learn. Read ~/.config/accelerate-ai-toolkit/journal-<site-slug>.json.
Show the top 2 won patterns (highest hit rate) and the top 1 lost pattern as one-line bullets:
**What's working on your site:**
- Rewriting headlines to match search intent has won 4 of 5 tests (+23% avg improvement)
- Adding social proof near buttons has won 3 of 4 tests (+12% avg improvement)
**Not working here:**
- Adding urgency language to buttons has lost 3 of 3 tests
Keep it brief. This is a status check, not a deep dive. If the user wants more, they can run /accelerate-learn.
End with 1–3 plain-English observations, each one grounded in a number you fetched. Examples:
accelerate-diagnose.)accelerate-opportunities. That's the skill for prioritisation and operating plans; you produce the status picture.accelerate/get-post-performance with the post_id and present that focused view instead. You can also fetch accelerate/get-engagement-metrics scoped to that post for bounce rate, scroll depth, time on page.