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

ig-caption

Skill0 starsChanged 29 days agoMITView on GitHub

Write and lint the caption for a queued Instagram post - the first line that survives the "... more" fold, one ask, plain words, at most five hashtags - in the user's own voice. Use when a queue item has no caption, when the user says "caption this", or when `igap lint` reports problems.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ig-dm, ig-human and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JakeschincariolSkill

    ig-dm

    Write Instagram DMs that get replies - the keyword delivery, the first message to someone who engaged, the collab pitch, and the two follow-ups. Use when the user says "DM this person", "what do I send them", "outreach message", "how do I follow up", "pitch this brand", or is reaching out to someone specific.

    Also in 9 projects that use this

  • JakeschincariolSkill

    ig-human

    Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out. Use whenever text needs to sound human, when the user says humanize, "does this sound like AI", "remove the em dashes", "de-slop this", "this sounds like ChatGPT", or before any caption, script, comment, reply or DM is shown to the user.

    Also in 9 projects that use this

  • vava2684Skill

    ig-reply

    Instagram 貼文留言智慧回覆。抓某篇貼文底下的新留言,由 Claude 在對話裡依貼文內容與留言者語言生成友善回覆,再透過 Graph API 自動送出。觸發時機:使用者說「回覆留言」「處理 IG 留言」「回 IG」「IG 自動回覆」「抓留言來回」「回我 IG 那篇」等。

    Also in 7 projects that use this

  • +3 more from Jakeschincariol

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    Distinctive

    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. Distinctive:

    Ask what the video shows and the one thing a viewer should do next, if the user has not said.

    line 14
  2. Distinctive:

    Use only facts the user gave you.

    line 15
  3. Very specific:

    If the account uses AI voices or generated footage, say so in the caption.

    line 20
  4. Very specific:

    Run igap lint <id> and fix every ERROR.

    line 22
  5. Distinctive:

    Write like a person talking to one viewer: contractions, concrete nouns, no stock phrases (the lint lists the common ones).

    line 24

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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-caption

The caption is the text under the frontmatter in the item's queue file (~/.instagram-autopilot/queue/<id>.md). Edit it there, then igap lint <id>.

  1. Ask what the video shows and the one thing a viewer should do next, if the user has not said. Use only facts the user gave you.
  2. Line one carries the post. The feed shows about 125 characters. For a Reel that already hooks in the video, line one is context plus the ask; for an image or carousel, line one is the hook.
  3. One ask. Links are not clickable in captions, so say "link in bio".
  4. Hashtags: 0–3 specific ones beat 5 generic ones; the hard cap is caption.max_hashtags.
  5. If the account uses AI voices or generated footage, say so in the caption; put the phrase in caption.require_phrases so the lint enforces it.
  6. Run igap lint <id> and fix every ERROR. Read the WARN lines and fix the ones that matter.

Write like a person talking to one viewer: contractions, concrete nouns, no stock phrases (the lint lists the common ones).

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.