Name: nimble-crm
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nimble-crm

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

Quality

65%

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/nimble-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 provides concrete, executable Membrane CLI guidance with a well-validated connection workflow. It loses points for an unnecessary CRM intro and marketing prose, inconsistent step numbering, and a "Popular actions" section that does not actually list popular actions.

Suggestions

Remove the CRM-definition intro paragraph and marketing phrases ("burn less tokens", "focus on the integration logic rather than auth plumbing") to tighten token use.

Fix the step numbering: label a clear "Step 1"/"Step 2" (or remove the dangling "Step 2" and "1b" references) so the connection workflow reads as one coherent sequence.

Make "Popular actions" list actual common Nimble actions (e.g. create/update a contact, list deals) with example actionIds instead of repeating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding Claude does not need — the CRM intro paragraph ("Nimble is a CRM... designed for small to medium-sized businesses") and marketing language ("burn less tokens", "focus on the integration logic rather than auth plumbing") — fitting score 3.	3 / 5
Actionability	Concrete, executable commands appear throughout (login, connection ensure, action list/run, request proxy) with a clear flag table and well-marked placeholders, but there are no fully worked examples with real action names or IDs for common Nimble cases, matching score 4.	4 / 5
Workflow Clarity	The connection setup is a clear sequence with explicit state validation (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-act-repoll feedback loop, but step numbering is inconsistent ("Step 2" is referenced but never labeled as a header, "1b" has no matching "1a"), fitting score 4.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and easy navigation, and no bundle files are referenced; minor gaps (a misleading "Popular actions" section that repeats the discovery command instead of listing actions, and inconsistent step labels) keep it at score 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 explicitly covers both what the skill does and when to use it, anchored by a distinctive product name. Its main weakness is generic action language that omits the concrete CRM terms (contacts, deals, leads) users would naturally say.

Suggestions

Replace generic actions with concrete CRM verbs, e.g. "Manage contacts, deals, and activities in Nimble, and automate workflows".

Expand the trigger clause with natural user phrases: "Use when the user wants to manage Nimble contacts, deals, activities, or search records."

Drop the redundant "Nimble integration." lead-in to tighten the description and avoid repeating the product name.

Dimension	Reasoning	Score
Specificity	Names the Nimble domain plus 1-2 actions ("Manage data, records" and "automate workflows"), but the actions are generic rather than concrete CRM operations like contacts or deals, matching the score-3 anchor of domain + 1-2 non-comprehensive actions.	3 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Nimble data") are present, but the 'when' is generic rather than listing concrete trigger phrases, matching score 4.	4 / 5
Trigger Term Quality	The product name "Nimble" and "interact with Nimble data" are natural triggers, but common CRM vocabulary a user would actually say (contacts, deals, leads, CRM) is missing, fitting score 3 (some relevant keywords, missing common variations).	3 / 5
Distinctiveness Conflict Risk	The specific "Nimble" product name gives it a clear, distinct niche with minimal conflict risk, but the generic "manage data, records, automate workflows" phrasing creates minor overlap with other data-management skills, fitting score 4.	4 / 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/nimble-crm/SKILL.md
Commit: f484c82

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