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

clubworx

Clubworx integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clubworx 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/clubworx/SKILL.md

Quality

Content

78%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 executable CLI commands and clear state-driven connection workflow, but it loses points for inlining a large actions/flags catalog rather than offloading it to reference files, and for lacking explicit verification steps after destructive action runs. No bundle files exist, so structure is single-file only.

Suggestions

Add an explicit verification step after mutating actions (e.g. re-run the corresponding list/get action to confirm the create/update/cancel took effect), since the rubric caps workflow_clarity at 3 for batch/destructive ops without validation.

Move the popular-actions table and proxy flag reference into separate reference files (e.g. ACTIONS.md, PROXY.md) with one-level-deep links from SKILL.md to improve progressive disclosure.

Trim the Clubworx marketing overview ('all-in-one club management software... used by gym, fitness, and martial arts studios') which is context Claude already knows and does not aid execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with executable snippets and tables, but the Clubworx overview block and some explanatory prose around the connection lifecycle add mild padding that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a concrete popular-actions table and full flag reference covering the common cases.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling guidance, but operations that mutate data (create/update/cancel member, booking, prospect) have no explicit validation or verification checkpoint after running.	4 / 5
Progressive Disclosure	It is well sectioned within a single file, but everything lives inline in SKILL.md with no separate reference files or one-level-deep links despite a sizable popular-actions table and proxy flag reference that could be split out.	3 / 5
	Total	16 / 20 Passed

Description

73%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 names a distinct niche (Clubworx) and includes an explicit 'Use when' clause, satisfying the completeness threshold, but its action language ('Manage data, records, and automate workflows') is generic and could be sharpened with concrete operations. Trigger quality is good but leans almost entirely on the product name.

Suggestions

Replace generic verbs with concrete operations drawn from the body, e.g. 'Create and update members, manage bookings and memberships, list events and payments'.

Add natural synonyms users actually say beyond the product name, such as 'gym', 'fitness studio', 'memberships', or 'bookings'.

Make the 'Use when' clause enumerate a few concrete triggers (e.g. 'when the user wants to manage members, bookings, attendance, or billing in Clubworx').

Dimension	Reasoning	Score
Specificity	Names the domain (Clubworx) and a couple of generic actions ('Manage data, records, and automate workflows'), but these are abstract rather than concrete operations like 'create members' or 'list payments' found in the body.	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Clubworx data'); the 'when' is concrete enough to clear the cap but is somewhat generic rather than enumerating specific triggers.	4 / 5
Trigger Term Quality	'interact with Clubworx data' and 'Manage data, records' include reasonably natural user phrasings, though it relies almost entirely on the product name itself and lacks synonyms a user might say (e.g. 'members', 'bookings', 'gym', 'membership').	4 / 5
Distinctiveness Conflict Risk	The proper noun 'Clubworx' gives it a clear niche with minimal overlap risk against other skills, and the trigger is tied to that specific application.	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/clubworx/SKILL.md
Commit: f484c82

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