Name: clockodo
Rating: 60 (1 reviews)
Author: membranedev

clockodo

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

Quality

70%

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

Quality

Content

75%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 copy-paste-ready Membrane CLI commands and a well-sequenced connection workflow, but it carries some redundant content and a small step-labeling inconsistency. Overall a strong, executable skill body.

Suggestions

Remove the redundant 'Popular actions' section or fold it into 'Searching for actions' to avoid repeating the action-list command.

Trim the introductory paragraph about Clockodo's business purpose (payroll, invoicing) since Claude can infer it; keep only the entity list and docs link.

Fix the step numbering: label the connection section 'Step 1' and add an explicit 'Step 2' header so the 'skip to Step 2' reference resolves.

Dimension	Reasoning	Score
Conciseness	Commands are mostly efficient, but the intro paragraph explaining Clockodo's business purpose (payroll, invoicing) and the redundant 'Popular actions' section repeating the search command from 'Searching for actions' add unnecessary tokens, fitting anchor 3 (mostly efficient with some unnecessary explanation).	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (membrane login, connection ensure, action run with JSON input, request with a complete flag table) that cover the common cases, matching anchor 5.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED branching), but step labels are inconsistent (a dangling 'Step 2' reference and an unlabeled '1a'), fitting anchor 4 (clear sequence, minor gaps) rather than anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist; the single file is well-organized into clear sections, tables, and code blocks with no nested references, but the redundancy and lack of any split-out reference material keep it at anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 names a distinct, uniquely-named integration and provides an explicit 'Use when' clause, but its capability list is generic and its trigger phrasing omits natural domain terms like 'time tracking' or 'timesheets'.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Track time, manage projects and customers, and generate reports' instead of 'Manage data, records, and automate workflows'.

Broaden the trigger clause with natural user phrasing: 'Use when the user wants to track time, manage timesheets, or interact with Clockodo data'.

Add a concrete trigger synonym (e.g. 'time tracking', 'timesheets') so the skill surfaces when users describe the task without naming Clockodo.

Dimension	Reasoning	Score
Specificity	Names the Clockodo domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; anchor 3 fits because it lists 1-2 actions without comprehensive coverage, and anchor 4 would require several specific actions.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Clockodo data') are present, but the when is generic rather than a concrete varied trigger phrase, so it fits anchor 4 not anchor 5.	4 / 5
Trigger Term Quality	The trigger 'interact with Clockodo data' relies on the app name but omits natural domain phrases users actually say like 'time tracking' or 'timesheets', matching anchor 3 (relevant keywords, missing common variations/synonyms).	3 / 5
Distinctiveness Conflict Risk	'Clockodo' is a uniquely-named SaaS product, giving the skill a clear niche with distinct triggers and minimal conflict risk against other skills, matching anchor 5.	5 / 5
	Total	15 / 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/clockodo/SKILL.md
Commit: f484c82

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