Menu
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.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Design a new on-brand version of a block or a fresh section — "make me a variant of the hero", "design a new pricing section", "compose an on-brand version", "give me a bolder hero". Produces ready-to-use content; offers to put it in a test but never forces one. NOT for running or tracking an A/B test (use accelerate-test) or a multi-round optimization loop (use accelerate-evolve).
Improve a block over multiple rounds — "keep improving my hero", "run an optimization loop on the homepage", "autopilot the waitlist block", "evolve this section until it stops getting better". Each round fields bold new challengers, tests them, harvests the winner, and builds the next round on it. NOT for a single A/B test (use accelerate-test) or a one-off variant (use accelerate-design).
Connect the toolkit to your WordPress site. Set up credentials, generate an application password. Also triggered when the site connection is missing.
Improve a landing page. Make it convert better. What should I change on my homepage? Optimise a specific page with data-grounded recommendations and A/B test hand-off. Recommends WHAT to change across a page; NOT for composing a specific new version of one block — use accelerate-design for that.
Any question about a WordPress site — analytics, traffic, bounce rate, conversions, A/B tests, landing pages, audiences, personalization, campaigns, content performance, what to improve, how the site is doing. Routes to the right workflow.
A/B test lifecycle — plan, create, monitor, review, or end a test. What should I test? Set up a split test. How is my test doing? Is there a winner? Stop or declare a winner. NOT for composing a single on-brand variant without a test (use accelerate-design) or running a multi-round optimization loop (use accelerate-evolve).
| name | accelerate-review |
| description | 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. |
| license | MIT |
| category | review |
| parent | accelerate |
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 date_range_preset: "7d" (default; adjust if the user named a different window). This gives you total views, visitors, bounce rate, time series.accelerate/get-top-content with limit: 10 and date_range: {preset: "7d"} (match the window from step 1). Top performing content.accelerate/get-traffic-breakdown with dimension: "referrer" and date_range: {preset: "7d"} (match the window from step 1). 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"), use the matching preset for date_range_preset on get-performance-summary and the equivalent date_range: {preset: "..."} on the other calls:
1h, 4h, 12h, or 24h7d30d90dFor windows that don't match a preset (e.g. "last 45 days"), use date_range: {start: "<ISO>", end: "<ISO>"} on the data calls and omit date_range_preset on get-performance-summary.
Use 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 key from get-site-context using the site key derivation rule in accelerate-learn. Read ~/.config/accelerate-ai-toolkit/sites/<key>/journal.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.