Name: workable
Rating: 64 (1 reviews)
Author: membranedev

workable

Workable integration. Manage Persons, Organizations, Deals, Leads, Projects, Users and more. Use when the user wants to interact with Workable data.

Quality

76%

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

Quality

Content

82%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 highly actionable, command-driven integration guide with strong validation feedback loops in the connection workflow. Its weaknesses are mild: a small amount of conceptual over-explanation and broken step numbering ('Step 2', '1b') that hurts workflow sequencing.

Suggestions

Fix the step numbering: label the connection steps consistently (1, 1b/2, ...) and either add an explicit 'Step 2' header or reword the 'skip to Step 2' reference to point at a real section.

Trim the introductory 'Workable is an applicant tracking system...' paragraph and 'auth plumbing' prose, which explain concepts Claude already knows.

Consider moving the 16-row Popular actions table to a references file (e.g. ACTIONS.md) and keeping a short representative subset inline for a cleaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, command-driven reference material, with minor over-explanation such as the opening 'Workable is an applicant tracking system (ATS)...' paragraph and padding like 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flag examples and a proxy-options table, and a Popular actions table covering the common cases.	5 / 5
Workflow Clarity	The connection flow has explicit validation checkpoints and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, error-state handling), but step numbering is incoherent — 'skip to Step 2' references a Step 2 that is never labeled and '1b' appears without a '1'/'1a'.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files to navigate; the bulky 16-row Popular actions table is inline rather than split to a reference, a minor organization gap that keeps it below 5.	4 / 5
	Total	17 / 20 Passed

Description

71%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 the Workable niche and includes an explicit Use-when clause, with good entity-level specificity. Its main weakness is trigger-term quality: the listed entities are not the natural vocabulary Workable users employ, and concrete domain synonyms are absent.

Suggestions

Add natural Workable user terms (candidates, jobs, applicants, hiring pipeline, ATS) to the trigger vocabulary so the description matches what users actually say.

Tighten the Use-when clause with concrete trigger phrases, e.g. 'Use when the user wants to manage candidates, jobs, or applications in Workable.'

Replace the generic 'Manage ... and more' with a few specific action verbs (e.g. create, update, move, disqualify candidates) to reach comprehensive specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete entity domains — 'Manage Persons, Organizations, Deals, Leads, Projects, Users' — giving concrete capability coverage, though the single generic verb 'Manage' and the 'and more' hedge leave minor gaps versus comprehensive.	4 / 5
Completeness	Both 'what' ('Workable integration. Manage Persons, Organizations, Deals, Leads, Projects, Users') and 'when' ('Use when the user wants to interact with Workable data') are explicit, but the when-clause lacks concrete trigger phrases that would lift it to 5.	4 / 5
Trigger Term Quality	The strong natural keyword 'Workable' appears and a Use-when clause is present, but the listed entities (Persons, Deals, Leads) are not the terms Workable users naturally say; the common domain synonyms (candidates, jobs, applicants, hiring, ATS) are missing.	3 / 5
Distinctiveness Conflict Risk	'Workable integration' names a specific product niche with a distinct trigger ('Workable'), giving minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/workable/SKILL.md
Commit: f484c82

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