Update to Simplified for AI

{
  "description": "Analyze connected social accounts and translate metrics into decisions for marketers and small businesses. Use when the user asks how social performed, requests a weekly or monthly report, wants winners and losers, needs KPI or audience analysis, asks what content worked, wants account comparisons, or needs evidence-based recommendations for the next content plan.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 611
    },
    {
      "relative_path": "assets/simplified-icon-256.png",
      "size_in_bytes": 8191
    },
    {
      "relative_path": "assets/simplified-logo.png",
      "size_in_bytes": 6726
    }
  ],
  "name": "social-performance-analyst",
  "skill_md_contents": "---\nname: social-performance-analyst\ndescription: Analyze connected social accounts and translate metrics into decisions for marketers and small businesses. Use when the user asks how social performed, requests a weekly or monthly report, wants winners and losers, needs KPI or audience analysis, asks what content worked, wants account comparisons, or needs evidence-based recommendations for the next content plan.\n---\n\n# Social Performance Analyst\n\nTurn Simplified social analytics into clear signals, limitations, and next actions. This skill is read-only unless the user separately asks to create content.\n\n## Workspace and handoff\n\nBefore connected operations, use `simplified-workspace` when the client/workspace/teamspace is named or uncertain. Resolve the exact numeric teamspace and carry its `space_id` on every related account, analytics, asset, generation, draft, tag, review, and continuation call. Re-list scoped resources after switching clients; stop on access failures rather than falling back to another space. Pass the resolved context to every delegated skill.\n\n## Workflow\n\n1. Resolve the reporting period. Use the previous complete calendar month for \"last month\" and the last 30 completed calendar days ending yesterday (date_from = today minus 30 days, date_to = yesterday) for an unspecified recent period. Never send a future `date_to`. For a user-requested period through today, label today as partial. Pass a known IANA `tz` only to tools exposing it (Range and Audience); Posts and Aggregated do not expose `tz`, so disclose day-boundary limitations when material.\n2. Call `social_getSocialMediaAccounts` once, then select the relevant integer account IDs. If multiple matching accounts exist and the distinction materially affects the answer, ask which one; otherwise analyze all and label them.\n3. Call `social_getSocialMediaAnalyticsAggregated` for the KPI overview.\n4. Call `social_getSocialMediaAnalyticsRange` when trends, spikes, or timing matter. Choose valid metrics for the account type from `../simplified-social/references/analytics.md`.\n5. Call `social_getSocialMediaAnalyticsPosts` with `per_page: 100` to identify content winners and losers. Paginate until complete when the user requests a comprehensive report.\n6. Call `social_getSocialMediaAnalyticsAudience` only when demographics or follower origin is relevant; partial or empty results are normal.\n7. Compare `value` with `prevValue`. Report absolute values and direction; avoid percentage change when the prior value is zero.\n8. Synthesize the evidence as signal, likely interpretation, limitation, and recommended action. Do not claim causation from correlation.\n\n## Analysis Standard\n\n- Separate reach or impressions, engagement, audience growth, and publishing volume.\n- Normalize account comparisons where possible; raw totals across different networks are not directly equivalent.\n- Connect post-level observations to concrete attributes such as topic, format, hook, CTA, or timing only when the returned data supports it.\n- Note sparse data, missing metrics, platform attribution windows, and incomplete audience fields.\n- Recommend no more than three prioritized actions and attach each to an observed signal.\n- Suggest a measurable next experiment, including what to change and which metric will determine success.\n\n## Failure Handling\n\n- On `401`, stop and ask the user to authorize the Simplified connector.\n- On an empty account list, explain that social accounts must be connected in Simplified.\n- If a metric is unsupported or silently omitted, report that limitation rather than treating it as zero.\n\n## Output\n\nLead with a concise performance verdict. Follow with KPI changes, trend evidence, top and weak content, audience findings when relevant, and three prioritized next actions. Include the exact reporting period and account names.\n"
}