Content audit
Audit an existing social media account and its content — the retrospective reality-check of what's working and what isn't. Use when someone wants to "audit my content/account," "what's working and what isn't," "clean up my profile/feed," "I post a lot but it's not working," or to triage an existing account before replanning. Produces a keep/kill/refresh triage, maps pillar coverage, catches voice drift, and fixes profile fundamentals — then a quick-wins-vs-long-term roadmap. Uses the AUDIT framework. Reads brand-profile + content-pillars + social-strategy (the plan) and analytics-and-reporting (the data) first. It reads native analytics (WoopSocial has none), scores on signal not vanity, recommends rather than auto-deletes, and never fabricates. Feeds content-recycling, content-pillars, profile-optimization, voice-builder, and social-strategy. Distinct from analytics-and-reporting (ongoing measurement) and competitor-analysis (rivals).From its SKILL.md
npx -y skills add social-media-skills/skills --skill content-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.7 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
content-audit
The retrospective bridge — read how an existing account has performed and turn it into a keep/kill/
refresh roadmap that feeds the forward plan. It reads (via analytics-and-reporting) and
recommends; the human and other skills act.
The POV: activity isn't progress
Plenty of accounts look busy — daily reels, carousels, likes trickling in, followers inching up — while nothing actually moves. A content audit finds the signal under the busy-ness: what gets saved and shared (not just liked), which pillars are starved or bloated, where the voice has drifted (or where your winners say it should evolve), and which profile fundamentals quietly leak followers. Strategy is forward-looking; the audit is the retrospective reality-check that informs it.
Read these first
- brand-profile + voice-builder — the voice/brand standard to audit against.
- content-pillars + social-strategy — the intended plan (the audit checks execution of it).
- analytics-and-reporting — the performance data source (native analytics; WoopSocial has none).
The framework: AUDIT
(Depth: references/the-audit-framework.md.)
- A — Assemble the inventory: ~90 days of output by platform/format/pillar/time + native metrics; pull the plan you're auditing against.
- U — Uncover the signal: score on saves/shares/replies + the goal-mapped KPI (not vanity); surface top/bottom performers + patterns by format/time/pillar.
- D — Diagnose pillars, voice & profile: pillar whitespace (→ content-pillars); voice drift both ways (→ voice-builder); profile fundamentals + cadence (→ profile-optimization).
- I — Iterate: keep / kill / refresh: scale winners (→ content-recycling), cut chronic/off-brand/ non-native, refresh good-but-dated. Refresh before kill; human approves kills.
- T — Turn into a roadmap: strengths/weaknesses/opportunities; quick wins vs long-term; owners + timelines; hand off. No spreadsheet graveyard.
The method (verify specifics quarterly)
Audit = retrospective (vs forward strategy); signal-over-vanity; keep/kill/refresh; pillar whitespace;
voice drift both ways; profile fundamentals; ~90-day window; quarterly deep + monthly light; run after
major changes: references/content-audit-2026-reality.md. Triage rules, scorecard + worked examples:
references/triage-and-recipes.md.
Honest scope (never violate)
- Retrospective, not strategy — triages the past;
social-strategyplans the future. - Reads native analytics (WoopSocial has none) via
analytics-and-reporting; interprets numbers the user provides — never fabricates a metric or a coverage map. - Signal not vanity — low likes is not a kill criterion.
- Recommend, don't auto-act — never auto-delete (a human approves kills; deleting can lose evergreen/SEO value + history); refresh before kill; some profile edits are in-app/human.
- Thin data → structural audit only (profile/pillars/voice/cadence + baseline); revisit performance
triage at ~90 days.
(Scope, bridge role + connections:
references/scope-and-connections.md.)
Distinct from its siblings (route correctly)
content-audit (this) = periodic retrospective triage of YOUR account · analytics-and-reporting = ongoing measurement (the data source) · competitor-analysis = rivals' public side · social-strategy = the forward plan this informs · content-recycling = scales/refreshes the winners this surfaces · profile-optimization = executes the profile fixes this flags.
Where this connects
Reads first: brand-profile, voice-builder, content-pillars, social-strategy, analytics-and-reporting. Hands findings to: content-recycling, content-pillars, profile-optimization, voice-builder, social-strategy, experimentation. Benchmark context: competitor-analysis, goals-and-kpis. Per-platform format/native expectations: the per-platform *-growth skills. No publishing/tool surface — a diagnostic + planning skill.
Definition of done
A ~90-day inventory scored on signal (not vanity) from native analytics the user provided (nothing fabricated); pillar whitespace, voice drift (both ways), profile fundamentals, and cadence diagnosed; a keep/kill/refresh triage (refresh before kill; kills human-approved, none auto-deleted); a strengths/ weaknesses/opportunities roadmap split into quick wins vs long-term with owners + timelines, handed to content-recycling/content-pillars/profile-optimization/voice-builder/social-strategy; thin-data accounts get a structural audit + baseline instead; correctly distinguished from analytics-and-reporting, competitor-analysis, and social-strategy.
What ships with it: 5 files
17.3 KB alongside SKILL.md
evals/
- evals.json5.7 KB
references/
- content-audit-2026-reality.md3.0 KB
- scope-and-connections.md2.8 KB
- the-audit-framework.md2.5 KB
- triage-and-recipes.md3.2 KB
Gives 0 of the 12 instructions most audit compliance skills give in ~1.1k tokens
Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06
- Read product marketing context before asking questionsin 29 of 960, across 11 files
- Rank findings by severityin 29 of 960, across 22 files
- Generate audit reportin 22 of 960
- Run the audit scriptin 20 of 960, across 19 files
- Generate a prioritized action plan reportin 19 of 960, across 11 files
- Ensure one H1 per pagein 15 of 960, across 5 files
- Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
- Verify alt text on all imagesin 12 of 960, across 3 files
- Determine the audit scope before startingin 12 of 960, across 4 files
- Verify important pages allowed in robots.txtin 11 of 960, across 2 files
- Detect business type from homepage signalsin 11 of 960, across 7 files
- Delegate specialized tasks to subagentsin 11 of 960, across 7 files
Said here and by no other author read
- read brand profile and strategy first
- assemble ninety day content inventory
- score on saves and shares
- diagnose pillars voice and profile
- create keep kill refresh triage
- produce quick wins versus long term roadmap
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.