v1.0.0

Kimai Time Tracking

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 5:29 AM.

Analysis

This looks like a legitimate Kimai integration, but it deserves review because it can use a Kimai API token to perform broad administrative and potentially irreversible business-data changes.

GuidanceBefore installing, confirm you want an agent to manage Kimai records through the REST API. Use a dedicated least-privilege token, set KIMAI_BASE_URL only to your trusted Kimai instance, and require explicit human review for deletes, exports, invoice-related actions, user/team changes, or any command using force.

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

SeverityHighConfidenceMediumStatusConcern

scripts/kimai_cli.py

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

The code performs destructive API deletes and includes a force path that skips the interactive confirmation check.

User impactA mistaken or over-permissive invocation could delete Kimai business records, including linked project, activity, or timesheet data.

RecommendationUse this only with explicit user approval for destructive actions, avoid force deletion unless certain, and test administrative commands on non-production data first.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceMediumStatusNote

metadata

Source: unknown; Homepage: none; Install specifications: No install spec

The artifact is self-contained and static scan is clean, but provenance information is limited.

User impactUsers have less external context for verifying who authored or maintains the integration.

RecommendationReview the included script before use and prefer trusted sources or pinned, auditable releases for production workflows.

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

SeverityHighConfidenceHighStatusConcern

SKILL.md

`KIMAI_API_TOKEN` - Bearer token for authentication ... `delete_customer`, `delete_project`, `delete_activity`, `delete_team`, `view_user`

The skill requires a bearer token and lists permissions that can view users and delete major Kimai objects.

User impactIf given an admin or overly broad token, the skill can read and modify sensitive time-tracking, customer, project, team, and invoice-related data.

RecommendationCreate a dedicated Kimai API token with only the permissions needed for the intended workflow, and avoid granting admin/delete permissions unless required.