agentleFS
JavoxirJavaJavoxirJava/ig-publisher/skill/SKILL.md

instagram-publisher

Skill2 starsChanged 14 days agoMITView on GitHub

Publish, schedule and manage posts on the user's Instagram business account via the local ig-publisher service (~/ig-publisher). Use whenever the user asks to post/upload/schedule a Reel, photo, carousel or story to Instagram ("instagramga joyla", "reels qo'y", "ertaga 9 da post qil"), check the post queue/history, view Instagram stats/insights, or read/reply to Instagram comments.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. renatoasse/opensquad★ 2.1ksame name
    2. eumateusalex/Template-OS★ 0same 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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never print or send the access token.

    line 13
  2. Very specific:

    If a command fails with code=190 / "token yo'q", tell the user to follow SETUP.md step 3 (ig auth token -).

    line 14
  3. Very specific:

    Add --json for machine-readable output.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 publisher (ig-publisher)

Local service at ~/ig-publisher (adjust the path if you cloned it elsewhere). CLI: ig (in PATH). MCP server ig-publisher exposes the same functions as ig_* tools — use either. Setup guide: ~/ig-publisher/SETUP.md; full docs: ~/ig-publisher/README.md.

Rules

  • Publishing is public and hard to undo. Unless the user clearly asked to post now, run --dry-run first and show the caption.
  • Never print or send the access token. It lives in ~/ig-publisher/data/ig.sqlite.
  • If a command fails with code=190 / "token yo'q", tell the user to follow SETUP.md step 3 (ig auth token -).
  • Duplicate media is refused (exit code 3). Only use --force if the user explicitly wants a re-post.
  • Replying to comments posts publicly — confirm the text with the user first.

Common commands

ig doctor                                  # health: token, ffmpeg, host, quota, scheduler
ig post reel <video> --caption "..." [--cover img.png] [--at "ertaga 09:00"] [--dry-run]
ig post image <img> --caption "..." [--alt "..."]
ig post carousel <f1> <f2> ... --caption "..."
ig post story <file>
ig post --spec post.json [--at ...]
ig queue [--all] | ig queue cancel <id> | ig queue retry <id> --at "+1h"
ig history | ig limit | ig media | ig insights <media-id|account> | ig comments <media-id>

Add --json for machine-readable output. Times: +2h, 09:00, ertaga 09:00, 2026-10-27 18:30 (local).

Publishing a reel takes 1–5 minutes (Instagram processing); scheduled posts are published by the systemd timer every 5 min.

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.