Name: solve-crm
Rating: 62.4 (1 reviews)
Author: membranedev

solve-crm

Solve CRM integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Solve CRM 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/solve-crm/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.

The body is highly actionable with concrete CLI commands for the full integration lifecycle, but it spends tokens on a CRM overview Claude already knows and lacks validation/caution around destructive operations listed in its actions table.

Suggestions

Remove or shrink the opening "Solve CRM is a customer relationship management platform..." paragraph; assume Claude knows what a CRM is and lead with the integration mechanics.

Add a validation checkpoint for destructive actions (delete-contact, delete-company, delete-ticket): confirm the target exists and prompt for confirmation before running, and verify the result afterward.

Fix the step numbering — define "Step 2" explicitly or relabel the connection sub-steps so "skip to Step 2" resolves to a real section.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Solve CRM is a customer relationship management platform designed to help businesses organize contacts, track sales...") explains what a CRM is — padding Claude does not need — and "Use action names and parameters as needed" is filler, though the command-heavy bulk is efficient.	3 / 5
Actionability	Copy-paste ready commands cover the common cases end to end: `npm install -g @membranehq/cli@latest`, `membrane login`, `membrane connection ensure ... --json`, `membrane action list`, `membrane action run`, and `membrane request`, plus a populated actions table and proxy-flag table.	5 / 5
Workflow Clarity	The connection flow has a real feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but step numbering is inconsistent ("skip to Step 2" with no defined Step 2) and destructive actions (delete-contact/delete-company/delete-ticket) are listed with no validation or caution, triggering the destructive-ops cap at 3.	3 / 5
Progressive Disclosure	It is a single well-sectioned file with clear headers and no nested or broken references; the inline actions catalog and proxy-flag table could be externalized but are acceptably scoped as quick-reference material.	4 / 5
	Total	15 / 20 Passed

Description

78%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 cleanly states what the skill does and when to use it, scoped to a named product with concrete entities. It is strong but the trigger phrasing and action verbs could be richer for a top score.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Goals, Filters" lists several concrete CRM entity types to act on, though the single verb "Manage" leaves minor gaps in action diversity (no create/read/update distinction).	4 / 5
Completeness	It has both an explicit "what" ("Manage Organizations, Pipelines, Users, Goals, Filters") and an explicit "when" ("Use when the user wants to interact with Solve CRM data"), matching anchor 4 where the "when" could be more specific.	4 / 5
Trigger Term Quality	"Solve CRM" and "interact with Solve CRM data" give good primary keyword coverage, but common natural entity terms a user might say (contacts, companies, tickets) are missing.	4 / 5
Distinctiveness Conflict Risk	It names a specific product (Solve CRM) with its own entity vocabulary, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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/solve-crm/SKILL.md
Commit: f484c82

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