Why is this underperforming? Why is bounce rate high? Why did conversions drop? What's wrong with this page? Which page needs the most work? Root-cause diagnosis for content problems.
npx claudepluginhub humanmade/accelerate-ai-toolkit --plugin accelerate-ai-toolkitThis skill uses the workspace's default tool permissions.
You are helping a marketer figure out why something isn't working so they can decide what to fix first. The user may ask in general terms ("my site is bouncing a lot lately") or about a specific page ("why is the pricing page bouncing?"). Handle both.
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 helping a marketer figure out why something isn't working so they can decide what to fix first. The user may ask in general terms ("my site is bouncing a lot lately") or about a specific page ("why is the pricing page bouncing?"). Handle both.
accelerate/get-top-content with a reasonable window (default 30d) and limit: 20 to see what's popular.accelerate/get-post-performance with each post_id in parallel to get detailed metrics.accelerate/get-engagement-metrics with entity_type: "site" to get site-wide bounce rate, time on page, scroll depth, recirculation rate.accelerate/get-content-diff on the top 3 suspects, comparing the current period to the previous one, to see whether any of them recently got worse.accelerate/search-content with the user's description if they didn't give you a post_id. Pick the most likely match and confirm with the user.accelerate/get-post-performance with the post_id for that content.accelerate/get-engagement-metrics with entity_type: "post" and the same post_id to get detailed engagement signals for that specific page.accelerate/get-traffic-breakdown with dimension: "referrer" to understand who's landing on this page.accelerate/get-landing-pages — the specific page may show up with useful context.You're pattern-matching against these common issues:
| Pattern in the data | Likely cause | What to suggest |
|---|---|---|
| High bounce rate + visitors mostly from Google | Headline doesn't match search intent | Rewrite the headline to align with what visitors were searching for |
| Low time on page + high scroll p100 | Thin content, visitors reach the end and bounce | Add depth, expand sections, offer a related read |
| Low time on page + low scroll depth | Visitors aren't engaging at all — either wrong audience or bad first impression | Check the hero above the fold. Rewrite. |
| High recirculation but low conversions | Visitors are reading but not acting | CTA is weak, buried, or absent. Move it above the fold, strengthen copy. |
| Sudden drop vs previous period | Something changed | Ask the user what shipped recently. Compare top referrers between the two periods. |
| Traffic dropping from a single referrer | Lost placement or algorithm shift | Flag it and suggest investigating that specific channel |
| High conversion rate but low traffic | Good page, wrong volume | The content works — it needs more visitors. Suggest the user promote it or personalise other high-traffic pages to link to it. |
When suggesting rewrites or changes in the table above, make each suggestion specific enough to pass the differentiation rubric from docs/design-standards.md if it were turned into an A/B test variant. "Rewrite the headline" is too vague. "Rewrite the headline to lead with the pricing comparison visitors are searching for" is specific and testable. Ground every suggestion in a data point from the fetched analytics.
Start with the single biggest problem you found, then up to two smaller ones.
## What needs the most work
### 🔴 Homepage — high bounce, high stakes
The homepage gets 1,204 visitors a week and 78% of them leave without clicking anything. That's your biggest lever.
- **Why I think so:** 45% of these visitors come from Google, mostly for searches like "<query>". The current hero says something different, so people don't feel they've landed in the right place.
- **What to do:** Rewrite the hero headline to match the search intent.
- **What to measure:** bounce rate on the homepage, dropping toward ~60%.
- **Want me to set up an A/B test for this?**
### 🟡 Pricing page — drop vs last month
Pricing page conversions are down 22% vs the previous 30 days. Nothing else on the site changed, so this is worth checking directly.
...
accelerate-test if the user wants to act on a finding by running an A/B test.