Name: nectar-crm
Rating: 59.2 (1 reviews)
Author: membranedev

nectar-crm

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

Quality

69%

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/nectar-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 content is a well-structured, actionable CLI integration guide with a strong connection workflow and concrete commands throughout. Its weaknesses are mild verbosity (a CRM definition and promotional padding) and a couple of broken step references that hurt sequencing clarity.

Suggestions

Remove the opening CRM definition paragraph and promotional phrasing; assume Claude knows what a CRM is and lead directly with the install/auth workflow.

Fix the step numbering: label the connection-ensure section as "Step 1a" (or renumber) so "1b" and the repeated "skip to Step 2" references resolve to actual sections.

De-duplicate the action-list command (it appears in both "Searching for actions" and "Popular actions") and add one worked example showing a real intent and action run.

Dimension	Reasoning	Score
Conciseness	The body is mostly a lean command reference, but it opens by defining what a CRM is and who uses it (concepts Claude already knows), includes promotional padding like "so you can focus on the integration logic rather than auth plumbing", and duplicates the action-list command in two sections.	3 / 5
Actionability	Provides concrete copy-paste commands throughout (install, login, connection ensure, action run with --input, request with a full flag table), but uses template placeholders and lacks a single worked end-to-end example with a real action, leaving a minor gap.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop, but a dangling "Step 2" reference, an unlabeled "1b" with no "1a", and no error-handling guidance for action runs are minor validation gaps.	4 / 5
Progressive Disclosure	A single well-organized file with clear sections and one external docs link; no bundle files exist and the >50-line simple-skill exception does not apply, so the lack of signaled one-level-deep references keeps it just below a 5.	4 / 5
	Total	15 / 20 Passed

Description

71%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 product niche and lists concrete managed entities with an explicit 'Use when' clause. Its main weakness is generic, somewhat inconsistent trigger phrasing that lacks the natural synonyms users would actually say.

Suggestions

Replace the generic trigger with concrete user phrasings, e.g. "Use when the user wants to create or update contacts, deals, or leads, log activities, or query Nectar CRM data."

Align entity terms with the body or add synonyms (e.g. "Contacts (Persons)", "Companies (Organizations)", "Opportunities (Deals)") so triggers match how users actually refer to them.

Drop "and more" in favor of naming the remaining capabilities explicitly, or state the category boundary clearly to avoid over-claiming.

Dimension	Reasoning	Score
Specificity	Lists several concrete managed entity types ("Persons, Organizations, Deals, Leads, Activities, Notes") under a clear "Manage" action, giving specific capability coverage; the trailing "and more" is a minor gap that keeps it just below a 5.	4 / 5
Completeness	Explicitly states both what ("Manage Persons, Organizations, Deals, Leads, Activities, Notes") and when ("Use when the user wants to interact with Nectar CRM data"), but the trigger clause is generic rather than packed with concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	Includes the product name and several entity keywords, but uses terms inconsistent with the body (Persons/Organizations/Deals vs. Contact/Company/Opportunity) and lacks common synonyms a user would naturally say, leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product ("Nectar CRM") with distinct entity-level triggers, giving it a clear niche with minimal risk of triggering for the wrong skill.	5 / 5
	Total	16 / 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/nectar-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.