TickTick API

**Quick judgment**: This skill is a solid, focused TickTick integration that covers the core CRUD actions for tasks and projects. It’s best suited for users who already rely on TickTick and want their assistant to help manage a simple to-do workflow (list, add with due dates, complete, delete). It does not expose the full richness of TickTick (e.g., advanced reminders, recurring rules, subtasks) and requires manual OAuth setup, which slightly limits accessibility and compatibility. **Strengths** - Good coverage of essential task management actions (list/add/complete/delete) tied directly to TickTick’s official Open API endpoints. - Simple, predictable command set that closely mirrors the underlying REST API. - Supports due dates and project-level organization, enabling more structured task workflows than a plain text to-do list. - Reasonable performance is expected, as operations are straightforward HTTP calls to a production-grade API. **Risks & limitations** - **Destructive operations** (complete/delete) can permanently alter or remove tasks; the assistant should confirm user intent before invoking them and avoid bulk deletions without explicit instructions. - **OAuth setup complexity**: users must create a TickTick developer app, configure a redirect URI, and run `ticktick-setup` locally. This may be a barrier for non-technical users and can reduce overall compatibility. - **Partial feature coverage**: the documented interface doesn’t clearly expose advanced TickTick features such as recurring tasks, reminders beyond a due date, tags management via the CLI, or subtasks—so it’s better for straightforward task lists than complex workflows. - **External dependency**: reliability and performance depend on TickTick’s API uptime and any future API changes; if endpoints or auth flows change, the skill may degrade until updated. - **Time and timezone handling**: due dates are ISO-like strings; incorrect or ambiguous times/timezones could cause reminders at unintended times if not normalized. **Recommended scenarios** - The user explicitly says they use TickTick and wants the assistant to manage tasks there ("add this to my TickTick," "show my TickTick tasks," "mark this TickTick task done"). - The user wants a lightweight, cloud-synced to-do list integration with basic operations rather than a deeply customized task system. - Situations where the assistant needs to **reflect** and **update** the user’s real to-do system (cross-device) rather than maintain a separate internal checklist. **Less suitable scenarios** - Users who do not have a TickTick account or are unwilling/unable to perform the OAuth setup steps. - Workflows requiring rich TickTick features (complex recurrence rules, nested subtasks, granular reminders, tags management) that are not clearly surfaced in the described interface. - High-risk, high-volume bulk modifications of tasks (e.g., mass deletes) without strong confirmation and context, due to safety concerns around irreversible changes.