Social analytics report skill

Social analytics report — The content growth factory (from the Ootto-AI/claude-content-skills README)

Illustration · not a resultFrom the Ootto-AI/claude-content-skills README — shows the whole collection, not only this skill.source ↗

Use when you need to turn supplied social performance data into a decision about what to keep, test, change, or stop.

by Ootto-AI·MIT license·★ 139 Stars on the repo·GitHub ↗

Use now
Social analytics report — The content growth factory (from the Ootto-AI/claude-content-skills README)

Illustration · not a resultFrom the Ootto-AI/claude-content-skills README — shows the whole collection, not only this skill.view on GitHub

Files of Social analytics report

Ootto-AI/main1 file shown
SKILL.md
Show the full text46 lines

Social Analytics Report

Make an honest operational report from the metrics the team actually has, with context, uncertainty, and a next decision.

1. Establish what the data can answer

Ask for the date range, channels, posts or campaigns, metric definitions, collection method, target or baseline, and any known changes in spend, audience, format, or distribution. If definitions differ across channels, do not silently compare the raw totals.

2. Check the data before interpreting it

Identify missing rows, partial reporting windows, duplicate posts, changed tracking, or metrics collected at different ages. Label the report's data boundary. Separate direct observations from hypotheses about why something happened.

3. Read outcomes against the intended job

Group results by the job each post or channel was assigned: awareness, education, discussion, qualified traffic, conversion assistance, or creator partnership learning. Compare like with like. Look for repeatable patterns in message, format, audience context, and distribution rather than choosing one winner by impressions.

4. Recommend the next smallest test

Return a decision table: observation, confidence, likely explanation, action, owner, and evidence needed next. State what not to conclude. Recommend a bounded test that preserves the campaign claim and measurement method so the next report can actually compare it.

Hard rules

  • Never claim causation from correlation or a single post.
  • Do not compare unlike metrics, date windows, paid and organic activity, or posts at different maturity without saying so.
  • Keep raw data, calculated rates, and interpretation distinguishable.
  • Do not hide low-performing or incomplete data to make a narrative look cleaner.
  • Never fabricate access to native analytics, ad accounts, or conversion systems.

Failure modes

Failure Do this instead
A high-impression post is declared successful Judge it against the job and downstream evidence it was intended to influence.
A report lists metrics but makes no decision End with one keep, one test, one change, and their owners.
Platform totals are compared as if identical Normalize the question or report each channel separately.
The team changes five things at once Choose the smallest observable test and hold other conditions steady where possible.

Where it sits

Use campaign-brief and utm-campaign-plan before publishing so the report has a decision and attribution plan. Use this skill during a campaign for operating reviews. Use launch-retrospective after the reporting window to combine results, qualitative evidence, and process lessons.

1---
2name: social-analytics-report
3description: Use when you need to turn supplied social performance data into a decision about what to keep, test, change, or stop. Trigger phrases include "report on this campaign", "what worked on social?", "analyse these post results", "make a weekly social report", and "what should we do next from these metrics?". Do not use this to invent data access, claim causation from a dashboard, or replace a campaign brief; use campaign-brief to define success before launch and launch-retrospective for the broader after-action review.
4---
5 
6# Social Analytics Report
7 
8Make an honest operational report from the metrics the team actually has, with context, uncertainty, and a next decision.
9 
10## 1. Establish what the data can answer
11 
12Ask for the date range, channels, posts or campaigns, metric definitions, collection method, target or baseline, and any known changes in spend, audience, format, or distribution. If definitions differ across channels, do not silently compare the raw totals.
13 
14## 2. Check the data before interpreting it
15 
16Identify missing rows, partial reporting windows, duplicate posts, changed tracking, or metrics collected at different ages. Label the report's data boundary. Separate direct observations from hypotheses about why something happened.
17 
18## 3. Read outcomes against the intended job
19 
20Group results by the job each post or channel was assigned: awareness, education, discussion, qualified traffic, conversion assistance, or creator partnership learning. Compare like with like. Look for repeatable patterns in message, format, audience context, and distribution rather than choosing one winner by impressions.
21 
22## 4. Recommend the next smallest test
23 
24Return a decision table: observation, confidence, likely explanation, action, owner, and evidence needed next. State what not to conclude. Recommend a bounded test that preserves the campaign claim and measurement method so the next report can actually compare it.
25 
26## Hard rules
27 
28- Never claim causation from correlation or a single post.
29- Do not compare unlike metrics, date windows, paid and organic activity, or posts at different maturity without saying so.
30- Keep raw data, calculated rates, and interpretation distinguishable.
31- Do not hide low-performing or incomplete data to make a narrative look cleaner.
32- Never fabricate access to native analytics, ad accounts, or conversion systems.
33 
34## Failure modes
35 
36| Failure | Do this instead |
37| --- | --- |
38| A high-impression post is declared successful | Judge it against the job and downstream evidence it was intended to influence. |
39| A report lists metrics but makes no decision | End with one keep, one test, one change, and their owners. |
40| Platform totals are compared as if identical | Normalize the question or report each channel separately. |
41| The team changes five things at once | Choose the smallest observable test and hold other conditions steady where possible. |
42 
43## Where it sits
44 
45Use campaign-brief and utm-campaign-plan before publishing so the report has a decision and attribution plan. Use this skill during a campaign for operating reviews. Use launch-retrospective after the reporting window to combine results, qualitative evidence, and process lessons.
46 

Discussion

Alternatives

/ar:ar-status — Experiment DashboardShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.Data & AI · MITAnalytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Creator · MITEarnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly. · MITBenchmark checklistVet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.Data & AI · MIT