kimai-time-tracking

Complete Kimai time-tracking API integration. Manage timesheets, customers, projects, activities, teams, invoices and exports via REST API. Supports time tracking workflows, reporting, and administrative operations. Keywords - kimai, zeiterfassung, timesheet, tracking, project, customer, activity, invoice, export, timer, stunden

2.32x

Quality

80%

Does it follow best practices?

Impact

93%

2.32x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/0x7466/kimai-time-tracking/SKILL.md

Quality

Discovery

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description that clearly identifies the Kimai platform, lists comprehensive capabilities, and includes excellent trigger terms in both English and German. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The keyword list is a good practice but doesn't fully substitute for explicit trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Kimai, time tracking via Kimai API, or managing timesheets, customers, projects, or invoices in Kimai.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: manage timesheets, customers, projects, activities, teams, invoices and exports via REST API, plus time tracking workflows, reporting, and administrative operations.	3 / 3
Completeness	Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The keywords section partially compensates but doesn't constitute explicit 'when' guidance per the rubric.	2 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including both English and German keywords (kimai, zeiterfassung, stunden), plus domain-specific terms users would naturally say: timesheet, tracking, project, customer, activity, invoice, export, timer.	3 / 3
Distinctiveness Conflict Risk	Very clearly scoped to Kimai specifically as a named product with REST API integration. The combination of 'Kimai' + time-tracking + API creates a distinct niche unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent concrete CLI examples and well-sequenced workflows. Its main weakness is verbosity — the activation triggers, permission lists, HTTP error codes, and full CLI reference could be trimmed or split into separate files. The safety boundaries around destructive operations are well-handled with explicit confirmation requirements and cascade warnings.

Suggestions

Move the detailed CLI Tool Reference section to a separate REFERENCE.md file and link to it, keeping only the most common commands inline.

Remove or significantly trim the 'When to use' / 'Do NOT activate for' section and the API permissions list — these are routing/meta concerns that consume tokens without adding actionable value.

Remove the HTTP error codes table — Claude already knows standard HTTP status codes; only document Kimai-specific behaviors like the 409 overlap conflict.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some unnecessary sections like the lengthy 'When to use' activation triggers and 'Do NOT activate for' lists, which are more about routing than actionable content. The API permissions list and HTTP error codes are things Claude already knows. However, the CLI reference and workflow sections are reasonably efficient.	2 / 3
Actionability	The skill provides fully executable CLI commands with concrete arguments, specific flags, and realistic examples. Commands are copy-paste ready with real parameter values, and the hierarchical workflow (customer → project → activity) gives clear, concrete guidance for common operations.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced (Quick Time Tracking, Data Management, Export/Invoice). Destructive operations explicitly require confirmation, cascade effects are documented, and there's a --dry-run flag for testing. The validation section includes connectivity testing. The delete operations are clearly marked with warnings and confirmation requirements.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections, but it's quite long and monolithic. The CLI Tool Reference section alone is extensive and could be split into a separate reference file. The skill does reference an external API spec file and external docs, but the inline content could benefit from more aggressive splitting of the detailed command reference into a separate file.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: openclaw/skills
Commit: 07a4057

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.