Name: clockify
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

clockify

Clockify integration. Manage Users, Reports. Use when the user wants to interact with Clockify 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/clockify/SKILL.md

Quality

Content

71%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 highly actionable with concrete, copy-paste-ready CLI commands and a clear connection workflow with state-checkpoint feedback loops. Its main weaknesses are some unnecessary background explanation up front and a monolithic structure with no progressive disclosure into separate reference files.

Suggestions

Trim the opening paragraph that explains what Clockify is; Claude already knows the product, so lead directly with the integration workflow.

Move the 20-row Popular actions table and the detailed connection state-machine handling into a separate reference file (e.g. ACTIONS.md) and link to it from SKILL.md so the main file stays an overview.

Add a short verification/error-handling note after the `membrane action run` example (e.g. check the `output` field and handle non-READY connection states) to close the workflow-clarity validation gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Clockify is ("Clockify is a time tracking tool used by teams and individuals...") and mildly promotional Membrane phrasing ("so you can focus on the integration logic rather than auth plumbing") are unnecessary explanations Claude does not need, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides copy-paste-ready executable commands for every phase (install, login, connection ensure, action list, action run, request) plus a 20-row table mapping action names to keys and a full table of proxy flags, fully covering the common cases per the top anchor.	5 / 5
Workflow Clarity	The connect-and-poll workflow is clearly sequenced with explicit state checkpoints and a feedback loop (poll state, handle CLIENT_ACTION_REQUIRED, re-poll), but the action-running phase lacks a verification or error-handling step after execution, leaving a minor validation gap below the 5 anchor.	4 / 5
Progressive Disclosure	The file is well-organized with clear section headers, but it is a monolithic ~165-line SKILL.md with no external reference files; detailed reference material such as the 20-row actions table and the connection state machine is inlined rather than split into one-level-deep referenced files, matching the anchor where content that should be separate is inline.	3 / 5
	Total	15 / 20 Passed

Description

62%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 is brand-specific and provides both a what and an explicit when-clause, but its actions are generic ("Manage") and its trigger phrasing is vague rather than enumerating concrete Clockify use cases. It is solid but could be sharpened with more specific verbs and trigger terms.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List, create, and update time entries, users, projects, and reports in Clockify."

Expand the when-clause with concrete trigger phrases: "Use when the user wants to track time, manage Clockify time entries, projects, tasks, or pull time tracking reports."

Add natural synonyms users say ("time tracking", "timesheet", "time entries") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Clockify) and two areas ("Manage Users, Reports"), but the verb "Manage" is generic rather than a concrete action like list/create/update, matching the anchor that names the domain with 1-2 actions that are not comprehensive.	3 / 5
Completeness	It answers both what ("Clockify integration. Manage Users, Reports.") and when ("Use when the user wants to interact with Clockify data"), but the when-clause is generic rather than concrete trigger phrases, so it sits above the missing-when anchor but below the explicit-concrete-triggers anchor.	4 / 5
Trigger Term Quality	It includes the brand term "Clockify" plus "Users" and "Reports", but misses core natural terms users would say such as "time tracking", "time entries", "projects", or "tasks", fitting the anchor with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The brand-specific "Clockify" naming gives it a clear niche with minimal conflict risk, but the generic trigger "interact with Clockify data" keeps it just below the distinct-triggers anchor at 5.	4 / 5
	Total	14 / 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/clockify/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.