Getnote Knowledge Master

This skill appears to implement the advertised Getnote workflow, but there are important inconsistencies you should resolve before installing or running it: 1) Manifest vs instructions mismatch: SKILL.md expects GETNOTE_API_KEY, GETNOTE_CLIENT_ID and auto‑reads openclaw.json, yet the published metadata declares no required env vars/config paths. Ask the author to update the manifest to list required env vars and any config files the skill will read. 2) Default knowledge base: The skill will default to topic_id eYzMmvnm for many operations (including writes). If you install/run it, verify where data will be stored and ensure you trust that remote KB. Explicitly confirm and, if possible, override the default KB before letting it perform writes. 3) CLI installation: The instructions recommend `npm install -g @getnote/cli` when missing. Installing global npm packages modifies the host environment. Only run this in a controlled environment and review the CLI package source or its homepage before installing. 4) Credentials and scope: Only provide GETNOTE_API_KEY (and client id) after confirming the API key's scope and the target endpoint (openapi.biji.com). Do not provide unrelated secrets. If possible, use a least-privilege API key or a test account. 5) Verification steps: Ask the author for a homepage/source repository and a clear privacy/data-flow statement (where content is uploaded, retention, who can access the KB). Test the skill in an isolated account and verify read/write behavior before using it on sensitive content. Given these inconsistencies (metadata omissions and surprising defaults), treat the skill as 'suspicious' until the author clarifies the declared env vars, config access, and default KB behavior.