content-audit
Skill0 starsChanged 31 days agoMITView on GitHub
Audits a B2B company''s existing content across blog, newsletter, LinkedIn, YouTube and events to set a baseline
25 other projects use a version of this.
Adopted by
Most recently taken up by
- risukisu/marketing-skillstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- robritacca-dotcom/rift-dstheir own version, first seen Nov 1, 2026
- brainbytes-dev/everything-claude-marketingtheir own version, first seen Nov 1, 2026
- robritacca-dotcom/design-systemtheir own version, first seen Oct 28, 2026
- microsoft/frontier-ghcp-rvastheir own version, first seen Oct 25, 2026
Used with
Projects with it also use asset-spec, create-control-manifest and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillasset-spec
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Also in 10 projects that use this
lilangMaxSkillcreate-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Also in 10 projects that use this
- +10 more from lilangMax
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- Ootto-AI/claude-content-skills★ 417same name
- OffchainLabs/arbitrum-docs★ 252same name
- striderZA/OpenCodeGameStudios★ 118same name
- cenconq25/claude-code-app-studio★ 40same name
- dawn840705/codex-code-studios★ 17same name
- huifer/AdSense-Readiness-Benchmark★ 14same name
- brainbytes-dev/everything-claude-marketing★ 9same name
- robritacca-dotcom/rift-ds★ 9same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- content-opsSkill
- content-strategySkill
- newsletterSkill
- thought-leadershipSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use it before writing a content strategy, when taking over a content programme, or when someone asks "what are we actually publishing and …
- Very specific: line 19
Don't use it to write posts or articles, to build the strategy itself (that's /content-strategy, which reads this audit), or for a …
- Very specific: line 23
Read these first if they exist.
- Distinctive: line 30
Ask the user for:
- Distinctive: line 36
If a context file is missing, run anyway and say in the output which judgements are weaker because of it (for example, "relevance scored …
- Very specific: line 44
Find the channels: Check the site footer and navigation, then search site:domain.com blog OR newsletter OR resources and the company name …
- Distinctive: line 56
Every channel listed with its URL, status and last-active date.
- Distinctive: line 58
Every key finding links to the specific post or page it came from.
- Distinctive: line 59
No invented engagement figures or guessed intent.
- Very specific: line 72
Write to outputs/content/MMYY-content-audit.md with this shape:
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content audit
Take stock of what a company already publishes, channel by channel, so the next plan builds on real numbers instead of guesses. The output is a diagnosis: what exists, how often, on what topics, at which funnel stage, what works and what's missing.
When to use it
Use it before writing a content strategy, when taking over a content programme, or when someone asks "what are we actually publishing and is it working?".
Don't use it to write posts or articles, to build the strategy itself (that's /content-strategy, which reads this audit), or for a one-channel quick look you can answer in a paragraph.
Inputs
Read these first if they exist. Agency users: swap context/ for clients/<client>/context/.
context/icp/: who the content is for and the problems they have. Needed to judge relevance.context/positioning/andcontext/messaging/: what the company wants to be known for.context/goals/: what content is meant to deliver (pipeline, awareness, hiring).context/competitors/: optional, for a light benchmark.
Ask the user for:
- Company name and website URL (required).
- At least one content channel URL: blog or newsletter, LinkedIn company page or founder profile. Optional: YouTube, events page.
- Time range. Default to the last 6 months.
If a context file is missing, run anyway and say in the output which judgements are weaker because of it (for example, "relevance scored without an ICP file").
Tools
If you have Firecrawl or Exa, use them to list and read pages. Otherwise use web search with site: queries, or ask the user to paste URLs or exports. List pages first, keep only the ones in scope, then read those. Don't crawl a whole domain to count blog posts.
Steps
- Find the channels. Check the site footer and navigation, then search
site:domain.com blog OR newsletter OR resourcesand the company name on LinkedIn, YouTube and event platforms. Produces: a channel list with URL, active or inactive, and last-published date. - Audit the blog or newsletter. Sample the 10-15 most recent pieces. Record cadence (posts per month), topic, format, funnel stage, and quality signals: headline specificity, depth, a clear call to action, any lead magnet. Produces: a per-piece table plus a cadence figure.
- Audit LinkedIn. Pull the last 20-30 posts. Record cadence, format (text, carousel, video, image, poll), topic, and visible engagement. Read 5-10 for voice and hook patterns. Produces: the same table for LinkedIn plus voice notes.
- Audit YouTube and events, if they exist. Cadence, content types, recent view counts, production quality; for events, type, virtual or in-person, and community signals. Produces: one short section each.
- Map topics to the ICP. Group everything into topic clusters and check each against the problems in
context/icp/. Produces: a cluster table showing which ICP problems are covered, thin or missing. - Check the funnel mix. Tag each piece top (problem awareness), middle (how to solve it) or bottom (why this product). Produces: the mix as percentages per channel and overall.
- Score. Rate 1-5 on volume, consistency, quality, ICP relevance, funnel balance and cross-channel alignment, then an overall health score. Each score gets one line of evidence.
- Find what works. Name the 3-5 pieces or formats that clearly outperform the rest and say what they have in common.
- Write the recommendations. Split into quick wins (this week), strategic fixes (next 30 days) and longer bets (next quarter). Each one names the gap it closes.
What good looks like
- Every channel listed with its URL, status and last-active date.
- Numbers, not adjectives: "3.2 posts a month, mostly Tuesdays", not "posts regularly".
- Every key finding links to the specific post or page it came from.
- No invented engagement figures or guessed intent. Where data isn't visible, write "not available" and say how to get it.
- Gaps are stated in ICP terms: "nothing on [problem the ICP names]", not "needs more educational content".
- Recommendations are specific enough that someone could start one tomorrow.
Mistakes to avoid
- Judging quality by taste. Tie every score to evidence or to the ICP's problems.
- Counting only the blog. LinkedIn and the founder's profile are often where the real output is.
- Reading likes as results. Engagement shows reach, not pipeline; say which you're looking at.
- Padding the recommendations. Five that matter beat fifteen that don't.
Output
Write to outputs/content/MMYY-content-audit.md with this shape:
- Header: company, website, audit period, channels audited, date.
- Summary: three to five sentences on overall health and the biggest gap.
- Scorecard: the six dimensions plus overall, 1-5, one line of evidence each.
- Channel sections: inventory table, cadence, topics, formats, notes.
- Topic and funnel analysis: cluster table against ICP problems, funnel mix.
- What works: the outperformers and the pattern behind them.
- Recommendations: quick wins, strategic, longer bets.
- Input for the strategy: current baseline, gaps to close, voice patterns worth keeping.
- Data gaps: what you couldn't see and how to get it.
Next step: run /content-strategy, which reads this file as its baseline.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

