Kimai Time Tracking

PassAudited by ClawScan on May 10, 2026.

Overview

This appears to be a legitimate Kimai API helper, but it is powerful because it can use your Kimai token to change or delete time-tracking and administrative data.

Install only if you want an agent to operate your Kimai instance. Provide a least-privilege Kimai token, review the full script if available, and require explicit approval for deletes, exports that lock entries, user/team changes, or other administrative actions.

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.

What this means

If given a broad or admin Kimai token, the agent could perform sensitive account and business-data operations within Kimai.

Why it was flagged

The skill requires a Kimai bearer token and documents permissions that may allow reading, editing, deleting, and administering business time-tracking data.

Skill content
`KIMAI_API_TOKEN` - Bearer token for authentication ... `delete_customer` ... `delete_project` ... `delete_team` ... `view_user`
Recommendation

Use a least-privilege Kimai token limited to the operations you want the agent to perform, and avoid admin/delete permissions unless needed.

What this means

A mistaken ID or overly broad instruction could delete or alter Kimai records, including cascading customer/project/activity/timesheet data.

Why it was flagged

The CLI exposes destructive Kimai API actions. It has an interactive confirmation by default, but the presence of a force path means destructive calls should be explicitly controlled.

Skill content
if not args.force and not confirm_deletion('customer', args.id, cascade): ... client.delete(f'customers/{args.id}')
Recommendation

Require explicit user confirmation for destructive or administrative actions, verify IDs before running them, and do not use force/no-confirm behavior unless the user specifically asked for it.

What this means

Users may not see the token requirement or provenance from registry metadata alone.

Why it was flagged

The registry metadata does not provide provenance and does not declare the credential/environment requirements that the SKILL.md and script use.

Skill content
Source: unknown; Homepage: none ... Required env vars: none ... Primary credential: none
Recommendation

Review the included script before use, verify it came from a trusted source, and treat the Kimai token as sensitive.