Ticktick Linux

Manage TickTick tasks (add, list, complete) via the local `tickrs` CLI.

Security Scan

The skill's requirements and runtime instructions are consistent with a thin wrapper around the local tickrs CLI, but it hard-codes an absolute user path and asks for sensitive TickTick credentials — verify those before installing.

Purpose & Capability

The name/description (manage TickTick via tickrs) matches the declared requirements: the SKILL.md only invokes the tickrs CLI and the required env vars (TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET) are plausible for TickTick authentication. One oddity: the required binary is an absolute path (/home/david/.cargo/bin/tickrs) rather than a generic 'tickrs' on PATH, which is brittle and unusual but not itself malicious.

Instruction Scope

SKILL.md only contains commands that call the local tickrs binary to list/create/complete tasks and to run tickrs init for authentication. It does not instruct reading other files, scanning the filesystem, or sending data to unrelated endpoints. It does assume the binary lives at the hard-coded path.

Install Mechanism

There is no install spec (instruction-only), so nothing is downloaded or written by the skill itself. This minimizes install-time risk. The skill relies entirely on an existing local tickrs binary.

Credentials

Requesting TICKTICK_CLIENT_ID and TICKTICK_CLIENT_SECRET is proportionate for a TickTick integration, but these are sensitive secrets. The skill declares only these two env vars and does not reference unrelated credentials. Note: providing a client secret to a skill (or placing it in environment) has risk — verify you trust the binary and understand where tokens will be stored.

Persistence & Privilege

always is false and the skill has no install steps or code that attempts to modify agent/system configuration. It does not request persistent privileges or modify other skills.

Assessment

This skill appears to be a thin wrapper that runs your local tickrs CLI. Before installing: 1) Confirm you have the tickrs binary and that it's trustworthy (inspect source/release and the installed binary). Note the SKILL expects it at /home/david/.cargo/bin/tickrs — if your binary is elsewhere, the skill will fail or you should edit the path. 2) Be cautious with TICKTICK_CLIENT_ID and TICKTICK_CLIENT_SECRET — only set them if you understand how you manage secrets (avoid pasting them into chat). Alternatively run `~/.cargo/bin/tickrs init` manually to authenticate and let the CLI store tokens locally instead of exporting long-lived secrets. 3) Because this is instruction-only, there is no code to audit in the skill bundle; the main risk surface is the local tickrs binary and how it handles credentials.

TickTick

Manage tasks in TickTick.

Prerequisite: You must authenticate the CLI first by running: ~/.cargo/bin/tickrs init

Tools

ticktick_list

List tasks from the default project (Inbox) or a specific project.

• Parameters:

  • project (string, optional): Project name to filter by.
  • status (string, optional): Filter by status (incomplete [default], complete).

• Command:

  /home/david/.cargo/bin/tickrs task list --json \
    {{#if project}}--project-name "{{project}}"{{/if}} \
    {{#if status}}--status {{status}}{{/if}}
  

ticktick_create

Create a new task.

• Parameters:

  • title (string, required): The task title.
  • content (string, optional): Description or notes.
  • date (string, optional): Natural language date (e.g., "today", "tomorrow at 5pm", "next friday").
  • project (string, optional): Project name to add to.
  • priority (string, optional): none, low, medium, high.

• Command:

  /home/david/.cargo/bin/tickrs task create --json \
    --title "{{title}}" \
    {{#if content}}--content "{{content}}"{{/if}} \
    {{#if date}}--date "{{date}}"{{/if}} \
    {{#if project}}--project-name "{{project}}"{{/if}} \
    {{#if priority}}--priority {{priority}}{{/if}}
  

ticktick_complete

Mark a task as complete by ID (get ID from ticktick_list).

• Parameters:

  • id (string, required): The Task ID.

• Command:

  /home/david/.cargo/bin/tickrs task complete "{{id}}" --json
  

ticktick_projects

List all projects.

• Command:

  /home/david/.cargo/bin/tickrs project list --json