Use the Instagram Graph API by directly executing curl commands to read and publish Instagram content.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioninstagramExecute the skills CLI command in your project's root directory to begin installation:
Fetches instagram from vm0-ai/vm0-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate instagram. Access via /instagram in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
52
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
52
stars
Use the Instagram Graph API by directly executing curl commands to read and publish Instagram content.
Official docs:
https://developers.facebook.com/docs/instagram-api
Use this skill when you need to:
INSTAGRAM_TOKEN: a long-lived user access tokenINSTAGRAM_BUSINESS_ACCOUNT_ID: your Instagram Business account IDSet the environment variables, for example:
export INSTAGRAM_TOKEN="EAAG..."
export INSTAGRAM_BUSINESS_ACCOUNT_ID="1784140xxxxxxx"
These examples use Graph API version v21.0. You can replace this with the latest version if needed.
Depending on which endpoints you use, make sure your app has requested and been approved for (at least):
instagram_basicpages_show_listinstagram_content_publish (for publishing media)instagram_manage_insights and related permissions (for insights / some hashtag use cases)All examples below assume you have already set:
INSTAGRAM_TOKEN
INSTAGRAM_BUSINESS_ACCOUNT_ID
Fetch the most recent media (photos / videos / Reels) for the account:
curl -s -X GET "https://graph.facebook.com/v21.0/$INSTAGRAM_BUSINESS_ACCOUNT_ID/media?fields=id,caption,media_type,media_url,permalink,timestamp" --header "Authorization: Bearer $INSTAGRAM_TOKEN"
Notes:
id: media ID (used for details / insights later)caption: caption textmedia_type: IMAGE / VIDEO / CAROUSEL_ALBUMmedia_url: direct URL to the mediapermalink: Instagram permalinktimestamp: creation timeIf you already have a media id, you can fetch more complete information. Replace <your-media-id> with the id field from the "Get User Media" response (section 1 above):
curl -s -X GET "https://graph.facebook.com/v21.0/<your-media-id>?fields=id,caption,media_type,media_url,permalink,thumbnail_url,timestamp,username" --header "Authorization: Bearer $INSTAGRAM_TOKEN"
Note: hashtag search requires proper business use cases and permissions as defined by Facebook/Instagram. Refer to the official docs.
This usually involves two steps:
Replace <hashtag-name> with any hashtag name you want to search for (without the # symbol), e.g., "travel", "food", "photography":
curl -s -X GET "https://graph.facebook.com/v21.0/ig_hashtag_search?user_id=$INSTAGRAM_BUSINESS_ACCOUNT_ID&q=<hashtag-name>" --header "Authorization: Bearer $INSTAGRAM_TOKEN"
Note the id field in the returned JSON for use in the next step.
Replace <hashtag-id> with the id field from the "Search Hashtag" response (section 3.1 above):
curl -s -X GET "https://graph.facebook.com/v21.0/<hashtag-id>/recent_media?user_id=$INSTAGRAM_BUSINESS_ACCOUNT_ID&fields=id,caption,media_type,media_url,permalink,timestamp" --header "Authorization: Bearer $INSTAGRAM_TOKEN"
Publishing an image post via the Graph API usually requires two steps:
Write the request data to /tmp/request.json:
{
"image_url": "https://example.com/image.jpg",
"caption": "Hello from Instagram API 👋"
}
Replace https://example.com/image.jpg with any publicly accessible image URL and update the caption text as needed.
curl -s -X POST "https://graph.facebook.com/v21.0/$INSTAGRAM_BUSINESS_ACCOUNT_ID/media" -H "Content-Type: application/json" -d @/tmp/request.json --header "Authorization: Bearer $INSTAGRAM_TOKEN"
The response will contain an id (media container ID), for example:
{
"id": "1790xxxxxxxxxxxx"
}
Note this ID for use in the next step.
Write the request data to /tmp/request.json:
{
"creation_id": "<your-creation-id>"
}
Replace <your-creation-id> with the id field from the "Create Media Container" response (section 4.1 above):
curl -s -X POST "https://graph.facebook.com/v21.0/$INSTAGRAM_BUSINESS_ACCOUNT_ID/media_publish" -H "Content-Type: application/json" -d @/tmp/request.json --header "Authorization: Bearer $INSTAGRAM_TOKEN"
If successful, the response will contain the final media id:
{
"id": "1791yyyyyyyyyyyy"
}
You can then use the "Get details for a single media" command to fetch its permalink.
(#10) Application does not have permission for this actionINSTAGRAM_TOKEN is a valid long-lived tokenINSTAGRAM_TOKEN is sensitive; avoid printing it in logs or chat transcriptsv21.0 version in URLs to the latest<your-media-id> instead of shell variables in URLs to avoid dependencies and make examples self-containedMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
instagram fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
instagram has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added instagram from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
instagram reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend instagram for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for instagram matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: instagram is focused, and the summary matches what you get after install.
Useful defaults in instagram — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added instagram from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
instagram has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 41