JD.com API

Analyze JD.com workflows with JustOneAPI, including product Details, product Comments, and shop Product List.

Security Scan

This skill is a straightforward wrapper around JustOneAPI's JD.com endpoints and only needs a Node runtime and a single API token that it sends to api.justoneapi.com; its files and instructions align with that purpose.

Purpose & Capability

The name/description claim JD.com product/details/comments/shop list functionality and the code, manifest, and SKILL.md all implement exactly those GET endpoints on https://api.justoneapi.com. Requiring the node binary and JUST_ONE_API_TOKEN is appropriate for this purpose.

Instruction Scope

SKILL.md limits runtime behavior to selecting an operation, asking for missing parameters, and invoking the included Node helper. The helper only reads CLI args, constructs a URL for the advertised endpoints, performs a network GET, and returns JSON. It does not read unrelated files, other env vars, or transmit data to unexpected endpoints.

Install Mechanism

There is no install spec (instruction-only skill with a small included Node script). Nothing is downloaded or extracted at install time; the only requirement is an existing node binary.

Credentials

The skill requests a single API token (JUST_ONE_API_TOKEN) which is declared as the primary credential and is used as the required 'token' query parameter when calling the JustOneAPI endpoints. No unrelated secrets, config paths, or additional credentials are requested.

Persistence & Privilege

always is false and the skill does not attempt to modify other skills or system settings. It has no install hooks that persist credentials or change agent configuration. Normal autonomous invocation is allowed (disable-model-invocation is false) which is expected for skills.

Assessment

This skill appears to do what it says: call JustOneAPI's JD.com endpoints. Before installing, confirm you trust api.justoneapi.com (the JUST_ONE_API_TOKEN will be sent to that domain as a query parameter). Be aware that passing tokens on the command line can expose them in shell history or process lists—use environment variables (as suggested) and avoid pasting secrets into ephemeral commands. Check JustOneAPI's billing, privacy, and rate-limit policies for your token, and ensure your agent's network policy allows calls only to the intended host.

JD.com

This skill wraps 3 JD.com operations exposed by JustOneAPI. It is strongest for product Details, product Comments, and shop Product List. Expect common inputs such as itemId, page, shopId.

When To Use It

• The user needs product Details or product Comments on JD.com.
• The task lines up with shop Product List rather than a generic cross-platform workflow.
• The user can provide identifiers or filters such as itemId, page, shopId.
• The user wants an exact API-backed answer instead of a freeform summary.

Representative Operations

• getItemDetailV1: Product Details — Get JD.com product Details data, including pricing, images, and shop information, for catalog analysis, product monitoring, and ecommerce research
• getItemCommentsV1: Product Comments — Get JD.com product Comments data, including ratings, timestamps, and reviewer signals, for customer feedback analysis and product research
• getShopItemListV1: Shop Product List — Get JD.com shop Product List data, including item titles, prices, and images, for catalog tracking and seller research

Request Pattern

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