The Social Dashboard Built For People Who Don't Run Ads

Sprout and Hootsuite were built for ad agencies. This one was not. It is a Claude skill that tracks the four numbers that move organic growth, adds a weekly scorecard for every client, and runs off a single spreadsheet you probably already keep. First build takes about ten minutes.

The Problem: Every Tool Leads With The Wrong Numbers

You grow on content, not on ad spend. So why does every social tool you pay for open with cost per result, cost per acquisition, and paid reach?

Those numbers say nothing about your business when you never put money behind a post. Worse, they crowd out the four you actually came to check: views, engagements, content published, followers. You open the dashboard, scroll past the ad panels, and hunt for the one chart that matters.

It gets heavier when you run content for clients. Now you have one tool for analytics, another for scheduling, a doc for the plan, a chat thread for the client, and a spreadsheet for the scorecard. Five places to see one client, and none of them talk to each other. Every Monday you rebuild the whole picture by hand before the meeting.

This skill folds that into one screen. Two things live on it: the work that needs doing, and the results of the work already done. That is the whole review.

What This Skill Is

It is a single file you hand to Claude. You tell it your platforms, your client list, and where your numbers live. It reads that, rolls up the four core metrics per client and per platform, and builds one dashboard you open in a browser.

The analytics half puts the four numbers up top, with a chart behind each one over time. You filter by platform, by client, by date range, and switch between daily and cumulative in a click. No paid metrics, because you asked for none.

The operating-system half is the part the paid tools skip. For every client it writes a weekly scorecard: the leading metrics to hit this week, the current priorities, and the to-dos that came out of the last meeting. That layer is what keeps a retainer alive. Most agencies sell content. The ones that keep clients sell the rhythm that produces it.

Copy The Skill

Paste this whole file into a new Claude chat and say "follow this skill." If you run Claude Code, drop it into a skills/organic-social-ops-dashboard/ folder instead. Fill in the three fields at the top before your first run.

---
name: organic-social-ops-dashboard
description: Turn your scattered organic-social numbers and client ops into one Claude-built dashboard. Tracks the 4 numbers that actually matter (views, engagements, content published, followers) filterable by platform, client, and date, and adds an operating-system layer with per-client weekly scorecards, priorities, and to-dos. Use it when you run organic content for yourself or for clients and you are tired of bouncing between six tools to see one client.
---

# Organic Social Ops Dashboard

> What this does (in one line): You point Claude at your social accounts and your client list, and it builds one dashboard that shows the 4 numbers that actually matter plus a weekly scorecard, priorities, and to-dos for every client.

## Before you start: fill these in

These are the only things you need to provide. Everything else is automatic.

| Fill in | What it is | Example |
|---|---|---|
| `PLATFORMS` | The social platforms you publish on | Instagram, TikTok, YouTube, LinkedIn |
| `CLIENTS` | The list of clients (or just "me" if it is your own account) | Acme Co, Bright Studio, me |
| `DATA_SOURCE` | Where the numbers come from. Either a CSV/Google Sheet you export from each platform, or read-only API access if you have it | a Google Sheet called "social-stats" with one row per post |

> If you do not have one of these yet, the skill tells you exactly where to get it the first time you run it. The simplest start is a Google Sheet you paste exports into; you can wire up live APIs later.

## What you need installed

- Claude Code or Claude Desktop.
- A place to keep your numbers. A single Google Sheet (or a folder of CSV exports) is enough to start.
- Optional: read-only access to your platform analytics if you want the numbers pulled automatically instead of pasted.

## How to use it

1. Put this `SKILL.md` where your agent looks for skills (in Claude Code: a `skills/organic-social-ops-dashboard/` folder, or just paste this whole file into a new chat and say "follow this skill").
2. Fill in the fields above.
3. Then tell your agent: "Build my organic social ops dashboard from DATA_SOURCE for these clients and platforms."

## The workflow (what the agent does)

1. Read `DATA_SOURCE`. If it is empty or missing, tell the user exactly what columns to put in it: date, platform, client, post link, views, engagements. One row per post.
2. For each platform in `PLATFORMS` and each client in `CLIENTS`, roll up the 4 core numbers only: total views, total engagements, content published (count of posts), and followers (latest value). Ignore paid-ad metrics, CPAs, and anything that does not move organic growth.
3. Build the analytics view: the 4 numbers up top, then a simple chart for each one over time (views over time, engagements over time, content vs performance which is average views per post, follower growth). Make it filterable by platform, by client, and by date range, and let the user switch daily vs cumulative.
4. Build the operating-system layer. For each client, generate a weekly scorecard with: the leading metrics they need to hit this week, their current priorities, and the to-dos that came out of the last meeting. Keep it to one screen: the work that needs doing, and the results of the work already done.
5. Output the dashboard as a single self-contained HTML file (open it in any browser) or a Markdown report, whichever the user asks for. Refresh it any time by re-running with updated data.
6. Tell the user how to keep it current: paste this week's exports into `DATA_SOURCE`, then say "refresh the dashboard."

## If something goes wrong

- The numbers look wrong or zero: check that `DATA_SOURCE` has one row per post with the six columns named above. Most issues are a missing or misnamed column.
- You only see one platform or one client: the filter is active. Ask the agent to "show all platforms" or "show all clients" to clear it.
- You do not have follower history: that is fine. Enter the latest follower count per platform and the follower-growth chart starts filling in from this week forward.
- It feels too complex: tell the agent "keep it to the 4 numbers and one scorecard per client." Simpler is the point.

How To Use It

Fill in PLATFORMS, CLIENTS, and DATA_SOURCE at the top. The easiest data source is one Google Sheet with a row per post and six columns: date, platform, client, post link, views, engagements. Then tell Claude, "Build my organic social ops dashboard from DATA_SOURCE for these clients and platforms." Each week after that, paste in the new exports and say "refresh the dashboard."

What You Get Back

Five things land on the page. Here is what each one is for.

1. The four numbers, per client and per platform. Views, engagements, content published, followers. Nothing about paid reach or cost per result, because you never asked for it.

2. A chart behind every number. Views over time, engagements over time, average views per post, follower growth. Filter to one platform or one client when you want to look at it alone.

3. A weekly scorecard for each client. The leading metrics they need to hit, laid out before the meeting instead of scrambled together during it.

4. Priorities and to-dos in one place. What matters this quarter, and what came out of the last call, sitting next to the numbers they affect.

5. One screen per client. The work that needs doing on one side, the results already shipped on the other. Nothing between them to scroll past.

Honest: What It Does Not Do

This is not a scheduler. It reads your numbers and reports them. It does not post for you, so keep whatever you already use to publish.

It is only as good as the sheet you feed it. One row per post, six columns, named correctly. Miss a column and the numbers come back wrong, and the fix is almost always a renamed header. If a client goes missing, check whether a filter is still switched on.

Follower history is the one thing you cannot backfill. If you have never tracked it, the growth chart starts flat and fills in from this week forward. Enter the latest count per platform and let it build.

If the whole thing starts to feel heavy, tell Claude to keep it to the four numbers and one scorecard per client. Simpler was the point of building your own in the first place.

If You Only Do One Thing

Build the analytics half first. Skip the client scorecards, skip the filters, skip the live APIs. Put one week of posts in a sheet with the six columns, then ask Claude for the four numbers and their charts. That is ten minutes of work. If the picture reads clearer than the tool you pay for, add the operating-system layer next week. If it does not, you are out ten minutes and one spreadsheet.