CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clockwork

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/clockwork/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers strongly executable CLI guidance with a well-handled connection-state feedback loop, and its structure is easy to navigate as a single-file skill. Its weaknesses are moderate verbosity (marketing filler and a vague overview line) and a broken step reference ('Step 2' is never defined) plus inconsistent CLI invocation styles.

Suggestions

Delete the marketing opener and filler sentences ('helps professionals and teams manage their time more efficiently', 'so you can focus on the integration logic rather than auth plumbing') and the empty line 'Use action names and parameters as needed.'

Fix the broken workflow numbering: 'skip to Step 2' references a heading that doesn't exist — rename '### Searching for actions' to '### Step 2: Searching for actions' or remove the step references.

Standardize CLI invocation (always 'membrane ...' or always 'npx @membranehq/cli ...') so commands are consistently copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is mostly command-driven and efficient, but includes padding Claude doesn't need: the marketing opener ('helps professionals and teams manage their time more efficiently'), 'so you can focus on the integration logic rather than auth plumbing', and the contentless line 'Use action names and parameters as needed.', fitting the 'mostly efficient but includes some unnecessary explanation' anchor.

3 / 5

Actionability

Nearly all guidance is copy-paste executable (install, login, connection ensure/get, action list/run, proxy flags table), but minor gaps remain: the undefined 'Step 2' reference, inconsistent 'membrane' vs 'npx @membranehq/cli' invocation styles, and one vague overview line, keeping it below the fully-executable anchor.

4 / 5

Workflow Clarity

The sequence (install → authenticate → connect → poll for readiness → search actions → run/proxy) is clear with a genuine feedback loop for BUILDING and CLIENT_ACTION_REQUIRED states, but the text tells the reader to 'skip to Step 2' when no Step 2 heading exists, and there is no validation before running actions that could mutate data.

4 / 5

Progressive Disclosure

The single-file skill is well-sectioned with clear headers, an external docs link, and appropriately inline tables; since no bundle files exist there is nothing to offload, but minor organization gaps (dangling step numbering, a redundant 'Popular actions' intro repeating the search command) keep it at the good-structure anchor rather than the clear-overview anchor.

4 / 5

Total

15

/

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 has the right structure (what + explicit 'Use when' clause) and is anchored by a distinct app name, but its capability statement is generic and its trigger vocabulary is limited to the app name itself. Users describing scheduling, calendar, or reminder needs in natural language would not activate this skill.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete capabilities, e.g. 'Schedule meetings, set task reminders, log time entries, and synchronize calendars in Clockwork'.

Expand the 'Use when' clause with natural trigger phrases: 'Use when the user mentions Clockwork, scheduling, calendar sync, meetings, reminders, or time tracking'.

State the concrete objects the skill works with (accounts, tasks, time entries, tags) in the description so the 'what' is specific rather than circular.

DimensionReasoningScore

Specificity

The description names the Clockwork domain but its actions — 'Manage data, records, and automate workflows' — are generic abstractions; no concrete operations like scheduling meetings, syncing calendars, or tracking time are stated, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2-concrete-actions anchor above it.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Clockwork data') are present, but the 'what' is vague and the 'when' is circular, so it does not reach the anchor-5 level of concrete trigger phrases.

4 / 5

Trigger Term Quality

'Clockwork' is a relevant trigger keyword, but every natural phrase a user would say for this tool's domain ('calendar', 'schedule a meeting', 'reminder', 'time entry') is missing, fitting the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The distinct app name 'Clockwork' gives a clear niche with minimal conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing overlaps with any data-management skill, keeping it below the clear-niche anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.