taskleef
Analysis
The skill matches its stated Taskleef purpose, but it installs an unpinned external CLI that will use your API key and can change or delete your tasks.
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.
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.
"install":[{"id":"todo-cli","kind":"download","url":"https://raw.githubusercontent.com/Xatter/taskleef/main/taskleef-cli/todo","bins":["todo"]The skill installs the executable CLI from a mutable raw GitHub main-branch URL, with no pinned version, checksum, or included source in the artifact set. That CLI is central to all account actions.
todo delete <title-or-id> ... todo project delete <project-name-or-id> ... todo board clear <column-name-or-id> ... Title match: Partial, case-insensitive title match
The documented tool can delete or clear Taskleef items and supports partial title matching, which is useful but can be risky if an item name is ambiguous.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
The CLI uses the `TASKLEEF_API_KEY` environment variable. Users can get their API key from https://taskleef.com.
The skill requires a Taskleef API key, which is expected for the service integration but grants account access to whichever CLI is run.
