{"id":79729,"plugin_id":"plugin_asdk_app_6ac07a221a0881918b403530f3177912","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:12:54.561Z","digest":"6f91bd8c6c210281c60804f0f8e47697d91588db1674a4cc4b720e649523771e","against":null,"payload":{"description":"Build a social media analytics report from PostZen — post performance, follower growth, daily metrics, and best times to post across connected accounts. Use when the user asks how their posts or accounts are performing.","included_files":[],"name":"analytics","skill_md_contents":"---\nname: analytics\ndescription: Build a social media analytics report from PostZen — post performance, follower growth, daily metrics, and best times to post across connected accounts. Use when the user asks how their posts or accounts are performing.\n---\n\n# PostZen analytics report\n\nProduce a readable performance summary for the user's connected social accounts. The user's request follows: \"$ARGUMENTS\"\n\n## Workflow\n\n1. **Scope it.** Call `listAccounts` to see connected accounts. If the user didn't specify platforms or a time range, default to all accounts over the last 7 days and say so in the report.\n2. **Pull the data** (parallel calls where independent):\n   - `getAnalytics` — per-post engagement metrics for the period.\n   - `getDailyMetrics` — day-by-day account-level metrics (impressions, engagement).\n   - `getFollowerStats` — follower counts and growth.\n   - `listPosts` — recently published posts, to tie metrics back to actual content.\n   - `syncExternalPosts` stores imported records and is a write. Use it only when the user explicitly asks to synchronize external posts; ordinary analytics summaries use stored data.\n3. **Synthesize, don't dump.** Lead with the headline (best-performing post, follower trend direction, notable spikes or drops). Then a short per-platform breakdown. Quote actual numbers with their period. Call out anything actionable — e.g. a content type that consistently outperforms, or a platform going stale.\n4. **Close with timing guidance** if relevant: `getBestTimeToPost` gives data-driven posting-time suggestions per account; mention the top slots.\n\n## Notes\n\n- Some platforms gate analytics behind extra permission scopes; if a tool returns an authorization/scope error for one account, note it in the report (\"analytics not enabled for this account — reconnect it in the PostZen dashboard to grant analytics access\") and continue with the rest rather than failing the whole report.\n- The analytics retrieval tools are read-only. Empty or unavailable history is not zero; report gaps without inventing metrics. Do not silently synchronize or modify account settings.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}