Instagram API

Analyze Instagram workflows with JustOneAPI, including user Profile, post Details, and user Published Posts across 5 operations.

Security Scan

This skill is internally consistent: it requires only a JustOneAPI token and node, and its instructions and code call JustOneAPI endpoints to retrieve Instagram data as described.

Purpose & Capability

Name/description (Instagram via JustOneAPI) aligns with requested artifacts: the skill requires node and JUST_ONE_API_TOKEN and the manifest and code call https://api.justoneapi.com endpoints for Instagram data. No unrelated cloud credentials, binaries, or config paths are requested.

Instruction Scope

SKILL.md instructs the agent to pick an operation, ask for missing params, and run bin/run.mjs with --operation and --token. It does not ask the agent to read unrelated files, environment variables, or transmit data to endpoints other than the declared baseUrl (api.justoneapi.com). Error-handling guidance is explicit and scoped to the backend responses.

Install Mechanism

No install spec is provided (instruction-only deployment), and included code is a small node script (bin/run.mjs). Nothing downloads arbitrary archives or runs remote installers.

Credentials

Only JUST_ONE_API_TOKEN is required and declared as the primary credential. That single API token is proportional to the stated purpose (calling JustOneAPI). No other secrets or unrelated environment variables are requested.

Persistence & Privilege

The skill is not always-on (always: false) and requests no system-wide configuration or modification of other skills. Autonomous invocation is allowed (default) but that is normal for skills and is not combined with other concerning privileges.

Assessment

This skill appears to do what it says: it sends GET requests to JustOneAPI endpoints and needs only your JUST_ONE_API_TOKEN. Before installing, confirm you trust https://api.justoneapi.com and that the token you supply is scoped appropriately (use a token limited to the minimum necessary privileges). Avoid reusing high-privilege credentials, rotate the token if you stop using the skill, and review JustOneAPI's privacy/terms to understand how third-party data is handled. If you need stricter guarantees, ask the publisher for token-scoping details and ensure you are comfortable with autonomous invocation (the agent may call the skill without explicit prompts).

Instagram

This skill wraps 5 Instagram operations exposed by JustOneAPI. It is strongest for user Profile, post Details, user Published Posts, and reels Search. Expect common inputs such as paginationToken, username, code, endCursor, hashtag.

When To Use It

• The user needs user Profile or post Details on Instagram.
• The task lines up with user Published Posts rather than a generic cross-platform workflow.
• The user can provide identifiers or filters such as paginationToken, username, code, endCursor.
• The user wants an exact API-backed answer instead of a freeform summary.

Representative Operations

• getUserDetailV1: User Profile — Get Instagram user Profile data, including follower count, following count, and post count, for obtaining basic account metadata for influencer vetting, tracking follower growth and audience reach over time, and mapping user handles to specific profile stats
• getPostDetailV1: Post Details — Get Instagram post Details data, including post caption, media content (images/videos), and publish time, for analyzing engagement metrics (likes/comments) for a specific post and archiving post content and media assets for content analysis
• getUserPostsV1: User Published Posts — Get Instagram user Published Posts data, including post code, caption, and media type, for monitoring recent publishing activity of a specific user and building a historical record of content for auditing or analysis
• searchReelsV1: Reels Search — Get Instagram reels Search data, including post ID, caption, and author profile, for tracking trends and viral content via specific keywords or hashtags and discovering high-engagement reels within a particular niche

Request Pattern

• 5 operations are available in this skill.
• HTTP methods used here: GET.
• The most common non-token parameters are paginationToken, username, code, endCursor, hashtag.
• All operations in this skill are parameter-driven requests; none require a request body.

How To Work

1. Read generated/operations.md before choosing an endpoint.
2. Start with one of these operations when it matches the user's request: getUserDetailV1, getPostDetailV1, getUserPostsV1, searchReelsV1.
3. Pick the smallest matching operation instead of guessing.
4. Ask the user for any missing required parameter. Do not invent values.
5. Call the helper with:

node {baseDir}/bin/run.mjs --operation "<operation-id>" --token "$JUST_ONE_API_TOKEN" --params-json '{"key":"value"}'

Environment

• Required: JUST_ONE_API_TOKEN

Output Rules

• Start with a plain-language answer tied to the Instagram task the user asked for.
• Include the most decision-relevant fields from the selected endpoint before dumping raw JSON.
• When using getUserDetailV1, explain why the returned fields answer the user's question.
• If the user gave filters such as paginationToken, username, code, echo those back so the scope is explicit.
• If the backend errors, include the backend payload and the exact operation ID.