Tessl • The management layer for AI agent skills

SkillPublic

clubworx

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

Quality

73%

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

75%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 strongly actionable CLI guide with executable commands, a well-handled connection state machine, and good single-file organization. Its main weaknesses are padded introductory sections that assume less of Claude than needed and a dangling 'Step 2' reference that breaks an otherwise clear workflow.

Suggestions

Trim the 'Clubworx Overview' intro and bare domain-object bullet list, or fold them into a single line of domain context that informs action discovery.

Define or remove the undefined 'Step 2' references — label the 'Searching for actions' section as Step 2 or drop the step numbering.

Fix the 'This will burn less tokens' phrasing in Best practices (should be 'use fewer tokens') and tighten that section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient copy-paste commands, but contains unnecessary padding Claude does not need: the marketing-style intro ("Clubworx is an all-in-one club management software. It's used by gym, fitness, and martial arts studios..."), the bare domain-object bullet list under 'Clubworx Overview' with no usage guidance, and the 'Agent Types' aside. Not 4 because these are several padded sections rather than minor instances.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout: 'npm install -g @membranehq/cli@latest', 'membrane login --tenant --clientName=<agentType>', 'membrane connection ensure "https://www.clubworx.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input ...', plus a concrete proxy flags table and a popular-actions table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with state-machine checkpoints (poll with --wait, handle CLIENT_ACTION_REQUIRED and its clientAction fields, check error for CONFIGURATION_ERROR/SETUP_FAILED) — real validation and error recovery. Not 5 because 'Step 2' is referenced twice ('skip to Step 2') but never defined or labeled, leaving a navigation gap in the sequence.	4 / 5
Progressive Disclosure	A single-file skill (no references/, scripts/, or assets/ bundle) with well-organized headers — install, authentication, connection, action search/run, proxy, best practices — each reasonably placed. Not 5 because of the dangling 'Step 2' references and minor ordering gaps (e.g. the popular-actions table sits between the search and run sections).	4 / 5
	Total	16 / 20 Passed

Description

61%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 distinctive and has both a 'what' and 'use when' clause, but the capability statement is generic ('manage data, records, and automate workflows') and trigger coverage relies solely on the product name. Listing concrete operations and natural synonyms would materially improve it.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions, e.g. 'Create and update members, prospects, and bookings; manage memberships, events, and payments'.

Add natural trigger terms users would actually say: memberships, bookings, billing, payments, prospects, classes, gym or studio management.

Make the 'Use when' clause less circular — e.g. 'Use when the user mentions Clubworx, members, bookings, or membership billing'.

Dimension	Reasoning	Score
Specificity	"Clubworx integration. Manage data, records, and automate workflows" names the domain but the actions are entirely generic — no concrete operations (create members, manage bookings, list payments, bill memberships) are listed. It is not 1 because a domain and action verbs are present, and not 3 because no specific concrete action is named.	2 / 5
Completeness	Both 'what' ("Manage data, records, and automate workflows") and 'when' ("Use when the user wants to interact with Clubworx data") are explicitly present. Not 5 because the 'when' clause is circular (interact with Clubworx data) and lacks concrete trigger phrases; not 3 because the 'when' is not missing or merely implied.	4 / 5
Trigger Term Quality	"Clubworx" is a relevant, specific keyword, but the description omits natural variations users would say such as memberships, bookings, billing, payments, prospects, or gym/studio management. It is not 4 because coverage is limited to a single product name with no synonyms.	3 / 5
Distinctiveness Conflict Risk	"Clubworx integration" ... "interact with Clubworx data" occupies a clear niche with a distinct product-name trigger; minimal risk of firing for the wrong skill.	5 / 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/clubworx/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

clubworx

Table of Contents

Is this your skill?