Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
WizNote
v1.0.0WizNote private API connector for reading and writing notes via RESTful API. Use when the user mentions "为知笔记", "WizNote", "Wiz", or needs to search, create,...
⭐ 0· 64·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description and the included Python scripts are coherent with a WizNote private API connector (login, CRUD, search, folder ops). However the skill registry metadata claims 'Required env vars: none' while SKILL.md and the code clearly require WIZ_USER and WIZ_ENDPOINT (WIZ_TOKEN optional/used). Also the package does not declare the required 'requests' dependency even though the code exits if requests is missing. These metadata omissions are inconsistent with the skill's stated purpose and will cause surprise or runtime failure.
Instruction Scope
SKILL.md limits actions to interacting with WizNote endpoints, setting WIZ_ environment variables, and describes retries and error handling — all within the stated purpose. It does instruct storing tokens in environment variables and suggests .env or os.environ edits; the code also sets WIZ_KB_GUID in os.environ at login and writes log files (wiznote.log, wiznote_error.log) to disk. No instructions or code were found that read unrelated system files or call external endpoints outside the specified WizNote API.
Install Mechanism
There is no install spec while the package includes multiple Python scripts that depend on the 'requests' library. The code aborts if requests is missing. The absence of a declared dependency (requests) in the registry metadata or an install step is a coherence/operational issue — it increases the chance of runtime errors and unexpected manual steps for the user.
Credentials
The required/used environment variables (WIZ_ENDPOINT, WIZ_USER, optional WIZ_TOKEN, and the code sets WIZ_KB_GUID) are reasonable for a private API connector. But the registry metadata says no env vars required while the code enforces WIZ_USER and uses WIZ_ENDPOINT — a mismatch. The skill asks users to store credentials/tokens in environment variables or .env files; this is functional but has security implications (tokens in files/logs). No unrelated credentials (AWS, GitHub, etc.) are requested.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide configs. It writes local log files and sets process environment variables (WIZ_KB_GUID) after login; these are limited, expected behaviors for a client library. Autonomous invocation is permitted (platform default) but that is not in itself a new risk here.
What to consider before installing
This package largely does what it says (WizNote private API client), but there are several inconsistencies you should consider before installing:
- Metadata mismatch: The registry lists no required environment variables or dependencies, but SKILL.md and the code require WIZ_ENDPOINT and WIZ_USER (WIZ_TOKEN optional) and the Python 'requests' package. Expect to set these and to pip-install requests manually unless the platform does it for you.
- Secrets handling: The skill advises storing tokens in environment variables or .env files and the code writes logs to the current working directory. Avoid placing long-lived production credentials in easily readable files; use limited-scope tokens if possible and ensure logs do not retain secrets.
- Source trust: Homepage is missing and the skill owner is unfamiliar; review the included Python files yourself or run the skill in an isolated/test environment before giving real credentials.
- Operational checks: Verify WIZ_ENDPOINT is reachable from your agent, and that the private WizNote deployment uses the endpoints/ports described (80 or 9269). Test with a throwaway account/token first.
If you want to proceed: (1) inspect the scripts for any additional network calls, (2) run in an isolated container or sandbox, (3) do not provide high-privilege credentials until you have validated behavior. If the registry should be authoritative, ask the maintainer to update metadata to declare required env vars and dependencies.Like a lobster shell, security has layers — review code before you run it.
apivk979h17dejc4jnz82dekabqgq583v3qrlatestvk979h17dejc4jnz82dekabqgq583v3qrnotesvk979h17dejc4jnz82dekabqgq583v3qr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
