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

salesmate

Salesmate integration. Manage Organizations, Pipelines, Users, Filters, Projects. Use when the user wants to interact with Salesmate 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/salesmate/SKILL.md

Quality

Content

67%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 well-structured, command-heavy integration guide with a clear connection- setup workflow and state-based checkpoints, weakened mainly by an unnecessary CRM-intro paragraph and a large inlined action catalog that could be offloaded.

Suggestions

Delete the generic CRM-definition opening paragraph ('Salesmate is a CRM software designed to help...'); Claude can infer the domain, so it only costs tokens.

Move the 20-row 'Popular actions' catalog into a references file (e.g., references/actions.md) and keep only a few representative examples inline, with a one-level link.

Fix the step numbering — add a matching '1a' heading and label the 'Searching for actions' section as 'Step 2' so the 'skip to Step 2' reference resolves.

Dimension	Reasoning	Score
Conciseness	Command blocks and tables are efficient, but explanatory padding like 'Salesmate is a CRM software designed to help sales teams manage leads...' and 'so you can focus on the integration logic rather than auth plumbing' explains concepts Claude already knows, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete copy-paste commands appear throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.salesmate.io/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --json'), but placeholders need substitution and the proxy section lacks a worked endpoint example, so it sits at 'mostly executable' below the fully-covered score 5.	4 / 5
Workflow Clarity	A clear install → authenticate → connect → poll-until-ready → search → run sequence with state-checkpoint feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED and 'poll again after the action') is present, matching 'clear sequence with most checkpoints'; minor gaps (a '1b' heading with no '1a', a referenced 'Step 2' with no matching heading) keep it below 5.	4 / 5
Progressive Disclosure	Sections are well organized with clear headers and tables and no nested references, but the 20-row 'Popular actions' table is inlined and nothing is split into reference files (no references/scripts/assets exist), so it fits 'good structure with minor organization gaps' rather than the well-split score 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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 has an explicit 'Use when' trigger, a named niche, and a clear what, but its capabilities are described with a single generic verb over a list of entities and its trigger keywords are thin on synonyms.

Suggestions

Replace the generic verb 'Manage' with the concrete operations it covers (e.g., 'create, update, list, and fetch Organizations, Pipelines, Users, Filters, Projects') to lift specificity.

Add natural trigger synonyms beyond 'Salesmate data' — e.g., 'Salesmate CRM', 'Salesmate deals/contacts/companies' — so users phrase the request in more ways.

Tighten the 'when' clause to reference concrete CRM tasks (managing deals, contacts, pipelines) rather than the generic 'interact with Salesmate data'.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage Organizations, Pipelines, Users, Filters, Projects' name the domain plus several entities, but the single verb 'Manage' is a generic umbrella rather than multiple distinct concrete actions, matching the 'names domain and 1-2 concrete actions' anchor and falling below score 4's 'several specific actions'.	3 / 5
Completeness	'Salesmate integration. Manage Organizations...' gives a clear what and 'Use when the user wants to interact with Salesmate data.' gives an explicit when, satisfying the 'Use when...' requirement that prevents the cap of 3; it stays below 5 because the when could be more specific (no mention of CRM/deals/contacts).	4 / 5
Trigger Term Quality	The phrase 'interact with Salesmate data' surfaces essentially one natural keyword ('Salesmate') plus the generic 'data', missing common synonyms or variations, paralleling 'Works with PDF files' rather than the broader coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	'Salesmate' is a specific named CRM brand with a narrow, distinct trigger ('interact with Salesmate data'), giving a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/salesmate/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.