Ig audience insights
Skill sergebulaev/instagram-skills/.codex-marketplace/instagram-skills/skills/ig-audience-insights
Read your Instagram niche and profile from real data via Apify, no login. Scan a hashtag for the posts traveling now (likes, comments, owner) to see the format and hook that works. Pull profile stats for any handle, yours or a competitor's: followers, posts, bio, category. Instagram hides who liked or commented on other accounts, so this is discovery plus profiles, not engagers. Triggers on "what works in my niche", "scan the hashtag", "competitor stats". Not for writing captions (use ig-caption-writer).From its SKILL.md
npx -y skills add sergebulaev/instagram-skills --skill ig-audience-insightsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- reads credentialsReads from 1 credential source: `APIFY_TOKEN`.
- 12 stars12 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.
- runs commandsInstructs the agent to run 2 commands, including `lib.ApifyClient().fetch_niche_posts(hashtag, max_items=20)` and 1 more.
SKILL.md
5.0 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
Instagram Audience Insights
Turn real Instagram data into a read on what is working: which posts in your niche are traveling right now and why, and how any account (yours or a competitor's) actually performs. This is the read layer, so the skill sees real numbers instead of guessing.
One honest limit: Instagram caps and cookie-gates who liked or commented on someone else's post, so a liker or commenter roster is not reliably available for other accounts. The signal here is niche post performance + profile stats, which is what you can actually read on Instagram.
When to use
- "What is working in my niche / scan the #hashtag"
- "Pull the stats for this account / how big is this competitor"
- "What format is traveling under this hashtag right now"
- "Compare my follower count to this account"
Not for writing a caption (use ig-caption-writer) or planning a carousel (use ig-carousel-planner).
Setup (optional)
The read layer uses Apify (no login, no cookies). Get a free token at https://console.apify.com/account/integrations and set APIFY_TOKEN. No token? Paste the posts or profile stats you already have and the skill runs the same analysis on them.
Input
- A niche hashtag (with or without the
#), a username (yours or a competitor's), or both - Optional: the goal (niche pulse / competitor read / self benchmark)
Output
- Niche pulse - the top posts under a hashtag ranked by engagement, with the pattern behind the winners (hook shape, caption length, image vs carousel vs Reel, presence of a question or a specific number)
- Profile read - the stats for a handle: followers, post count, bio, category, verified and business flags
- Benchmark - your account against a competitor on follower count and post cadence, normalized so a small account's breakout is not buried under a big account's average
- Action list - what format to make more of, which accounts to watch, what to route to
ig-caption-writerorig-carousel-planner
Steps
- Pull the data. For a niche:
lib.ApifyClient().fetch_niche_posts(hashtag, max_items=20). For a profile:fetch_profile(username). Falls back to pasted data if no token. - Rank by engagement. Sort the niche posts by likes + comments. Normalize against the owner's reach where known so a mega-account's average does not crowd out a small account's breakout.
- Extract the pattern. For the top posts, name what they share: the hook shape (question, confession, list, data-point), the caption length, image vs carousel vs Reel, the presence of a specific number. That is the repeatable part.
- Read the profile. From
fetch_profile, report followers, post count, bio, category, and whether it is a verified business account. Use it to benchmark, not to guess private engagement. - Benchmark honestly. Compare handles on the stats Instagram exposes (followers, post count, cadence). Do not imply access to a liker or commenter list for accounts you do not own.
- Build the action list. Make-more-of (the winning format), watch (specific accounts), route drafts to
ig-caption-writer/ig-carousel-planner. - Deliver the report in the Output shape, with the raw ranked posts and profile stats attached.
What the read layer exposes
| Method | Returns |
|---|---|
fetch_niche_posts(hashtag, max_items) | top posts under a hashtag: caption, likes, comments, owner, type, url |
fetch_profile(username) | profile stats: username, followers, following, posts, bio, category, verified, business |
Hard rules
Global voice rules: see root SKILL.md Voice rules. Additional skill-specific rules:
- Be honest that Instagram hides who liked or commented on other accounts. This is niche discovery + profile stats, not a liker or engager roster. Do not imply otherwise.
- Normalize by follower count before calling a post a winner, or you extract "big account" effects, not "good post" effects.
- Never invent a post, a number, or a pattern. If a hashtag returns thin, say so and try an adjacent tag or pull known accounts.
- A pattern is only a pattern if it recurs across several top posts, not one.
Related skills
ig-caption-writer- write more of what the niche data shows is workingig-carousel-planner- turn a winning format into a slide planig-hook-extractor- reverse-engineer the hook from a top-performing postig-hashtag-strategist- size the hashtag set around the tags that are travelingig-content-planner- feed the winning patterns into a weekly plan
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in ~1.1k tokens
Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06
- Use third-person for skill descriptionsin 54 of 1951, across 35 files
- Start descriptions with Use whenin 43 of 1951, across 29 files
- Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
- Use active voicein 40 of 1951, across 36 files
- Map file responsibilities before defining tasksin 36 of 1951, across 29 files
- Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
- Ask one question at a timein 35 of 1951
- Offer execution options after saving the planin 33 of 1951, across 24 files
- Include complete code in every stepin 33 of 1951, across 27 files
- Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
- Announce the skill usage at the startin 30 of 1951
- Verify agent compliance after adding the skillin 29 of 1951, across 17 files
Said here and by no other author read
- Create action list for content and engagement
- Fetch niche posts using Apify
- Fetch profile stats for handles
- Normalize engagement by follower count
- Identify recurring patterns in top posts
- Compare handles using public stats
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.