instagram skill

Other Community

Skill notes

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,

JSON Output

All commands accept -o json / --output json. Responses follow this envelope: Always use --output json when you need to parse results programmatically.

List inbox

Returns recent threads. Each thread includes: id, title, users, lastMessage, lastActivity, unread.

Search threads

Searches by both username and thread title, merging results by relevance score.

Send a message

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview instagram-skill.preview
# JSON Output

{ "ok": true, "data": { ... } }
{ "ok": false, "error": "message" }

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.