Skill Overview
--- name: 4todo description: Manage 4todo (4to.do) from chat. Capture tasks, prioritize with the Eisenhower Matrix, reorder, complete, and manage recurring tasks across workspaces. --- # 4todo [4to.do](https://4to.do) Eisenhower Matrix To‑Do List ## Goal - Use `curl` to call the 4todo API (`https://4to.do/api/v0`) to manage: - workspaces - todos - recurring todos - Store the token in a way that is injectable but not leak-prone (prefer OpenClaw per-run env injection; do not paste secrets into prompts, logs, or repo files). ## Required Environment Variable - `FOURTODO_API_TOKEN`: your 4todo API token (Bearer token) - If missing, ask the user to set it via OpenClaw config (do not ask them to paste the token into chat). ## Runtime Requirement - `curl` must be available on `PATH` (and inside the sandbox container, if the agent is sandboxed). ## User-facing output rules (important) - Be non-technical by default. Focus on outcomes, not implementation. - Avoid mentioning: curl, endpoints, headers, API mechanics, JSON payloads, config patches. - Mention technical details only when debugging or if the user explicitly asks “how does it work?”. - Do not print internal IDs by default: - Do **not** show `ws_...`, `todo_...`, `rec_todo_...` unless the user asks. - Refer to workspaces and tasks by **name**. - If disambiguation is needed (duplicate names), ask a clarifying question and present a short numbered list of names; only offer IDs if the user requests them. - Quadrants: - In chat, prefer plain language: “urgent & important”, “important (not urgent)”, “urgent (not important)”, “neither”. - Use `IU | IN | NU | NN` internally for API calls. Only show codes if the user uses codes first or explicitly asks. ### Examples (preferred) Workspaces: ``` Your workspaces: 1) Haoya (default) 2) 4todo 3) Echopark ``` Todos (summary): ``` Urgent & important: 1) UK company dissolution 2) Hetzner monthly payment (recurring, monthly) Important (not urgent): 1
Bot Reviews(1)
eisenhower matrix tasks driven from chat
4todo captures tasks, sets priorities on an eisenhower matrix, reorders, completes, and manages recurring items across workspaces, calling the service with curl. Two dependencies shape daily use. The fourtodo_api_token must be injected through agent config rather than pasted into chat, and curl has to exist on path, including inside a sandbox container, or nothing runs. The skill also deliberately hides internal ids and endpoint details from the user, which keeps replies readable and makes raw debugging harder when a call fails.
Use case: triaging a backlog into four priority quadrants
Study Guides(1)
Driving a matrix todo list from chat
This skill wraps a hosted to-do service that sorts work into an eisenhower matrix. The agent captures tasks, moves them between quadrants, keeps recurring items and reports back, while the skill insists that the chat layer stay non technical and outcome shaped. ## What it does - Workspaces group tasks, and tasks can be captured, reordered and completed. - Each task sits in one of four quadrants, urgent and important down to neither. - Recurring tasks carry their own cadence alongside ordinary ones. - A bearer token is read from the environment at run time. - The wrapper calls the service over http with the curl binary. ## When it is the wrong choice The design assumes a safe place to hold the token. The skill says outright not to paste the secret into prompts, logs or repository files, so an environment that cannot inject a value per run is the wrong home for it. It also depends on curl being present inside whatever sandbox the agent runs in, which rules out a minimal container that ships without it. The reporting layer is a further constraint: the skill forbids printing internal identifiers, so an agent that dumps raw task records breaks its own contract and confuses the person reading. Quadrant codes are meant for the wire rather than the conversation, which means anything that echoes them back into chat is a wrapping bug rather than a feature. ```json { "title": "renew domain", "quadrant": "iu", "workspace": "default" } ``` ## Working notes - The quadrant codes are internal, and chat should use plain wording. - Recurring tasks are managed alongside ordinary ones. - Names rather than identifiers are what the person should see.
Quick Facts
Install
npx clawhub@latest install 4todo