mcpField
T
ticktick-cli

ticktick-cli

github.com/flexoidProductivity443 installsUpdated 37w ago
Repository

About ticktick-cli

ticktick-cli is a skill for running TickTick workflows through terminal commands. It guides agents handling tasks and related data, with structured output, identifier resolution before changes, and post-write verification.

Key features

  1. 01Run TickTick operations from the CLI
  2. 02Prefer JSON output
  3. 03Resolve names to IDs before changes
  4. 04Verify results after writes
  5. 05Require confirmation for destructive actions

Use cases

  1. 01Query and update tasks from a terminal
  2. 02Scope task changes to a project ID
  3. 03Set task dates and verify the result
  4. 04Confirm before deleting projects or tags

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/flexoid/ticktick-cli --skill ticktick-cli

After installing, type/ticktick-cliin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
columns.md
folders.md
habits.md
projects.md
setup-and-auth.md
tags.md
tasks.md
troubleshooting.md
user-focus-sync.md

Details

From the project README

TickTick CLI

Use this skill to execute TickTick workflows directly from terminal commands with deterministic output handling.

Execution Policy

  1. Execute the requested ticktick ... command first. Do not run version or tool-presence pre-checks.
  2. If execution fails because CLI is missing, load references/setup-and-auth.md and follow install recovery flow.
  3. If execution fails due auth/config issues, load references/setup-and-auth.md and run guided auth before retrying the original command.
  4. Keep auth recovery CLI-only. Do not improvise custom SDK/Python token exchange scripts.
  5. Use --help only as recovery when a command fails due unknown flags/arguments or missing required params.

Defaults

  • Prefer --json on all data commands and parse structured output.
  • Resolve names to IDs before mutations; never guess identifiers.
  • Apply read -> mutate -> verify for every write operation.
  • Prefer explicit --project PROJECT_ID for task mutations when deterministic behavior matters.
  • Use explicit date formats (YYYY-MM-DD for date-only fields, ISO datetime for timed fields).

Safety

  • Require explicit user confirmation before install/environment changes.
  • Never use risky system-install flags unless the user explicitly asks for that path.
  • Never print secrets or tokens in user-visible output.
  • Require explicit user confirmation before destructive operations:
    • tasks delete
    • projects delete
    • folders delete
    • columns delete
    • tags delete
    • tags merge
    • habits delete

Reference Map

Load only the file needed for the active area.

Comments

Markdown supported