Name: desktime
Rating: 58.4 (1 reviews)
Author: membranedev

desktime

DeskTime integration. Manage Users, Organizations, Projects, Tasks, Reports, Absences. Use when the user wants to interact with DeskTime data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/desktime/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The content is actionable and well-structured, built around concrete executable CLI commands. Its main weaknesses are mild verbosity, a repeated discovery command, and an absence of validation/verification checkpoints for data-mutating operations.

Suggestions

Add explicit validation steps, e.g. after running a mutating action, check the JSON output for errors and confirm the change before proceeding.

Trim the opening 'what is DeskTime' paragraph and deduplicate the action-discovery command by defining it once and referencing it.

Consider moving the proxy flag reference table into a separate REFERENCE.md and linking to it to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and brief guidance, but the opening paragraph ('DeskTime is a time tracking software...') explains what DeskTime is and the discovery command is repeated across sections, so it could be tightened.	3 / 5
Actionability	It provides concrete, copy-paste-ready npx CLI commands with flags for login, connect, action list/run, and proxy requests, with only minor gaps such as a generic placeholder for the proxy endpoint path.	4 / 5
Workflow Clarity	A sequence exists (setup -> connect -> discover actions -> run/proxy), but there are no explicit validation or verification checkpoints after running actions; since the skill can mutate DeskTime data, the missing feedback loop caps this at 3.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly signaled sections (Overview, Working with DeskTime, Popular actions, Best practices) with no nested references, though at over 100 lines some reference material (e.g. the proxy flag table) could arguably live in a separate file.	4 / 5
	Total	14 / 20 Passed

Description

71%Weight 40%Scale 1-5

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

The description clearly identifies a distinct niche (DeskTime) and lists comprehensive managed entities with an explicit 'Use when' trigger. It is held back from a top score by a single generic verb and limited trigger-term variation.

Suggestions

Replace the single verb 'Manage' with a few distinct concrete actions (e.g., 'list, create, and update Users, Projects, and Tasks; pull Reports and Absences').

Broaden the trigger clause with natural synonyms, e.g. 'Use when the user wants to track time, pull DeskTime reports, or manage DeskTime users and projects.'

Dimension	Reasoning	Score
Specificity	Names the DeskTime domain and lists several concrete managed entities ('Users, Organizations, Projects, Tasks, Reports, Absences'), but all share a single generic verb 'Manage' rather than distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	It states both what ('Manage Users, Organizations, Projects, Tasks, Reports, Absences') and when ('Use when the user wants to interact with DeskTime data'), but the trigger clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger 'when the user wants to interact with DeskTime data' is natural but offers only the keyword 'DeskTime' with no synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	'DeskTime integration' targets a specific named SaaS product with distinct triggers, creating a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/desktime/SKILL.md
Commit: f484c82

Reviewed: ~17 hours 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.