instagram-audit
Skill1 starsChanged 22 days agoMITView on GitHub
Monthly check of what is working on Instagram for the active business, from the user's own Insights export: rates by format and theme (not raw totals), top and bottom posts and why, whether the account reaches new people and moves them to act, then keep 3, stop 3, try 3 tied to the business's goals, and a scorecard to beat next month. Says plainly when there is too little data. Use it when the user says "audit my Instagram", "is Instagram working for us", "what's working on my IG", "monthly Instagram review", "why is my reach down", "here's my Insights export", or before planning next month.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- proyecto26/instagram-ai-plugintheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- proyecto26/instagram-ai-plugin★ 1same name
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 repository13 other files it gives its agents.
- founder-contextSkill
- generate-imagesSkill
- humanizeSkill
- instagram-carouselSkill
- instagram-commentSkill
- instagram-dmSkill
- instagram-planSkill
- instagram-profileSkill
- instagram-replySkill
- instagram-repurposeSkill
- instagram-storySkill
- talking-head-cardsSkill
- transcribeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Ask for one of these, in this order of preference:
- Very specific: line 36
If the user has no numbers at all, do not invent any.
- Distinctive: line 70
No made-up benchmarks: Do not say "a good save rate is 2 percent".
- Distinctive: line 89
Every number in the scorecard comes from the tool's output or the user.
- Very specific: line 125
Keep the wording plain; run it through references/before-you-show.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
instagram-audit
Most founders look at follower count and likes and guess. Both mislead. A post can get many likes from people who already follow and never buy. This audit asks two questions instead: are we reaching new people, and are those people doing something (saving, sending, visiting the profile, messaging, buying)?
It reads numbers the user exports. It never scrapes, logs in, or guesses numbers.
1. Get the numbers
Ask for one of these, in this order of preference:
- The Insights export from Meta Business Suite (Insights, then Content, then Export) as CSV, for the last 30 to 90 days. Works for business and creator accounts.
- A pasted table: date, format, reach, likes, comments, shares, saves, follows, profile visits. Whatever the user has.
- Screenshots of Insights: read the numbers out, and say which ones you could not read.
Also read log.md and old plan.md files for the theme of each post, and the business
file for goals (references/business-files.md). An audit without goals can only say what
is popular, not what is working.
If the user has no numbers at all, do not invent any. Offer a review you can do now: the
profile (/instagram-profile) and the last few captions they paste. Then explain how to
export Insights for next month.
2. Run the numbers
python3 scripts/insights.py export.csv --log ~/.founder/social/instagram/<slug>/log.mdFor each post it works out shares plus saves per 100 people reached. It groups posts by format and theme, lists the top and bottom posts, and flags a small sample (under 8 posts). It also says which columns the export did not have.
Why shares and saves per reach? People send and save a post when it is worth something to them. Dividing by reach makes a small post and a big post comparable.
3. Read it, honestly
Report only what the numbers support:
- Reaching new people? Reach compared with follower count, and which formats reach furthest. If the export shows followers vs non-followers, use it.
- Worth something? Shares plus saves per 100 reached, by format and theme. Which themes people keep.
- Moving people? Profile visits, follows, link taps, DMs. And, from the user, what matters most: seats sold, trial signups, preorders. Ask for those if not given.
- Top 3 and bottom 3 posts, with a plain guess at why. Label it a guess: "likely the hook", not "because of the hook".
Rules:
- Small samples are hunches. With under 8 posts, or one post far ahead of the rest, say so and keep the advice light.
- No made-up benchmarks. Do not say "a good save rate is 2 percent". Compare the account with itself: this month vs last, this format vs that one. If the user wants an industry number, it needs a source with a link and a date.
- Raw totals are context, not findings. A 10x reach month with no new follows is a finding. A 10x reach month alone is not.
- Reach drops have dull causes first: fewer posts, fewer Reels, a quiet season, a weaker hook. Check those before blaming the algorithm.
4. Keep, stop, try
Three of each, tied to the goal in the business file:
- Keep: what is working, with the number that says so.
- Stop: what costs time and returns little, with its number.
- Try: one test per line, with what you will measure next month.
A keep or stop with no number behind it is a hunch. Move it to try. Fewer than three is fine when the data is thin. Say so instead of filling the slot.
Every number in the scorecard comes from the tool's output or the user. If you work one out yourself, show the sum.
For a local business, also ask three things. Are posts reaching people nearby (location data in Insights, if shown)? Did the offer posts lead to visits or orders (ask the user)? Which collabs helped?
5. Scorecard
End with a small table to beat next month, using only numbers from this audit:
SCORECARD · <month>
posts <n> next month aim: <n>
median reach <n>
shares+saves/100 <n>
follows <n>
profile visits <n>
goal metric <n or {{from you}}> (e.g. founding seats sold)6. Output and files
INSTAGRAM AUDIT · <business> · <date range> · <n> posts
data: <file>, columns missing: <list>
sample: <ok / small, read as hunches>
REACH ...
WORTH ...
MOVING ...
TOP 3 / BOTTOM 3 ...
KEEP / STOP / TRY ...
SCORECARD ...Keep the wording plain; run it through references/before-you-show.md.
Save to ~/.founder/social/instagram/<slug>/audits/<YYYY-MM-DD>.md. Next month, read the last
audit first and compare.
This is a read of the user's own data, not financial advice. If the user is deciding on ad spend or hiring based on it, say to sanity check the numbers with whoever does their books.
Reads: the export, log.md, plan.md history, business file, the last audit. Writes:
audits/. Next: /instagram-plan for next month, /instagram-profile if visits do not
become follows.
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.

