← Back to Skills Marketplace
luciorenovato

Notion Tasks Blocks

by luciorenovato · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
553
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install notion-tasks-blocks
Description
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...
README (SKILL.md)

notion-tasks-blocks

Use this skill for Notion pages that contain to_do blocks (checklist items), not databases.

Required env vars

  • NOTION_TOKEN (secret_...)
  • NOTION_TASKS_PAGE_ID (page id that contains the task blocks)

Command wrapper

bash {baseDir}/scripts/notion_tasks_blocks.sh \x3Ccommand> [args]

Commands:

  • list → list current to-do blocks with index and done status
  • add "\x3Ctext>" → append new unchecked to-do block to the page
  • done \x3Cindex> → mark indexed task as checked
  • undo \x3Cindex> → mark indexed task as unchecked

Notes

  • Indexes come from list.
  • Works only for top-level to_do blocks on the page.
  • If Notion returns permission errors, share the page with your integration.
Usage Guidance
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.
Capability Analysis
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`.
Capability Assessment
Purpose & Capability
The script implements listing/adding/checking Notion to_do blocks via api.notion.com which aligns with the skill name and description. However the registry/manifest claims no required env vars or binaries while the SKILL.md and script require NOTION_TOKEN and NOTION_TASKS_PAGE_ID (and runtime tools like node and curl). The declared metadata is incomplete.
Instruction Scope
SKILL.md instructs only Notion-related actions (list/add/done/undo) and the script sends requests only to api.notion.com. The instructions and script do not read unrelated files, call other endpoints, or access extra environment variables.
Install Mechanism
No install spec (instruction-only with an included script) — low install risk. Nothing is downloaded from third-party URLs and no archives are extracted. However the script relies on node for JSON handling; this dependency is not declared in the registry metadata.
Credentials
The runtime requires NOTION_TOKEN and NOTION_TASKS_PAGE_ID which are appropriate for Notion API access, but the registry lists no required env vars. Also NOTION_TOKEN is a secret-like credential and users should ensure it has minimal scopes and is only granted to the relevant page/integration.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system settings, and will only act when invoked. It does perform API calls under provided credentials, which is expected for this purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install notion-tasks-blocks
  3. After installation, invoke the skill by name or use /notion-tasks-blocks
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of notion-tasks-blocks skill: - Manage Notion to-do blocks inside a page—no database required. - List, add, mark as done, and undo checklist tasks via simple commands. - Requires Notion integration and page ID environment variables. - Supports only top-level to-do blocks on the specified page.
Metadata
Slug notion-tasks-blocks
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Notion Tasks Blocks?

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... It is an AI Agent Skill for Claude Code / OpenClaw, with 553 downloads so far.

How do I install Notion Tasks Blocks?

Run "/install notion-tasks-blocks" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Notion Tasks Blocks free?

Yes, Notion Tasks Blocks is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Notion Tasks Blocks support?

Notion Tasks Blocks is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Notion Tasks Blocks?

It is built and maintained by luciorenovato (@luciorenovato); the current version is v1.0.0.

💬 Comments