Tessl • The management layer for AI agent skills

SkillPublic

clinchpad

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

Quality

69%

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

Quality

Content

68%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.

A well-structured, command-dense skill body that is immediately actionable for CLI setup, connection management, action discovery, and proxy fallback. Its main weaknesses are the missing validation guidance for destructive operations (capping workflow clarity), placeholder-only run examples, and a few dangling step references.

Suggestions

Add a validation checkpoint before destructive operations, e.g., 'Before delete-lead, run get-lead to confirm the correct ID and confirm the pipeline with the user' — this lifts the workflow_clarity cap of 3.

Fix the sequence numbering: 'skip to Step 2' points to a step label that doesn't exist, and section '1b' appears without a '1a'/Step 1 heading — relabel these as an explicit numbered step sequence.

Include one fully concrete action example with real values (e.g., membrane action run create-lead --connectionId=... --input '{"name": "Acme", "pipeline_id": "..."}') so the run pattern is copy-paste ready end to end.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and compact flag/action tables with no explanation of concepts Claude already knows. Minor filler remains, such as the 'ClinchPad is a lightweight CRM' intro paragraph, the empty nested Overview bullets, and the vacuous line 'Use action names and parameters as needed.'	4 / 5
Actionability	Concrete, copy-paste-ready commands cover install, login, connection ensure, state polling, action search, action run, and proxy requests, plus a flags table and a 20-action catalog. It stops short of anchor 5 because no example uses real values — '--input '{"key": "value"}'' and CONNECTION_ID are placeholders with no end-to-end example (e.g., an actual create-lead call).	4 / 5
Workflow Clarity	The install → auth → connection → state-handling → discovery → run sequence exists with good poll/recovery loops for BUILDING and CLIENT_ACTION_REQUIRED states, but the skill exposes destructive operations (delete-lead, delete-contact, delete-organization, delete-product) with no validation/verification guidance, capping this dimension at 3 per the rubric. The broken 'skip to Step 2' reference (no Step 2 exists) and an orphaned '1b' heading add sequence gaps.	3 / 5
Progressive Disclosure	No bundle files exist; the body uses clear sections and delegates full action discovery to 'membrane action list' rather than inlining an exhaustive API reference, which is appropriate layering. The 20-row Popular actions table and proxy flags table are borderline bulk reference inlined in a ~165-line SKILL.md, keeping it below anchor 5.	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 correctly names the ClinchPad niche and includes an explicit 'Use when' trigger clause, giving it adequate completeness and distinctiveness. However, the capability statement is generic ('Manage data, records, and automate workflows') and the natural vocabulary of the domain — CRM, leads, deals, contacts, pipeline — is entirely absent.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete actions, e.g., 'Create, update, and delete leads, contacts, organizations, products, and deals in ClinchPad pipelines.'

Add the natural trigger terms users would say — CRM, leads, deals, sales pipeline, contacts — e.g., 'Use when the user mentions ClinchPad, their CRM, leads, deals, or sales pipeline.'

Dimension	Reasoning	Score
Specificity	'Manage data, records, and automate workflows' names the ClinchPad domain but the actions are generic — no concrete operations (leads, deals, contacts, pipelines) appear. This matches anchor 2 ('names the domain but actions are minimal or generic'); it is above 1 because the domain is named, and below 3 because no concrete ClinchPad action is listed.	2 / 5
Completeness	Both parts are explicitly present: 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with ClinchPad data'), so the missing-trigger cap of 3 does not apply. It fits anchor 4 ('both what and when; when could be more explicit'); not 5 because the 'what' is generic and the 'when' lacks concrete trigger phrases like leads or deals.	4 / 5
Trigger Term Quality	'ClinchPad' and 'interact with ClinchPad data' are relevant natural terms, but the common phrases a user would actually say — CRM, leads, deals, contacts, sales pipeline — are all missing. This matches anchor 3 ('some relevant keywords but missing common variations or synonyms'); not 4 because several natural synonyms are absent.	3 / 5
Distinctiveness Conflict Risk	'ClinchPad integration' and 'interact with ClinchPad data' establish a clear niche app with distinct triggers, matching anchor 4 ('mostly distinct; minor overlap risk'). Not 5 because the generic 'Manage data, records' framing could overlap with other CRM/data-management skills when the user doesn't name ClinchPad.	4 / 5
	Total	13 / 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/clinchpad/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.

clinchpad

Table of Contents

Is this your skill?