{"id":94812,"plugin_id":"plugin_asdk_app_6a1574e90fc081918d40eca0fac88821","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-13T12:08:21.962Z","digest":"272c523e5ab10bf9ab72932462b8551717e580ee40fdf4ab4e530206daa41dd3","against":null,"payload":{"description":"Turn one Planable workspace's analytics into a client-ready report with key numbers, platforms, top posts and takeaways. Use when the user asks for a monthly report, a performance summary, or how a client's social media did last month.","included_files":[],"name":"monthly-performance-summary","skill_md_contents":"---\nname: monthly-performance-summary\ndescription: \"Turn one Planable workspace's analytics into a client-ready report with key numbers, platforms, top posts and takeaways. Use when the user asks for a monthly report, a performance summary, or how a client's social media did last month.\"\n---\n\n# Monthly performance report\n\nA client-ready summary of one workspace's social performance for a period.\n\n## 1. Scope\n\n- Workspace. Ask if it is not clear.\n- Period. Default: the previous calendar month. Point it out when the period is a partial month.\n- Pages. Default: all pages in the workspace.\n\nAnalytics needs the analytics add-on (hasAnalytics from get_workspace_details) and the user's analytics permission. If a tool rejects for that reason, say so plainly and stop.\n\n## 2. Fetch\n\n- list_pages for the page ids.\n- get_page_metrics for the numbers per page (audience, posts, impressions, engagement, engagement rate and the platform's own metrics).\n- get_page_metrics_summary for the totals.\n- get_post_metrics_summary for the post totals in the period.\n- get_post_metrics for the top posts. Fetch enough to rank the top 5 by engagement.\n- For the change against the period before, repeat the two summary calls for the previous period of the same length.\n\nIf metricsFetchedAt is old, offer refresh_page_metrics and refresh_post_metrics. They only queue a sync, and newer data lands after a few minutes, so offer to continue with the stored numbers.\n\n## 3. Report\n\n1. Key numbers: audience, impressions, engagement, engagement rate and posts published, each with the change against the previous period when you have it.\n2. By platform: one line per page or platform.\n3. Top 5 posts: page, a short preview and the number that put it there.\n4. What worked: 2 or 3 specific points from the data.\n5. What to watch: 1 or 2 specific points.\n6. Notes: pages without data (unsupportedPages), how fresh the data is (metricsFetchedAt), and that X figures cover only the posts published through Planable.\n\nRound the numbers (12K, 4.2%) and use plain language a client understands. If the month was quiet, say so, and never invent a trend.\nIf you can create documents or files here, offer a shareable version of the report. Otherwise keep it in the chat.\nIf the user uploads an analytics export instead, build the same report from the file.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}