Name: espocrm
Rating: 66.4 (1 reviews)
Author: membranedev

espocrm

EspoCRM integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with EspoCRM data.

Quality

80%

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

Quality

Content

82%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, highly actionable skill body dominated by executable Membrane CLI commands and a clear connection workflow with polling feedback. Its only weak spots are a brief CRM explainer Claude already knows and the absence of an explicit verification step after mutating actions.

Suggestions

Drop or trim the introductory sentence explaining what a CRM is; Claude already knows this.

Add a verification/retry checkpoint after running mutating actions (create/update/delete) so failures are caught and corrected.

Consider moving the 20-row "Popular actions" table to a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout, but the opening "EspoCRM is an open-source CRM (Customer Relationship Management) application..." explains a concept Claude already knows and could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection setup, action search/run, and proxy requests, plus a flags table covering the common cases fully.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with an explicit polling feedback loop (ensure → wait → check state → handle clientAction → re-poll), but action execution for mutating operations lacks an explicit post-run verification checkpoint.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files present; the long inline "Popular actions" table could arguably live in a reference file, leaving a minor organization gap.	4 / 5
	Total	17 / 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.

A focused, third-person description that names the EspoCRM domain and several entity types with an explicit "Use when" trigger. It is distinctive and clear, though the action verb is generic and the trigger condition is a single broad phrase.

Suggestions

Replace the generic verb "Manage" with specific concrete actions (e.g., create, update, list, search records) to lift specificity.

Expand the "Use when" clause with multiple concrete trigger phrases (e.g., "when the user mentions leads, deals, contacts, or wants to query/update CRM records").

Add common synonyms or the product's alternate phrasings users might say (e.g., "CRM records", "EspoCRM API").

Dimension	Reasoning	Score
Specificity	Lists several concrete entity targets ("Manage Leads, Persons, Organizations, Deals, Projects, Activities and more"), but the verb "Manage" is generic and there are minor coverage gaps, placing it just below the comprehensive anchor.	4 / 5
Completeness	Has a clear "what" (manage EspoCRM entities) and an explicit "Use when the user wants to interact with EspoCRM data" trigger, but the "when" is a single broad condition rather than the multiple concrete triggers of the top anchor.	4 / 5
Trigger Term Quality	Includes natural product term "EspoCRM" plus entity keywords a user would say (Leads, Deals, Organizations, Activities); good coverage but a few common phrasings or synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped explicitly to "EspoCRM integration" with EspoCRM-specific triggers, giving it a clear niche with minimal overlap 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/espocrm/SKILL.md
Commit: f484c82

Reviewed: 9 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.