instagram-skill
- Repo stars 1,952
- Author updated Live
- Author repo instagram-cli
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @supreme-gg-gg · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: instagram-skill
description: > Instagram CLI (instagram-cli) is a terminal client for Instagram. For agents, it exposes Every…
category: other
runtime: no special runtime
---
# instagram-skill output preview
## PART A: Task fit
- Use case: > Instagram CLI (instagram-cli) is a terminal client for Instagram. For agents, it exposes Every command that targets a thread accepts a <thread> argument resolved in this order: then pass those IDs directly to subsequent commands. This avoids redundant search API calls and runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Thread Resolution / JSON Output / Commands” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> Instagram CLI (instagram-cli) is a terminal client for Instagram. For agents, it exposes Every command that targets a thread accepts a <thread> argument resolved in this order: then pass those IDs directly to subsequent commands. This avoids redundant search API calls and runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Thread Resolution / JSON Output / Commands” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Thread Resolution / JSON Output / Commands”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: instagram-skill
description: > Instagram CLI (instagram-cli) is a terminal client for Instagram. For agents, it exposes Every…
category: other
source: supreme-gg-gg/instagram-cli
---
# instagram-skill
## When to use
- > Instagram CLI (instagram-cli) is a terminal client for Instagram. For agents, it exposes Every command that targets…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Thread Resolution / JSON Output / Commands” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "instagram-skill" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Thread Resolution / JSON Output / Commands
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Instagram CLI — Agent Usage Guide
Instagram CLI (instagram-cli) is a terminal client for Instagram. For agents, it exposes
one-turn commands that print to stdout and exit — perfect for scripting and tool-use.
All one-turn commands require the user to already be logged in (
instagram-cli auth login). If a command returns an auth error, prompt the user to log in first. Do not attempt to login using the CLI by yourself.
Thread Resolution
Every command that targets a thread accepts a <thread> argument resolved in this order:
- Thread ID (20+ digit number like
340282366920938463...) — direct, zero extra API calls - Username — exact Instagram username (e.g.
johndoe) - Thread title — fuzzy search across inbox (e.g.
"Book Club")
Best practice for multi-step workflows: call inbox --output json first to get thread IDs,
then pass those IDs directly to subsequent commands. This avoids redundant search API calls and
is more reliable than username/title matching.
JSON Output
All commands accept -o json / --output json. Responses follow this envelope:
{ "ok": true, "data": { ... } }
{ "ok": false, "error": "message" }
Always use --output json when you need to parse results programmatically.
Commands
List inbox
instagram-cli inbox [--limit <n>] [--output json]
Returns recent threads. Each thread includes: id, title, users, lastMessage, lastActivity, unread.
# Get 10 most recent threads as JSON
instagram-cli inbox --limit 10 --output json
Search threads
instagram-cli inbox --search <query> [--limit <n>] [--output json]
Searches by both username and thread title, merging results by relevance score.
instagram-cli inbox --search "alice" --output json
Send a message
instagram-cli send <thread> --text <message> [--output json]
instagram-cli send <thread> --file <path> [--type photo|video] [--output json]
<thread> is a thread ID, username, or title. --text and --file are mutually exclusive.
Media type is auto-detected from extension; use --type to override.
instagram-cli send johndoe --text "Hey, are you free tonight?"
instagram-cli send 340282366920938463123456789 --text "Got it!"
instagram-cli send "Book Club" --file ./photo.jpg --output json
Read messages
instagram-cli read <thread> [--limit <n>] [--cursor <cursor>] [--mark-seen] [--output json]
Returns messages newest-first. Use cursor from the previous response to paginate older messages.
Pass --mark-seen to mark the thread as read after fetching.
instagram-cli read johndoe --limit 20 --output json
instagram-cli read 340282366920938463123456789 --mark-seen
Each message in JSON output includes: id, itemType, text, userId, username, timestamp, isOutgoing.
Download media from a message
instagram-cli read <thread> --message-id <id> --download <path> [--output json]
Finds the message by ID (paginates up to --max-pages, default 10) and saves the media file.
The file extension is automatically inferred if not provided.
instagram-cli read johndoe --message-id 340282366... --download ./media
Reply to a message
instagram-cli reply <thread> --message-id <id> --text <text> [--output json]
Sends a threaded reply to a specific message.
instagram-cli reply johndoe --message-id 340282366... --text "Totally agree!"
Unsend a message
instagram-cli unsend <thread> --message-id <id> [--output json]
instagram-cli unsend johndoe --message-id 340282366...
Multi-Account Support
All commands accept -u <username> / --username <username> to target a specific logged-in account.
Omitting it uses the default account set via instagram-cli auth switch.
instagram-cli inbox -u myworkaccount --output json
instagram-cli send johndoe --text "Hi" -u mypersonalaccount
Typical Agent Workflow
# 1. Get inbox to find the right thread
INBOX=$(instagram-cli inbox --output json --limit 20)
# Parse "id" fields from INBOX to find the target thread
# 2. Read recent messages (use thread ID for speed)
THREAD_ID="340282366920938463..."
instagram-cli read "$THREAD_ID" --limit 10 --output json
# 3. Reply or send
instagram-cli send "$THREAD_ID" --text "On my way!" --output json
# 4. Mark as seen
instagram-cli read "$THREAD_ID" --mark-seen
Error Handling
- Auth errors → user needs to run
instagram-cli auth login - "No thread found matching" → the username/title didn't resolve; try
inbox --searchfirst "ok": falsein JSON output → theerrorfield contains the reason- Rate limits / network errors are surfaced as error messages; retry with backoff if needed
Decide Fit First
Design Intent
How To Use It
Boundaries And Review