agentleFS
Sign inStart free
raniellimontagnaraniellimontagna/agent-toolkit/skills/research/instagram-public-research/SKILL.md

instagram-public-research

Skill3 starsChanged 35 days agoMITView on GitHub

Collect Instagram-related public and first-party data safely for research packs, without posting, messaging, deleting, or bypassing access controls.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this research-only skill for market, audience, competitor, campaign, creator, or content context.

    line 10
  2. Distinctive:

    Prefer first-party exports or Graph API data when the operator has explicit authorization.

    line 17
  3. Distinctive:

    Use public Instagram pages only when accessible without login and permitted by the terms.

    line 19

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instagram Public Research

Use this research-only skill for market, audience, competitor, campaign, creator, or content context. Never publish, message, delete, hide, automate engagement, scrape authenticated-only content, or bypass login, paywalls, rate limits, bot protections, or platform controls.

Allowed Sources And Order

  1. Prefer first-party exports or Graph API data when the operator has explicit authorization.
  2. Use public Instagram pages only when accessible without login and permitted by the terms; collect public linked brand sources as needed.
  3. Record inaccessible/login-gated sources as limitations. Request an export or authorized API for private analytics, DMs, demographics, or insights.

Data To Extract

  • Visible profile basics, public links/category/counts, and visible themes.
  • Content patterns: topics, offer language, hooks, captions, creative formats, cadence inferred from dates, and CTAs.
  • Public engagement only when visible; otherwise mark it unavailable.
  • Evidence-backed audience/positioning clues, landing-page inputs, and SEO/content entities.

Research Pack Requirements

For every source, record URL, access method, collection time, and whether it was public, API-authorized, or user-provided. Separate visible facts from inference, state unavailable fields and why, use concise summaries rather than raw dumps, and never include private personal data without explicit authorization and need.

Include Instagram Findings: sources, visible facts with citations, content and positioning patterns, landing-page implications, and limitations.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free