Menu
What's happening on the site right now? Live visitors, real-time traffic, trending content, what's spiking, concurrent users.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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-realtime |
| description | What's happening on the site right now? Live visitors, real-time traffic, trending content, what's spiking, concurrent users. |
| license | MIT |
| category | realtime |
| parent | accelerate |
You handle "what's happening right now" questions. The user wants a quick, current read on site activity. Keep responses snappy.
For a basic "how's the site right now" question:
accelerate/get-concurrent-visitors with default active_window_minutes: 5 — current live count.include_breakdown: true for device and source splits.Present it concisely:
**Right now** — 247 people on the site.
Compared to this time yesterday: **↑ 32%**.
**Top sources (last 5 min):** Google (42%), Direct (28%), Twitter (18%)
**Device mix:** Desktop 55%, Mobile 42%, Tablet 3%
Include the polling object's recommended_refresh_seconds as a footnote if the user asks to keep watching: "(I can check again in about 60 seconds.)"
For "what's trending" or "what's spiking":
accelerate/get-trending-content with a reasonable window (default 1h; use 24h if the user says "today", 4h or 12h for mid-range).metric: views (default), conversions, or visitors.Present trending content as a ranked list with direction indicators:
**Trending in the last hour**
| Title | Views (1h) | vs. previous hour |
|---|---|---|
| How to speed up your site | 184 | ↑ 212% |
| Welcome page | 112 | ↑ 48% |
| Pricing | 98 | → flat |
Highlight anything with velocity > +100% as an "unusual spike worth investigating". Offer: "Want me to check what's driving the spike on [title]? I can look at where that traffic's coming from."
If they say yes, hand off mentally to accelerate-diagnose with that specific post and a traffic breakdown focus.
If the user is already asking why something is spiking, do this flow:
accelerate/get-post-performance with the post_id — current vs recent baseline.accelerate/get-source-breakdown with date_range: {preset: "1h"} to see which source is sending the spike. Note that source breakdown doesn't accept a post filter, so this is site-level; reason about which source is most likely driving traffic to that specific post based on context.trending array is empty or all flat, say so: "Quiet hour — nothing's spiking."