Amazon API

Analyze Amazon workflows with JustOneAPI, including product Details, product Top Reviews, and best Sellers across 4 operations.

Security Scan

The skill is internally consistent: it wraps JustOneAPI Amazon endpoints, only needs a single API token and node, and its code/instructions align with that purpose.

Purpose & Capability

Name/description, declared requirements (node, JUST_ONE_API_TOKEN), and the included operations (product detail, reviews, best sellers, products by category) are aligned. Requiring JUST_ONE_API_TOKEN is expected for a third‑party API wrapper.

Instruction Scope

The SKILL.md instructs the agent to call the provided CLI (bin/run.mjs) with the token and operation parameters; it does not ask the agent to read unrelated files or other environment variables. Note: the token is passed as a CLI argument and used as a query parameter, which can expose secrets in process listings, shell history, or server logs—this is a privacy/operational risk but not an incoherence with the skill's purpose.

Install Mechanism

No install/download steps are present (instruction-only plus a bundled run.mjs). There are no external downloads or extract steps; risk from install mechanism is low.

Credentials

The skill requests exactly one credential (JUST_ONE_API_TOKEN) which is the primary credential for calling JustOneAPI. No unrelated secrets, config paths, or multiple credentials are requested.

Persistence & Privilege

always is false and the skill does not request elevated/persistent platform privileges. Autonomous model invocation is permitted by default but is not combined with other concerning factors here.

Assessment

This skill appears to do what it says: call JustOneAPI's Amazon endpoints. Before installing, confirm you trust api.justoneapi.com to receive your JUST_ONE_API_TOKEN. Be aware the token is passed on the command line and as a query parameter—this can expose it in process lists, shell history, or logs; prefer using a least‑privilege token and run the skill in a controlled environment. If you want extra assurance, inspect bin/run.mjs locally to verify it only performs HTTP GETs to api.justoneapi.com and does not exfiltrate data to other endpoints.

Amazon

This skill wraps 4 Amazon operations exposed by JustOneAPI. It is strongest for product Details, product Top Reviews, best Sellers, and products By Category. Expect common inputs such as country, asin, page, category, categoryId.

When To Use It

• The user needs product Details or product Top Reviews on Amazon.
• The task lines up with best Sellers rather than a generic cross-platform workflow.
• The user can provide identifiers or filters such as country, asin, page, category.
• The user wants an exact API-backed answer instead of a freeform summary.

Representative Operations

• getProductDetailV1: Product Details — Get Amazon product Details data, including title, brand, and price, for building product catalogs and enriching item content (e.g., images), price monitoring and availability tracking, and e-commerce analytics and competitor tracking
• getProductTopReviewsV1: Product Top Reviews — Get Amazon product Top Reviews data, including most helpful) public reviews, for sentiment analysis and consumer feedback tracking, product research and quality assessment, and monitoring competitor customer experience
• getBestSellersV1: Best Sellers — Get Amazon best Sellers data, including rank positions, product metadata, and pricing, for identifying trending products in specific categories, market share analysis and category research, and tracking sales rank and popularity over time
• getProductsByCategoryV1: Products By Category — Get Amazon products By Category data, including title, price, and rating, for category-based product discovery and returns product information such as title, price, and rating

Request Pattern

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