Agkan
PassAudited by ClawScan on May 1, 2026.
Overview
The visible artifacts describe a coherent task-management CLI helper with expected task-editing powers, but users should verify the external agkan CLI and be careful with delete/update actions.
This skill appears benign and purpose-aligned for managing agkan tasks. Before installing, make sure you trust the agkan CLI installed on your machine, and ask the agent to confirm before deleting tasks or making large task-board changes.
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.
An agent using the skill could update, re-tag, or delete tasks if the user asks it to manage the board.
The skill documents commands that can mutate or delete task-board records. This is aligned with the stated task-management purpose, but it can still affect project data if used on the wrong task ID.
agkan task update <id> --status in_progress ... agkan task delete <id>
Review task IDs and intended changes before destructive actions such as delete operations.
The skill itself does not add code, but its behavior depends on whichever agkan executable is present in the user's environment.
The skill relies on the external agkan CLI, but the artifact does not install, pin, or declare that binary. Users must supply and trust the local CLI themselves.
No install spec — this is an instruction-only skill.
Install agkan only from a trusted source and confirm the expected binary is on PATH before relying on this skill.
Incorrect or untrusted task metadata could influence future task selection or project workflow decisions.
The task database and metadata are persistent and may influence later agent workflows. This is expected for a task-management system, but users should be aware that stored task content can be reused later.
`agkan` is an SQLite-based CLI task management tool... Skills that select tasks for execution (e.g., `agkan-run`) read this value to determine which task to work on next.
Avoid storing secrets or untrusted instructions in task bodies or metadata, and review priorities/metadata before automated task selection.
