agentleFS
dileepgaganrdileepgaganr/instagram-autopilot-skill/skills/ig-learn/SKILL.md

ig-learn

Skill0 starsChanged 30 days agoMITView on GitHub

Learn from what an Instagram account already posted - pull insights through the API, compare each post with the account's own median, correlate views and watch-through with video timing, length, posting slot, hook and caption, and turn that into a playbook the autopilot applies. Use when the user asks "what's working", "why did this flop", "when should I post", "what should I change", or wants a performance report.

The file

Files
SKILL.md

ig-learn

igap sync               # pull insights for posts younger than 7 days
igap learn              # rebuild ~/.instagram-autopilot/playbook.json and print it
igap report             # print the last playbook + recent posts

The scheduler runs sync + learn on every tick, so this is mostly for reading and explaining.

How it decides

  • Outlier multiple = a post's views ÷ the account's own median. Raw views mostly measure follower count; the multiple measures the post.
  • Watch-through = average watch time ÷ video length (Reels only).
  • Numeric features (length, first cut, longest still, lead silence, loudness, caption length, hashtags, hour) are rank-correlated (Spearman) with both. |rho| ≥ 0.4 is reported as a signal.
  • Buckets: length band, weekday+hour slot, and the hook tag set on each item.
  • Confidence: collecting below learn.min_posts (6) settled posts, then low < 12, medium < 30, high. Nothing is applied while collecting.

What it changes on its own: target_max_s (best length band, if it beats the median by 20% with 2+ posts), max_shot_s (when still stretches hurt), max_lead_silence_s (when dead air hurts), and the posting slots. Everything else is advice for the user.

Talking about results

Be honest about sample size: 8 posts is a hint, not proof. Recommend changing one thing at a time (tag hooks with --hook so they can be compared) and say which signal a recommendation rests on. A post with a high multiple and low watch-through had a good hook and a weak middle; the reverse had a weak hook. Point at the specific timing feature when you can.

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.