Facebook API

Analyze Facebook workflows with JustOneAPI, including post Search, get Profile ID, and get Profile Posts.

Security Scan

The skill's code, instructions, and required credential (JUST_ONE_API_TOKEN) align with its stated purpose of calling JustOneAPI endpoints for Facebook post search and profile lookups.

Purpose & Capability

Name/description (Facebook via JustOneAPI) match the manifest and implementation. The skill only requires 'node' and a JUST_ONE_API_TOKEN which are appropriate for running the included Node script that calls api.justoneapi.com.

Instruction Scope

SKILL.md directs the agent to choose one of three GET endpoints and to run the included node CLI with --operation, --token, and --params-json. The instructions do not request unrelated files, other environment variables, or any data exfiltration beyond calling the documented API.

Install Mechanism

There is no install spec (instruction-only with an included Node script). No downloads from arbitrary URLs or archive extraction are present. The runtime dependency is simply 'node', which is coherent with the included bin/run.mjs.

Credentials

Only one environment variable is required (JUST_ONE_API_TOKEN) and is used as the API token for the listed endpoints. There are no unrelated or excessive credential requests.

Persistence & Privilege

The skill does not request always:true, does not modify other skills or system settings, and has normal autonomous-invocation defaults. It only executes one-off API calls and prints JSON.

Assessment

This skill appears to do what it says: it runs a small Node CLI that calls JustOneAPI (api.justoneapi.com) using the JUST_ONE_API_TOKEN. Before installing, confirm you trust JustOneAPI and that the token you provide has only the minimum needed scope. Note that the token is sent as a query parameter (per the script), which can be logged by servers or intermediaries — prefer tokens with limited privileges and rotate them if exposed. If you handle sensitive accounts or data, review JustOneAPI's privacy/security practices and consider testing with a low-privilege token first. Finally, the skill prints raw JSON from the backend — review responses before sharing externally.

Facebook

This skill wraps 3 Facebook operations exposed by JustOneAPI. It is strongest for post Search, get Profile ID, and get Profile Posts. Expect common inputs such as cursor, endDate, keyword, profileId, startDate.

When To Use It

• The user needs post Search or get Profile ID on Facebook.
• The task lines up with get Profile Posts rather than a generic cross-platform workflow.
• The user can provide identifiers or filters such as cursor, endDate, keyword, profileId.
• The user wants an exact API-backed answer instead of a freeform summary.

Representative Operations

• searchV1: Post Search — Get Facebook post Search data, including matched results, metadata, and ranking signals, for discovering relevant public posts for specific keywords and analyzing engagement and reach of public content on facebook
• getProfileIdV1: Get Profile ID — Retrieve the unique Facebook profile ID from a given profile URL
• getProfilePostsV1: Get Profile Posts — Get public posts from a specific Facebook profile using its profile ID

Request Pattern

• 3 operations are available in this skill.
• HTTP methods used here: GET.
• The most common non-token parameters are cursor, endDate, keyword, profileId, startDate.
• 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: searchV1, getProfileIdV1, getProfilePostsV1.
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 Facebook task the user asked for.
• Include the most decision-relevant fields from the selected endpoint before dumping raw JSON.
• When using searchV1, explain why the returned fields answer the user's question.
• If the user gave filters such as cursor, endDate, keyword, echo those back so the scope is explicit.
• If the backend errors, include the backend payload and the exact operation ID.