agentleFS
Sign inStart free
JakeschincariolJakeschincariol/instagram-agent-skill/skills/ig-plan/SKILL.md

ig-plan

Skill88 starsChanged 2 months agoMITView on GitHub

Build the week on Instagram - what to post, which format, when, and who to engage with. Use when the user says "plan my week", "what should I post", "content calendar", "I have nothing to post about", or wants a posting schedule and an engagement list.

7 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    If ~/.claude/instagram/voice.md, swipe.md and log.md exist, read them.

    line 17
  2. Distinctive:

    If they do not exist, ask for four things and write them down:

    line 22
  3. Distinctive:

    Not a topic, an angle. "AI" is not a plan.

    line 49
  4. Very specific:

    Write the plan to ~/.claude/instagram/plan.md so the other skills can read it.

    line 98

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

ig-plan

The control room. Everything else in this pack executes; this decides what gets executed. Run it once a week, on the same day.

Input

If ~/.claude/instagram/voice.md, swipe.md and log.md exist, read them. The swipe file is the user's own evidence from /ig-viral about which formulas are landing in their niche right now, and it outranks anything in this file. The log stops the plan repeating a theme from the last fortnight.

If they do not exist, ask for four things and write them down:

  1. What the user sells, and to whom.
  2. The three or four themes they want to be known for.
  3. What actually happened this week: a client call, a number, a mistake, a thing they built, an argument they had. This is where posts come from.
  4. Ten accounts worth being visible to.

What to post

Four to five posts a week, and at least three of them Reels. Reels are the only format on Instagram that reliably reaches people who do not follow the account. Carousels go deep with the people who already do. Stories are daily and are planned separately.

Mix across the week, never two of the same type back to back:

typesharejob
Proof1 per weeksomething that happened, with a number. Reel.
Teach1 to 2 per weekone thing the viewer can do today. Reel or carousel.
Opinion1 per weeka position that could lose you followers. Reel.
Story1 per fortnighta scene with a cost. Reel.
Offer1 per fortnightwhat you sell, said plainly, no apology. Carousel or stories.

For each slot give: the theme, the specific angle from what actually happened this week, the format, and the hook formula number from ig-reel/hooks.json. Not a topic, an angle. "AI" is not a plan. "The proposal we lost because the draft had an em dash in it" is a Reel.

When to post

Post when the user's audience is awake and not at work. For most consumer audiences that is early evening local time; for a business audience, early morning.

But say this plainly: the hour matters far less than the first two seconds. Instagram will keep showing a Reel for days if it performs, and will bury a well-timed one that does not. If the user is optimising posting times before their hooks work, they are polishing the wrong thing, and you should say so.

Anchor times to the audience's timezone, not the user's, if those differ.

The engagement round, which is not optional

20 minutes a day, before posting, not after. Build a list of 10:

  • 5 reach - accounts with an audience the user wants, where a good comment gets seen. Comment early, before the thread is 200 deep.
  • 3 peers - same size, same field. This is the group that reciprocates.
  • 2 buyers - people who could actually buy. Comment for weeks before any DM, and never pitch in a comment.

Hand the list to /ig-comment.

Output

WEEK OF SEP 15

MON  engage only  (20 min, list below)
TUE  7:30pm  REEL      PROOF    #5  Time Collapse   - 5hr proposal to 20 min
WED  stories only + engage
THU  7:00pm  CAROUSEL  TEACH    Job B caption       - the 4-slide clause breakdown
FRI  7:30pm  REEL      OPINION  #2  Negative Command - stop doing discovery calls
SAT  -
SUN  6:00pm  REEL      STORY    #21 Mid-Sentence    - the refund email

STORIES  every day, 3 to 5 frames, question box on Thursday.

ENGAGE  (5 reach / 3 peers / 2 buyers)
  ...

Say "write Tuesday" and I will draft it.

Write the plan to ~/.claude/instagram/plan.md so the other skills can read it. Nothing is scheduled or posted anywhere. This is a plan and the user runs it.

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