Toggl Cli

What This Skill Does

The Toggl Cli skill provides a powerful command-line interface for interacting with your Toggl Track workspace. It enables seamless time tracking, project management, and reporting directly from your development environment. Whether you need to start a timer, list recent time entries, manage projects, or organize tasks, this skill wraps the Toggl API into intuitive, easily accessible commands. It supports full CRUD operations for time entries, projects, clients, tags, tasks, workspaces, and organizations.

Installation

To add this skill to your system, use the following installation command in your terminal: clawhub install openclaw/skills/skills/froemic/toggl-cli. Once installed, clone the repository from GitHub, run npm install, npm run build, and npm link to make the toggl command globally available. Ensure you have your TOGGL_API_TOKEN configured as an environment variable in your .bashrc, .zshrc, or the .env file within your agent configuration directory.

Use Cases

This skill is perfect for developers, freelancers, and project managers who want to eliminate context switching between their IDE and the web dashboard. Use it to automate time entry logging as you switch tasks, generate reports for billing cycles, keep your project metadata synced with your actual work, and manage your client base efficiently without leaving your terminal.

Example Prompts

1. "Start a new timer named 'Backend API Refactoring' and add a tag labeled 'urgent'."
2. "List all my time entries from this week and provide a summary of the total hours spent on the 'OpenClaw' project."
3. "Create a new project named 'Mobile App Migration' with the color blue and associate it with 'Acme Corp' client."

Tips & Limitations

To maximize productivity, alias the commands to shorter snippets like 't' for toggl. Be aware that the tool requires an active internet connection to communicate with the Toggl servers. Since it relies on the official API, ensure your environment variables are correctly exported before running commands. For complex operations involving large data sets or date ranges, always verify the output format to ensure compatibility with your reporting tools. Avoid running mass delete commands without verifying the IDs first, as the CLI performs these actions immediately.