4todo
Manage 4todo (4to.do) from chat. Capture tasks, prioritize with the Eisenhower Matrix, reorder, complete, and manage recurring tasks across workspaces.
- License 许可
- MIT
- 最近更新
- 2026-06-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- 4todo
- description
- Manage 4todo (4to.do) from chat. Capture tasks, prioritize with the Eisenhower Matrix, reorder, complete, and manage recurring tasks across workspaces.
03 SKILL.md 正文
4todo
4to.do Eisenhower Matrix To‑Do List
Goal
- Use
curlto 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
curlmust be available onPATH(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.
- Do not show
- Quadrants:
- In chat, prefer plain language: “urgent & important”, “important (not urgent)”, “urgent (not important)”, “neither”.
- Use
IU | IN | NU | NNinternally 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) Weekly review (recurring, Fridays)
Store / Inject the Token in OpenClaw (recommended)
OpenClaw can inject environment variables only for the duration of an agent run (then restores the original env), which helps keep secrets out of prompts.
Recommended (production): set FOURTODO_API_TOKEN in your Gateway process environment using your hosting provider’s secret store, and do not store tokens in chat logs.
Host runs (not sandboxed): use skills.entries
Edit ~/.openclaw/openclaw.json:
{
skills: {
entries: {
"4todo": {
enabled: true,
env: {
FOURTODO_API_TOKEN: "YOUR_4TODO_API_TOKEN"
}
}
}
}
}
Notes:
skills.entries.<skill>.envis injected only if the variable is not already set.
Sandboxed sessions: use agents.defaults.sandbox.docker.env
When a session is sandboxed, skill env injection does not propagate into the Docker container. Provide the token via Docker env:
{
agents: {
defaults: {
sandbox: {
docker: {
env: {
FOURTODO_API_TOKEN: "YOUR_4TODO_API_TOKEN"
}
}
}
}
}
}
Request Conventions
- Every request must include
Authorization: Bearer <token>. - Requests with a JSON body must include
Content-Type: application/json. GET /todosrequires aworkspacequery parameter.- Quadrants:
IU | IN | NU | NN(internal).
Workflow (recommended order)
Copy this checklist and keep it updated while executing:
Task checklist:
- [ ] List workspaces (pick `ws_...`)
- [ ] List todos for that workspace
- [ ] Perform the requested mutation (create / complete / reorder / recurring)
- [ ] Re-fetch to verify the change
GET /workspaces: pick a targetws_...(usually the default workspace).GET /todos?workspace=ws_...: fetch todos (grouped by quadrant).- Create:
POST /todos. - Complete:
POST /todos/:id/complete(idempotent). - Reorder / move quadrant:
POST /todos/reorder. - Recurring todos: use the
/recurring-todosendpoints.
HTTP Examples (curl)
This skill intentionally uses curl for maximum portability across OSes and environments.
Notes:
- HTTPS only (
https://4to.do/api/v0). - Always pass the token via
FOURTODO_API_TOKEN(never paste tokens into chat).
curl -sS -H "Authorization: Bearer $FOURTODO_API_TOKEN" -H "Accept: application/json" "https://4to.do/api/v0/workspaces"
curl -sS -H "Authorization: Bearer $FOURTODO_API_TOKEN" -H "Accept: application/json" "https://4to.do/api/v0/todos?workspace=ws_...&show=all"
curl -sS -X POST -H "Authorization: Bearer $FOURTODO_API_TOKEN" -H "Accept: application/json" -H "Content-Type: application/json" --data-raw '{"name":"...","quadrant":"IU","workspace_id":"ws_..."}' "https://4to.do/api/v0/todos"
curl -sS -X POST -H "Authorization: Bearer $FOURTODO_API_TOKEN" -H "Accept: application/json" "https://4to.do/api/v0/todos/todo_.../complete"
curl -sS -X POST -H "Authorization: Bearer $FOURTODO_API_TOKEN" -H "Accept: application/json" -H "Content-Type: application/json" --data-raw '{"moved_todo_id":"todo_...","previous_todo_id":"todo_...","next_todo_id":null,"quadrant":"IN"}' "https://4to.do/api/v0/todos/reorder"
Note: if moved_todo_id starts with rec_todo_, the API updates only the recurring todo quadrant and ignores previous_todo_id/next_todo_id.
Common Error Handling (agent guidance)
401 token_expired / invalid_token: stop retrying; ask the user to create a new token in 4todo settings and update OpenClaw config.402 WORKSPACE_RESTRICTED: the workspace is read-only; do not retry mutations; switch workspace or prompt user to upgrade/unlock.429 rate_limited: honorRetry-After/X-RateLimit-*and back off before retry.400 Invalid quadrant type: ensure quadrant is one ofIU|IN|NU|NN.
Reference
- Full API doc bundled with this skill:
{baseDir}/references/api_v0.md
04 同仓库更多 Skills
crowd-prompting
A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.
ceaser
Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).
ceaser-send
Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir/UltraHonk zero-knowledge proofs.
dilemm-ai
Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).
moldium
Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.
arxiv-paper-reviews
Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.