Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
carkey
v1.1.0查询车辆位置和车况信息（车锁、车门、车窗、空调等状态）/ Query vehicle location and condition information.
⭐ 0· 91·0 current·0 all-time
byzhou_guobao@zhouzidan
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name/description (query vehicle location and condition for Tika/TikaKey) matches the code and SKILL.md: the Python script calls the Tika open API (https://openapi.nokeeu.com/iot/v1/condition) and exposes options for reading position/condition. However, the registry metadata claims no required environment variables or primary credential while SKILL.md and query_vehicle.py explicitly rely on an App-generated API Key (recommended env var TIKA_API_KEY) and other token env vars. That omission in metadata is inconsistent and may mislead users about what sensitive access is required.
Instruction Scope
SKILL.md and the included script instruct the agent/user to read environment variables and to read/write a local cache file at ~/.skill_carkey_cache.json. The README even provides an OpenClaw prompt that encourages pasting the API Key for automated configuration. These instructions involve handling and persisting sensitive credentials and accessing the user's home directory; this scope is expected for a local CLI but should be explicit in the skill metadata and clearly presented to users before any automated or remote submission of secrets.
Install Mechanism
There is no installer or remote download; this is an instruction/script-only skill that requires Python 3.6+. No packages are fetched during install and no external archives or unknown URLs are downloaded by an installer. That lowers install-time risk.
Credentials
Although the skill logically needs a Tika API key, the registry entry lists zero required env vars/credentials. The SKILL.md and query_vehicle.py reference TIKA_API_KEY and also mention TIKA_VEHICLE_TOKEN/TIKA_ACCESS_TOKEN in code — additional credential-like env vars that are not declared. The README/SKILL.md further suggests writing the API key into a local cache and even provides guidance for letting OpenClaw populate the credential. Requesting or storing high-sensitivity API keys without the metadata reflecting that requirement is disproportionate and may confuse permission/consent decisions.
Persistence & Privilege
The skill does not request always:true and does not modify other skills. It does, however, persist credentials to a cache file (~/.skill_carkey_cache.json) and attempts to restrict file permissions per README. Persisting a high-sensitivity API key to disk is a privilege that users should be aware of; this behavior is legitimate for a CLI utility but should be opt-in and clearly communicated (the SKILL.md does describe it).
What to consider before installing
Before installing or running this skill: (1) recognize it requires a Tika API Key (TIKA_API_KEY) even though the registry metadata doesn't declare it — do not paste or upload that key to third parties unless you trust the skill and host; (2) the script will read env vars and can write a cache file (~/.skill_carkey_cache.json) containing your API key — prefer using a short-lived environment variable and avoid saving persistent keys on shared machines; (3) inspect the script (query_vehicle.py) yourself or verify the publisher and API endpoints (openapi.nokeeu.com / tikakey/chengqu sites) before providing credentials; (4) if you plan to let OpenClaw auto-configure credentials, be aware that this will store secrets on the agent host—only do this on a trusted machine; (5) ask the maintainer or registry to update the skill metadata to list required env vars/primary credential explicitly (TIKA_API_KEY) so permission prompts are accurate.Like a lobster shell, security has layers — review code before you run it.
latestvk9752wvstge37yv92191k1hba984vhxj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.