Name: clinchpad
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

clinchpad

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

Quality

66%

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

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 content is highly actionable with concrete CLI commands and a well-sequenced, state-aware connection workflow. Its main weaknesses are some introductory marketing prose and the large inlined actions table that could be split into a reference file.

Suggestions

Trim the introductory marketing paragraph and redundant overview tree to respect token budget.

Add a brief validation/confirmation note before destructive actions (delete-lead, delete-contact, etc.) to strengthen the workflow's feedback loop.

Consider moving the popular-actions table into a separate references file and linking to it from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly command- and table-driven, but opens with marketing prose ('lightweight CRM... close more deals') and a somewhat redundant overview tree that Claude does not need, pulling it below efficient.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) with a flags table and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The install-to-run sequence is clear with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling guidance, but destructive delete-* actions lack explicit validation or confirmation nudges, leaving a minor gap.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and a single self-contained file, but the 20-row actions table is inlined reference-style content that could live in a separate file given the overall length.	4 / 5
	Total	16 / 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 identifies the product and includes a 'Use when' trigger clause, satisfying the completeness bar. Its weakness is vague action verbs ('manage data', 'automate workflows') instead of concrete ClinchPad operations and missing natural trigger terms like leads, deals, and contacts.

Suggestions

Replace generic verbs with concrete ClinchPad operations, e.g. 'Manage leads, contacts, deals, and pipelines in ClinchPad'.

Add natural trigger terms users would say, such as 'leads', 'deals', 'contacts', 'sales pipeline', or 'CRM'.

Tighten the 'Use when' clause to name specific scenarios, e.g. 'Use when the user wants to manage ClinchPad leads, deals, or contacts.'

Dimension	Reasoning	Score
Specificity	Names the ClinchPad domain but the listed actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete API operations like leads, contacts, or deals.	2 / 5
Completeness	States both what the skill does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with ClinchPad data'), though the 'when' clause is generic.	4 / 5
Trigger Term Quality	Includes the product name 'ClinchPad' and 'data'/'records', but misses the natural phrases a user would say such as 'leads', 'deals', 'contacts', or 'CRM'.	3 / 5
Distinctiveness Conflict Risk	The named product 'ClinchPad' gives it a clear niche with minimal conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap with other CRM-like skills.	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
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.