Name: clockwork-recruiting
Rating: 56.8 (1 reviews)
Author: membranedev

clockwork-recruiting

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

Quality

65%

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

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 concrete, executable Membrane CLI guidance with a clear connection state machine and feedback loop, scoring well on actionability and workflow clarity. Conciseness is the weakest dimension due to product background explanation and a duplicated discovery section, and progressive disclosure has minor inline bulk. It is a solid, usable skill with light trimming opportunities.

Suggestions

Remove the introductory ATS product description and the 'auth plumbing' filler so the body assumes Claude's competence and starts with what to do.

Resolve the duplicated action-discovery content (the 'Searching for actions' and 'Popular actions' sections both show action list) and fix the 'Step 2'/'1b' numbering for a coherent single workflow.

Add an explicit validation/check step before running batch or destructive actions (e.g. confirm connection state is READY and review inputSchema before action run).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens by explaining what Clockwork Recruiting is and includes mild fluff ('so you can focus on the integration logic rather than auth plumbing') plus a duplicated action-discovery section; trimmable enough to keep it at anchor 3 rather than 4.	3 / 5
Actionability	Executable commands are provided throughout (install, login, connection ensure/get, action list/run, request proxy) with a flag table, but placeholder values like <actionId> and CONNECTION_ID and a duplicated search section leave minor gaps short of fully copy-paste-ready 5.	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with a state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling, but the 'Step 2'/'1b' labeling is muddled and there is no explicit validation before batch or destructive action runs, capping it just below 5.	4 / 5
Progressive Disclosure	As a single self-contained file with no bundle references, it is well-organized by clear headers and easy to navigate, but the fully inlined clientAction schema and flag table could be split out, leaving minor organization gaps short of a clean 5.	4 / 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 answers both what and when with an explicit trigger clause and a clear product niche, but its actions are generic and trigger-term coverage is thin. Third-person voice is used correctly. It lands in the mid-to-upper range with room for more specific capability language.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete capabilities like 'search candidates, create job postings, update application stages, and run recruiting reports'.

Broaden the trigger phrase to mirror natural user requests, e.g. 'Use when the user mentions candidates, job applications, hiring pipelines, or Clockwork Recruiting tasks'.

Add a file-format or synonym hint (e.g. referencing ATS, recruiting, or candidate data) to strengthen distinctiveness against adjacent skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Clockwork Recruiting integration') and 1-2 actions ('Manage data, records, and automate workflows'), but those actions are generic rather than comprehensive; not enough specific concrete actions for a 4.	3 / 5
Completeness	Both 'what' (Clockwork Recruiting integration managing data/records and automating workflows) and an explicit 'when' ('Use when the user wants to interact with Clockwork Recruiting data') are present, though the 'when' trigger could be more specific; not a 5 because concrete trigger phrases are thin.	4 / 5
Trigger Term Quality	Relevant keywords like 'Clockwork Recruiting', 'data', 'records', and 'workflows' are present, but natural synonyms and common variations users would say are missing; sits at anchor 3, not the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product gives a clear niche with minimal conflict risk, but the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap with adjacent ATS/CRM skills; not distinct enough for a 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/clockwork-recruiting/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.