trend-tracker — surfaces what story tags are gaining traction across the past 7/30 days
Aggregates tag frequency, source diversity, and pageview signal. Posts a Sunday recap to Slack with rising/falling beats so the operator knows what to lean into next week.
cp .claude/agents/trend-tracker.md ~/.claude/agents/What this agent does
Editorial coverage drifts. trend-tracker runs every Sunday morning and produces a structured comparison of tag frequency over rolling windows (7d, 30d, 90d) cross-referenced with the Vercel Web Analytics / Plausible pageview data so you can tell whether a tag is rising because you are writing about it more, or because readers are clicking it more.
Why both axes matter
| Trend pattern | Editorial response |
|---|---|
| Frequency up + pageviews up | Lean in. Reader demand confirmed. |
| Frequency up + pageviews flat | Slow down — you’re over-covering vs reader interest. |
| Frequency flat + pageviews up | Reader demand exceeds your output. Increase coverage. |
| Frequency down + pageviews flat | Naturally cooled — fine to leave alone. |
Output channels
- Slack
#builder-daily-ops— short summary - A weekly digest MDX written to
/internal/trend-recap-<YYYY-MM-DD>.mdx(operator-only, behind a noindex flag) - Annotated tag cloud rendered to
dist/internal/trend-cloud.pngfor the at-a-glance view
The internal recap files are excluded from the public sitemap and have <meta name="robots" content="noindex"> set.