Name: clockwork
Rating: 52.8 (1 reviews)
Author: membranedev

clockwork

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/clockwork/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 body is a solid, executable guide to the Membrane CLI workflow with concrete commands and a good connection-state feedback loop. Weaknesses are duplicated/mislabeled sections, marketing padding, and missing validation checkpoints before destructive action runs or proxy mutations.

Suggestions

Add a validation checkpoint before destructive operations: for POST/PUT/DELETE actions or proxy requests, inspect the action output or run a dry read first and confirm with the user before mutating.

Fix the step numbering — label the connect flow 'Step 1'/'Step 2' explicitly (and add the missing '1a') so the 'skip to Step 2' reference resolves.

Trim marketing fluff such as 'so you can focus on the integration logic rather than auth plumbing' and de-duplicate the action-list command between 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes marketing fluff ('so you can focus on the integration logic rather than auth plumbing') and duplicates the action-list command in both 'Searching for actions' and 'Popular actions'.	3 / 5
Actionability	It provides copy-paste-ready membrane commands for install, auth, connect, search, run, and proxy with a flag table, but uses generic placeholders and the 'Popular actions' section lists no actual actions, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow has a real feedback loop (poll READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but running actions and proxying POST/PUT/DELETE requests are potentially destructive yet lack validation or confirmation checkpoints, capping the score at 3.	3 / 5
Progressive Disclosure	Content is organized into clear sections with no nested references, though step numbering is inconsistent ('skip to Step 2' with no labeled Step 2, a '1b' with no '1a') and no bundle files are used.	4 / 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 is adequate: it names a specific integration and includes an explicit 'Use when' trigger clause, satisfying both what and when. Its main weakness is generic action phrasing ('manage data, records') and thin trigger-term coverage with no synonyms.

Suggestions

Replace generic verbs with concrete Clockwork actions, e.g. 'Schedule meetings, set task reminders, sync calendars, and log time entries'.

Expand trigger terms with natural synonyms users would say, e.g. 'Use when the user mentions Clockwork, scheduling meetings, task reminders, time tracking, or calendar sync'.

Tie the 'when' clause to specific Clockwork nouns (meetings, tasks, time entries, tags) to sharpen distinctiveness from other productivity/data skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Clockwork integration') but its actions are generic ('Manage data, records, and automate workflows') rather than concrete like 'extract' or 'fill forms', fitting the 'minimal or generic actions' anchor below the midpoint.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Clockwork data'), though the trigger clause is generic rather than specific.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Clockwork data' surfaces the relevant keyword 'Clockwork', but offers no synonyms or natural variations a user might say, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The named app 'Clockwork' gives it a clear niche with minimal conflict risk, but the generic 'manage data, records' phrasing leaves minor overlap with other data-management skills.	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/clockwork/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.