Jd Price History
v1.0.0京东商品价格历史查询，发现真实低价，避开先涨后降套路。适合比价购物、电商卖家。
⭐ 0· 204·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (JD price history) match the declared requirements: python3, curl and the optional pip dependency 'requests' are reasonable for fetching and parsing product pages. No unrelated env vars, binaries, or config paths are requested.
Instruction Scope
SKILL.md describes what the skill does and gives example queries and output but does not provide concrete runtime commands or third-party endpoints. It implies fetching JD product pages (expected) and setting up notifications, but it doesn't explain how notifications or paid features are implemented. The instructions do not direct reading local files or unrelated environment variables.
Install Mechanism
No install spec that downloads arbitrary archives; metadata only suggests installing the well-known 'requests' pip package. No remote, untrusted URL downloads or extract steps are present.
Credentials
No environment variables or credentials are requested. The required binaries and pip dependency are proportionate to the stated functionality.
Persistence & Privilege
always:false and no config paths requested. The skill does not request persistent or elevated platform privileges.
Assessment
This skill appears internally consistent with a JD price-history helper, but before installing consider: 1) The SKILL.md lacks implementation details—ask how it fetches JD pages (direct scraping vs. third-party API), how it handles rate limits and anti-bot measures, and whether it honors robots.txt and JD's terms. 2) Notifications and paid tiers are described but no mechanism is provided—verify where payment is handled and what third parties (if any) will receive your data. 3) Because scraping can be blocked or legally sensitive, confirm the developer's approach and get the implementation (or a code audit) if you need stronger assurance. 4) There are no requested secrets or system accesses, which is good; nonetheless avoid supplying unrelated credentials until you verify the notification/payment integrations.Like a lobster shell, security has layers — review code before you run it.
latestvk97fahgn00cep9dwrq7xy54zfx83jjgt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📈 Clawdis
Binspython3, curl