Bilibili API

Analyze Bilibili workflows with JustOneAPI, including video Details, user Published Videos, and user Profile across 9 operations.

Security Scan

The skill's code, instructions, and required token line up with its stated Bilibili-query purpose and do not request unrelated credentials or risky installs.

Purpose & Capability

Name/description claim Bilibili lookups via JustOneAPI. The skill requires JUST_ONE_API_TOKEN (the API token) and node to run bin/run.mjs; both are consistent with a CLI wrapper that queries https://api.justoneapi.com.

Instruction Scope

SKILL.md instructs the agent to pick an operation, ask for missing parameters, and run the included node script with --operation and --token. Instructions do not ask the agent to read unrelated files or exfiltrate data to non-JustOneAPI endpoints. The bundled run.mjs appears to map operations to the JustOneAPI baseUrl declared in the manifest, which matches the described scope.

Install Mechanism

No install spec or external downloads are requested. The skill is executed as a local Node script (node binary required). This is low-risk compared to remote code downloads or package installs.

Credentials

Only a single env var (JUST_ONE_API_TOKEN) is required and declared as the primary credential; that is proportionate for a third-party API wrapper. No other unrelated credentials, file paths, or secrets are requested.

Persistence & Privilege

The skill does not request always:true and uses normal autonomous invocation settings. It does not modify other skills or request system-wide config changes.

Assessment

This skill runs a local Node script that sends your JUST_ONE_API_TOKEN to JustOneAPI (https://api.justoneapi.com) to perform Bilibili queries. Before installing: verify you trust JustOneAPI and are comfortable giving it the token; prefer a token with limited scope if available; confirm the token is not reused elsewhere; ensure your environment has Node installed; and, if you want extra assurance, inspect the full bin/run.mjs file locally to confirm it only calls the documented endpoints and does not log or forward responses to unexpected hosts. If you have sensitive data tied to that token, test with non-sensitive queries first.

Bilibili

This skill wraps 9 Bilibili operations exposed by JustOneAPI. It is strongest for video Details, user Published Videos, user Profile, and video Danmaku. Expect common inputs such as aid, bvid, cid, page, uid.

When To Use It

• The user needs video Details or user Published Videos on Bilibili.
• The task lines up with user Profile rather than a generic cross-platform workflow.
• The user can provide identifiers or filters such as aid, bvid, cid, page.
• The user wants an exact API-backed answer instead of a freeform summary.

Representative Operations

• getVideoDetailV2: Video Details — Get Bilibili video Details data, including metadata (title, tags, and publishing time), for tracking video performance and engagement metrics and analyzing content metadata and uploader information
• getUserVideoListV2: User Published Videos — Get Bilibili user Published Videos data, including titles, covers, and publish times, for creator monitoring and content performance analysis
• getUserDetailV2: User Profile — Get Bilibili user Profile data, including account metadata, audience metrics, and verification-related fields, for analyzing creator's profile, level, and verification status and verifying user identity and social presence on bilibili
• getVideoDanmuV2: Video Danmaku — Get Bilibili video Danmaku data, including timeline positions and comment text, for audience reaction analysis and subtitle-style comment review

Request Pattern

• 9 operations are available in this skill.
• HTTP methods used here: GET.
• The most common non-token parameters are aid, bvid, cid, page, uid.
• 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: getVideoDetailV2, getUserVideoListV2, getUserDetailV2, getVideoDanmuV2.
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 Bilibili task the user asked for.
• Include the most decision-relevant fields from the selected endpoint before dumping raw JSON.
• When using getVideoDetailV2, explain why the returned fields answer the user's question.
• If the user gave filters such as aid, bvid, cid, echo those back so the scope is explicit.
• If the backend errors, include the backend payload and the exact operation ID.