4todo

What This Skill Does

The 4todo skill integrates OpenClaw with 4to.do, a task management platform built around the Eisenhower Matrix. It allows users to capture, prioritize, and complete tasks directly through natural language chat. The skill handles workspace organization, recurring task management, and urgency filtering without exposing the user to complex API calls or technical IDs. By mapping Eisenhower quadrants to plain language, it turns your chat interface into a highly efficient productivity dashboard.

Installation

To install, run: clawhub install openclaw/skills/skills/blackstorm/4todo.

Security is paramount: never paste your API token directly into the chat. Instead, inject the FOURTODO_API_TOKEN into your environment. For local host runs, add the token to your ~/.openclaw/openclaw.json file under skills.entries.4todo.env. For sandboxed sessions, ensure the token is provided via your Docker environment settings. If the token is missing, the skill will prompt you to configure it via your OpenClaw settings.

Use Cases

• Daily Planning: Review tasks categorized by urgency and importance to decide what to tackle first.
• Task Capture: Quickly dump brain-space tasks into specific workspaces (e.g., 'Add call Mom to Personal workspace as urgent and important').
• Routine Maintenance: Set up recurring chores like bill payments or weekly reviews, ensuring they surface at the right time.
• Workspace Switching: Seamlessly toggle between different projects like 'Work', 'Home', or 'Side Hustles' to maintain context.

Example Prompts

1. "What do I have marked as urgent and important in my Work workspace?"
2. "Add a new task: Submit expense report to the Work workspace under important but not urgent."
3. "Mark the weekly review task in my Home workspace as complete."

Tips & Limitations

• Terminology: The skill uses plain language for Eisenhower quadrants. You can say 'urgent and important', 'important not urgent', 'urgent not important', or 'neither'.
• Ambiguity: If you have multiple workspaces with similar names, the skill will ask for clarification.
• Non-Technical Focus: The skill is designed to hide backend technical IDs. If you ever need to debug a sync issue, you can ask for the technical details, but by default, it will only show names for a cleaner experience.