Name: clicktime
Rating: 53.6 (1 reviews)
Author: membranedev

clicktime

ClickTime integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClickTime data.

Quality

60%

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/clicktime/SKILL.md

Quality

Content

63%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 body is a strong, actionable CLI reference with a clearly sequenced connection workflow and good error-state coverage. Its main weaknesses are inlined bulk content (overview list, actions table) that should be split into reference files and some verbosity that could be trimmed.

Suggestions

Move the popular-actions table and the 28-item overview list into separate reference files (e.g. ACTIONS.md, ENTITIES.md) and link to them from the body.

Add a validation/check step before destructive actions (delete-time-entry, delete-job), e.g. confirm the target ID via a get-* call before deleting.

Trim explanatory prose such as 'so you can focus on the integration logic rather than auth plumbing' and the lead sentence defining what ClickTime is.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient command references, but the 28-item overview bullet list and the large popular-actions table include padding that could be trimmed, and phrases like 'so you can focus on the integration logic rather than auth plumbing' over-explain.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxying with a flags table, leaving only minor gaps (e.g. placeholder substitution in action run examples).	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop, though destructive actions like delete-time-entry and delete-job are listed without explicit pre-validation guidance.	4 / 5
Progressive Disclosure	The body is well-sectioned but everything is inlined in a single ~180-line file; the long overview list and popular-actions table are content that could live in separate reference files, and no external references are signaled.	3 / 5
	Total	14 / 20 Passed

Description

57%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 correctly includes a 'Use when...' trigger and names the specific product, giving it solid completeness and distinctiveness. Its weakness is generic action language ('manage data, records, automate workflows') that lacks concrete ClickTime-specific operations.

Suggestions

Replace generic verbs with concrete ClickTime actions, e.g. 'Create and update time entries, jobs, clients, and users; run time reports'.

Add natural trigger synonyms such as 'timesheets', 'time tracking', or 'ClickTime API' to broaden keyword coverage.

Tighten the 'when' clause with concrete triggers, e.g. 'Use when the user wants to track time, manage ClickTime projects/clients, or pull time reports'.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the ClickTime domain but the actions are generic verbs rather than concrete ClickTime operations, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with ClickTime data"), though the what could be more concrete.	4 / 5
Trigger Term Quality	"ClickTime" is the key natural keyword and "interact with ClickTime data" is a plausible user phrase, but common synonyms and variations are missing, fitting the anchor for some relevant keywords with gaps.	3 / 5
Distinctiveness Conflict Risk	The named product "ClickTime" and the trigger "interact with ClickTime data" carve a clear niche with minimal conflict risk, though the surrounding verbs remain somewhat broad.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

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