v1.0.0

TickTick CLI

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 4:44 AM.

Analysis

This is a coherent TickTick task-management CLI, but it grants and stores TickTick OAuth access, so users should protect the credential file and review write commands.

GuidanceBefore installing, be comfortable granting TickTick task read/write access. Use a trusted machine, protect ~/.clawdbot/credentials/ticktick-cli/config.json, and be careful with update, complete, abandon, and batch-abandon commands because they can change your TickTick account.

Findings (3)

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.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityLowConfidenceHighStatusNote

scripts/ticktick.ts

.command("batch-abandon <taskIds...>") ... .description("Abandon multiple tasks in a single API call")

The CLI exposes write operations, including a bulk task-status change. This matches the stated task-management purpose, but accidental or overly broad agent use could change multiple tasks.

User impactA mistaken command could complete, update, create, or abandon tasks/projects in the connected TickTick account.

RecommendationReview write and batch commands before running them, prefer project filters and task IDs, and require user approval for agent-initiated mutations if your workflow supports it.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

metadata

Source: unknown; Homepage: none

The registry metadata does not identify an upstream source or homepage, which reduces provenance transparency even though the supplied code is coherent.

User impactUsers have less external context for verifying the publisher, update history, or upstream project before trusting OAuth access.

RecommendationInstall only if you trust the registry publisher, and consider pinning/reviewing dependencies before use.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityMediumConfidenceHighStatusNote

SKILL.md

Tokens are stored in `~/.clawdbot/credentials/ticktick-cli/config.json` ... Credentials are stored in plaintext.

The skill persistently stores TickTick OAuth client credentials and tokens locally. This is disclosed and purpose-aligned, but the file represents sensitive account access.

User impactAnyone who can read the credential file may be able to access or refresh TickTick task permissions for this app.

RecommendationUse this only on a trusted machine, protect the credential file, and revoke the TickTick developer app or remove the config if you stop using the skill.