Kaiten
Analysis
This looks like a legitimate Kaiten integration, but it can use your Kaiten token to change or delete project-board data, so it should be reviewed before installation.
Findings (4)
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.
update-card) ... _patch "/cards/$1" "$2" ... delete-card) ... _del "/cards/$1"
The helper implements direct mutation and deletion of Kaiten cards using the user's API token, with no artifact-backed confirmation gate or rollback guidance.
Required env vars: none ... Primary credential: none
The registry metadata under-declares runtime requirements even though the skill instructions and script require KAITEN_TOKEN, KAITEN_DOMAIN, bash, curl, and python3.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
AUTH="Authorization: Bearer ${KAITEN_TOKEN}"The skill uses a bearer API token to act against the Kaiten account; this is expected for the integration but grants delegated account authority.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
State file: `SKILL_DIR/scripts/kaiten-state.json` ... When creating a card without explicit board → use `default_board_id`, fall back to `last_board_id`
The skill stores persistent board context and reuses it for future operations, which is useful but can affect where later cards are created.
