ticktick-automation
by ComposioHQticktick-automation helps agents automate TickTick tasks through Composio Rube MCP. It covers setup, required tool discovery with RUBE_SEARCH_TOOLS, TickTick connection checks, and safe task workflow usage.
This skill scores 70/100, which means it is acceptable for directory listing but should be presented as a lightweight Rube MCP workflow guide rather than a full-featured automation package. Directory users get enough information to know when to install it—TickTick automation through Composio/Rube—and agents get a usable trigger/setup pattern, but adoption still depends on runtime tool discovery and external toolkit behavior.
- Clearly scoped to automating TickTick operations through Composio's TickTick toolkit via Rube MCP.
- Provides concrete prerequisites and setup flow: add the Rube MCP endpoint, verify RUBE_SEARCH_TOOLS, manage the TickTick connection, and confirm ACTIVE status.
- Includes an operational discovery pattern that tells agents to search tools for the current schema before executing workflows, reducing schema guesswork.
- Execution depends on Rube MCP discovery at runtime rather than bundled TickTick tool schemas or examples, so agents must call RUBE_SEARCH_TOOLS before acting.
- Repository evidence is thin: only SKILL.md is present, with no scripts, reference files, README, or install command in the skill file.
Overview of ticktick-automation skill
What ticktick-automation does
ticktick-automation is a Claude skill for automating TickTick task workflows through Composio’s Rube MCP server. It helps an agent discover the current TickTick tool schemas, confirm the user’s TickTick connection, and then perform task operations such as creating, updating, searching, or organizing tasks through the available Rube tools.
Best fit for this skill
Use the ticktick-automation skill if you already manage work in TickTick and want an AI agent to turn natural-language instructions into reliable task actions. It is most useful for Workflow Automation cases such as capturing meeting follow-ups, converting plans into TickTick tasks, bulk-editing task metadata, or maintaining projects and lists from a conversation.
What makes it different from a generic prompt
The main differentiator is its required “search tools first” pattern. Instead of assuming fixed TickTick API fields, the skill instructs the agent to call RUBE_SEARCH_TOOLS before execution so it can use the latest Composio tool names, schemas, and pitfalls. That matters because MCP tool schemas can change, and task automation fails quickly when fields, project IDs, due-date formats, or connection state are guessed.
Important adoption constraints
This skill depends on Rube MCP and an active TickTick connection. It is not a standalone TickTick API wrapper, and the repository contains only SKILL.md, with no helper scripts or bundled references. Install it when you want an agent-facing workflow pattern, not a complete local automation app.
How to Use ticktick-automation skill
ticktick-automation install context
Install the skill in a compatible Claude skills environment, for example:
npx skills add ComposioHQ/awesome-claude-skills --skill ticktick-automation
Then add https://rube.app/mcp as an MCP server in your client configuration. The upstream skill states that no API key is needed for the MCP endpoint itself, but you still need to authorize TickTick through Rube. Confirm RUBE_SEARCH_TOOLS is available before expecting the skill to work.
Required setup before running workflows
Before asking the agent to change TickTick data, have it check the connection state:
- Call
RUBE_SEARCH_TOOLSfor the specific TickTick use case. - Call
RUBE_MANAGE_CONNECTIONSwith toolkitticktick. - If the TickTick connection is not
ACTIVE, open the returned auth link and complete authorization. - Re-check connection status before creating, editing, or deleting tasks.
This setup step is not optional. Without it, the agent may write a plausible plan but fail at execution because the TickTick toolkit is unavailable or unauthenticated.
Strong prompts for ticktick-automation usage
A weak prompt is: “Add my tasks to TickTick.”
A stronger prompt gives the skill the execution context it needs:
“Use ticktick-automation to create TickTick tasks for the following project. First search Rube tools for the current TickTick task creation schema, confirm my TickTick connection is active, then create tasks in the Product Launch project. Use due dates where provided, mark priority as high only for launch-blocking items, and summarize what was created before making any destructive changes.”
Useful input details include project/list name, task titles, due dates, priority rules, tags, recurrence, timezone, whether subtasks are needed, and whether the agent may update existing tasks or only create new ones.
Files to read first in the repository
Start with composio-skills/ticktick-automation/SKILL.md. It contains the full operational contract: prerequisites, Rube MCP setup, tool discovery, connection management, and the core workflow pattern. There are no extra README.md, scripts/, resources/, or references/ folders in this skill path, so the install decision should be based on the single skill file and your MCP environment.
ticktick-automation skill FAQ
Is ticktick-automation beginner-friendly?
Yes, if you are comfortable connecting an MCP server and authorizing a third-party toolkit. The skill’s workflow is simple, but beginners should avoid giving broad write permissions in prompts until they have tested creation and search actions on low-risk tasks.
Can I use it without Rube MCP?
No. The ticktick-automation skill is explicitly built around Rube MCP tools such as RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS. If your client cannot use MCP servers, this skill will not execute TickTick actions.
When should I not use this skill?
Do not use it for offline task planning, unsupported TickTick features, or workflows that require guaranteed transactional behavior across many task edits. Also avoid it when you cannot review changes before bulk updates or deletions. In those cases, ask the agent to draft a task plan first and execute only after approval.
How does it compare with ordinary TickTick prompts?
An ordinary prompt can organize a task list in text, but it cannot reliably discover live tool schemas or check your TickTick connection. The ticktick-automation skill adds a safer execution pattern for real TickTick operations by requiring tool discovery before action.
How to Improve ticktick-automation skill
Improve ticktick-automation results with clearer inputs
For better outputs, specify the target TickTick project, whether to create or update tasks, acceptable due-date interpretation, priority mapping, tag rules, and confirmation requirements. Example: “Do not delete or close tasks. If a matching task already exists, ask before updating it.” These constraints reduce accidental duplicates and unsafe edits.
Common failure modes to watch
The most common issues are inactive TickTick authorization, skipped tool discovery, ambiguous project names, missing dates, and prompts that mix planning with immediate execution. If the first run fails, ask the agent to report which Rube tool was selected, what schema it found, and which required fields were missing.
Iterate after the first automation run
After execution, request a concise audit: tasks created, tasks skipped, fields inferred, and any items needing manual review. For recurring workflows, save the successful prompt pattern with your preferred project names, tags, priority rules, and confirmation policy so future ticktick-automation usage is more consistent.
Repository-level improvements worth adding
The skill would be stronger with a short README.md, example prompts for common TickTick workflows, and non-destructive test scenarios. A small reference section showing create, search, update, and connection-check patterns would also help users evaluate the ticktick-automation install path before connecting their real task account.