← PostproxyCONTENT HISTORY

Update to Postproxy

Snapshot Oct 29, 2026 · 19:13 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Postproxy and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build a social media performance report from Postproxy data - what was published, how posts performed, and how followers and engagement changed over a period. Use when the user asks how their social accounts or posts are doing, wants a weekly or monthly report, or wants to compare networks or posts.",
  "included_files": [],
  "name": "performance-report",
  "skill_md_contents": "---\nname: performance-report\ndescription: Build a social media performance report from Postproxy data - what was published, how posts performed, and how followers and engagement changed over a period. Use when the user asks how their social accounts or posts are doing, wants a weekly or monthly report, or wants to compare networks or posts.\n---\n\n# Performance report\n\nProduce a short, accurate report from Postproxy data. Read-only: this skill never changes anything.\n\n## Data to gather\n\n1. `summary_get` for the period (`window`, or `from`/`to` for an explicit range, and `profile_group_id` to report on one brand). It returns posts published and failed, engagement totals, comments, reviews, and DM volume per network, with comparison counts for the previous period.\n2. `history_list` for the posts behind those numbers (raise `limit` for longer periods).\n3. `post_stats` with up to 50 post IDs to rank posts. Each post has several snapshots over time, so use the latest one per post and network.\n4. `profiles_stats` for follower and audience trends per profile. Facebook, LinkedIn, Telegram, and Google Business need a `placement_id` from `profiles_placements`.\n\n## How to read the numbers\n\n- Engagement in `summary_get` is lifetime-to-date for posts published in the window, not engagement earned during the window. Say this when comparing periods.\n- In `summary_get`, a post sent to three networks counts once in post totals and three times in `by_platform`.\n- Stats fields are each network's own metrics and aren't normalized. Compare like with like (for example, Instagram likes against Instagram likes) and don't add up different metrics across networks.\n- `engagement` is null when insights are turned off for the account. Say that instead of reporting zero.\n- Google Business stats are impressions, website clicks, calls, direction requests, and conversations. There is no follower count.\n\n## Report shape\n\n1. A headline line: posts published, the overall engagement trend, and the most important change.\n2. A per-network table with posts, key engagement metrics, and follower change.\n3. The top three posts with links and why they likely did well (format, topic, timing), and any failed posts with the error.\n4. Two or three concrete suggestions based on the data, such as what to post more of or when to schedule. Label them as suggestions.\n\nOnly report numbers returned by the tools. If data is missing for a network, say so rather than estimating.\n"
}

SHA-256 of public snapshot: cca6daf964f9ea0d41ab8b5aa1e645e5cc1a29a04c0343f78038a0a5ee723a08