antwork-analyticslisted
Install: claude install-skill polynode-co/antwork-skills
# Reporting on performance in Antwork
Antwork's analytics tools return **BigQuery-style tabular data** — `{ schema: { fields }, rows, rowCount }` — not charts. Your job is to pull the right table, then synthesize it into a decision: what's working, on which platform, and what to make more of. Numbers without a recommendation are not a report.
## 1. Pick the right query — don't pull everything
| Question | Tool | Notes |
|---|---|---|
| "What are my best posts?" | `get_performance(limit, days?, platform?)` | Lifetime totals per published post plus `platformTotals`. Best for **rankings**. `limit` 1–50 (default 30), `days` 1–365 (default 30). |
| "How is engagement trending?" | `get_engagement_history(days)` | Daily rows per platform + an "all" row per date, plus `platformTotals`/`rangeTotals`. Best for **trends over time**. 1–365 days, default 30. |
| "Am I gaining followers?" | `get_engagement_history(days)` → its `followers` table | One row per (date, account): `followers`, `dailyChange`, `approximate`, `unavailableReason`. `list_social_accounts` gives each account's latest `followers` (`count`, `asOf`, 30-day `change` since `changeSince`). |
| "How did *this* post grow?" | `get_engagement_history(post_id=..., days?)` | Per-day metrics for one post, both cumulative and daily-delta. Best for **single-post lifecycle**. Omit `days` for full history. |
| "Why is this one post's number blank?" | `get_post(post_id)` | A published post's `metricCells`: every metric with its `stat