JD Price Protection 京东自动价保
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running the skill can submit price-protection applications for all visible eligible JD orders.
The skill intentionally automates clicks that submit JD.com price-protection requests. This matches the stated purpose, but it is still an account-changing action without per-button confirmation.
Click every "申请价保" button on the page
Run it only when you are comfortable letting it act on all eligible JD price-protection entries, and review the JSON result afterward.
The skill can act as the logged-in JD.com user in Chrome while it is running.
The script reads the local OpenClaw gateway token and uses it to connect to the Browser Relay, which then operates through the user's logged-in Chrome/JD session.
const cfg = JSON.parse(readFileSync(join(HOME, '.openclaw/openclaw.json'), 'utf8')); return cfg.gateway?.auth?.token;
Use this only with a Chrome profile you trust for JD automation, and do not run it if you do not want OpenClaw-controlled browser actions on that session.
The skill may fail or use an existing local Playwright dependency that is not declared in the registry requirements.
The script depends on Playwright Core from the environment, but the registry metadata lists no required binaries, env vars, or install spec.
const paths = [ 'playwright-core', join(HOME, '.nvm/versions/node', process.version, 'lib/node_modules/openclaw/node_modules/playwright-core') ];
Ensure Node.js, OpenClaw Browser Relay, and Playwright Core are available from trusted installations before running.
If scheduled, the skill can keep checking JD.com and applying for price protection without manual runs.
The skill documents periodic scheduled operation. This is disclosed and aligned with automatic price protection, but it is persistent automation of a logged-in shopping account.
Set up a cron job to run every ~8 hours.
Only enable cron scheduling if you want recurring unattended JD price-protection checks, and keep a clear way to disable the job.
The agent may keep a record that the JD price-protection check ran, and possibly related shopping-result context depending on how the user schedules it.
The scheduled usage guidance suggests silently updating state, likely a check timestamp. This is limited, but retention and storage location are not specified.
If refunds found, notify user. Otherwise update checkedAt silently.
If using scheduled mode, decide where check history should be stored and avoid saving detailed order information unless needed.