Name: lime-crm
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

lime-crm

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

Quality

64%

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/lime-crm/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-rich integration guide with strong validation logic around connection setup and good progressive organization. Its main weakness is token efficiency: an introductory paragraph explaining what a CRM is adds padding Claude does not need, and a couple of dangling step references and unvalidated destructive proxy methods slightly blur the workflow.

Suggestions

Cut the opening paragraph explaining what Lime CRM/CRM is and who uses it; Claude already knows this — lead instead with what the skill does and the Membrane CLI workflow.

Fix the broken step numbering: label the workflow sections Step 1 (Install), Step 2 (Authenticate), Step 3 (Connect), etc., so the "skip to Step 2" and "1b" references resolve.

Add a validation checkpoint before destructive proxy calls (POST/PUT/PATCH/DELETE), e.g. confirm the target resource or dry-run the request before mutation, to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient, command-driven content, but the opening paragraph ("Lime CRM is a customer relationship management system designed to help businesses organize and manage their sales, marketing, and customer service activities...") explains what a CRM is — a concept Claude already knows — making this mostly efficient with some unnecessary explanation rather than the lean score-4 case.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands across the full flow (install, login, connection ensure, action list/run, request proxy) plus a complete flag table, but placeholders like CONNECTION_ID and the generic QUERY intent are never shown with a concrete Lime-CRM-specific worked example, leaving the minor gap that keeps it at 4 rather than 5.	4 / 5
Workflow Clarity	The connect-then-poll state machine has explicit validation and feedback loops (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-poll guidance), but the step references are inconsistent — "skip to Step 2" and "1b" appear without labeled Step 1/Step 2 anchors — and destructive proxy methods (DELETE/PUT) lack a validation checkpoint, the minor gaps that cap it at 4.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized under clear, navigable section headers (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); content is appropriately placed inline for a single-app integration skill, with only minor organization gaps (the long clientAction state machine could conceivably be split), matching the score-4 anchor.	4 / 5
	Total	15 / 20 Passed

Description

61%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 clearly identifies a distinct niche (Lime CRM) and includes an explicit Use-when trigger, but its action language is generic and its trigger terms lean on the product name rather than natural user phrasing. It is solid but could be sharpened with concrete verbs and common synonyms.

Suggestions

Replace generic verbs with concrete Lime CRM operations, e.g. "Create and update companies, persons, and cases; search sales; automate workflows."

Add natural trigger terms users actually say, such as "contacts," "deals," "pipeline," or "Lime CRM records," beyond just "interact with Lime CRM data."

Tighten the when-clause to name concrete triggers, e.g. "Use when the user wants to manage companies, persons, cases, or sales in Lime CRM."

Dimension	Reasoning	Score
Specificity	The phrase "Manage data, records, and automate workflows" names the Lime CRM domain but the actions are generic and minimal, with no concrete operations like "create companies" or "search persons," matching the score-2 anchor rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	Both halves are present — a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Lime CRM data"), but the what is somewhat vague and the when could be more specific, matching the score-4 anchor and falling short of the concrete trigger phrases needed for a 5.	4 / 5
Trigger Term Quality	It surfaces the key keyword "Lime CRM" plus "data," "records," and "workflows," but "interact with Lime CRM data" is not the most natural user phrasing and common action synonyms (contacts, deals, pipeline) are missing, so it sits at the score-3 anchor rather than the broader coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ("Lime CRM") with a trigger scoped to that product gives it a clear niche with minimal overlap risk against other skills, matching the score-5 anchor.	5 / 5
	Total	14 / 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/lime-crm/SKILL.md
Commit: f484c82

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