Ticktick CLI (Full Edition)
ReviewAudited by ClawScan on May 10, 2026.
Overview
This skill is a coherent TickTick CLI helper with disclosed account credentials, read access, and guarded mutations, but users should protect credentials and review write operations carefully.
Install only if you trust the TickTick CLI workflow. Keep TickTick credentials and .env files private, review IDs before any mutation, confirm destructive actions deliberately, and avoid running full-account sync unless you need that broad output.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone or any agent process with these values may be able to access or modify the user's TickTick data through the CLI.
The skill requires OAuth credentials plus username/password session credentials, which can authorize access to the user's TickTick account.
TickTick CLI requires both auth layers: - OAuth: `TICKTICK_CLIENT_ID`, `TICKTICK_CLIENT_SECRET`, `TICKTICK_REDIRECT_URI`, `TICKTICK_ACCESS_TOKEN` - Session: `TICKTICK_USERNAME`, `TICKTICK_PASSWORD`
Store credentials only in a trusted environment, avoid pasting secrets into chat when possible, rotate tokens if exposed, and keep the .env file private.
The agent can change tasks, projects, folders, columns, tags, and habits in the user's TickTick account when instructed.
The skill can perform account mutations and deletes through the CLI, but it documents safeguards such as read-before-write, verification, and confirmation for destructive operations.
Apply read -> mutate -> verify for every write operation. ... Require explicit user confirmation before destructive operations: - `tasks delete` - `projects delete` - `folders delete` - `columns delete` - `tags delete` - `tags merge` - `habits delete`
Review the target IDs and requested command before approving writes, and require explicit confirmation for deletes or merges.
Running sync may reveal detailed TickTick account contents in the session transcript or logs.
The sync command can expose a broad account-level payload to the agent context or user-visible output.
`sync --json`: emits raw full-account sync payload for diagnostics/export-style inspection.
Use full-account sync only when needed for diagnostics or export, and avoid sharing transcripts that contain sync output.
The behavior depends on the external package version fetched at install time.
The recovery flow installs the external ticktick-cli package without pinning a version, although it asks for permission and prefers an isolated virtualenv.
`.venv/bin/python -m pip install --upgrade ticktick-cli`
Approve installs explicitly, prefer a trusted package source, and consider pinning or reviewing the ticktick-cli version before use.
