Manage Notion checklist blocks inside a page (no database required). Use when the user has plain to-do blocks and wants to list tasks, add tasks, and mark ta...

This skill's code appears to do only Notion API operations (list/add/mark tasks), which is consistent with its description — but the registry metadata is incomplete. Before installing: 1) Confirm you will provide NOTION_TOKEN and NOTION_TASKS_PAGE_ID (the SKILL.md requires them). 2) Ensure Node and curl are available in the runtime (the script calls node -e). 3) Use a Notion integration token with the minimal scopes and only share the specific page with that integration; avoid supplying broader organization tokens. 4) Ask the skill author or registry to update the metadata to declare the required env vars and binaries (this mismatch is the main coherence problem). 5) Inspect the script yourself (it is included) and only proceed if you are comfortable with the token being used to call api.notion.com; rotate the token after testing if you are concerned.

Type: OpenClaw Skill Name: notion-tasks-blocks Version: 1.0.0 The OpenClaw skill 'notion-tasks-blocks' is benign. It correctly uses environment variables (`NOTION_TOKEN`, `NOTION_TASKS_PAGE_ID`) for authentication with the Notion API and performs actions (list, add, mark done/undone) as described. User input for task text and index is handled safely by JSON encoding via `node -e` or numerical conversion, preventing shell or JSON injection. All network calls are directed to `api.notion.com`, and there is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts in `SKILL.md`.