Name: sugarcrm
Rating: 63.2 (1 reviews)
Author: membranedev

sugarcrm

SugarCRM integration. Manage crm and sales data, records, and workflows. Use when the user wants to interact with SugarCRM data.

Quality

75%

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/sugarcrm/SKILL.md

Quality

Content

76%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 lean, highly actionable skill with excellent concrete CLI examples and a well-structured connection workflow. Its main gap is the lack of validation guidance for the destructive and batch actions it exposes.

Suggestions

Trim the generic CRM intro ('SugarCRM is a customer relationship management (CRM) platform. It helps sales, marketing... Businesses of all sizes use it to improve...') to a single purpose line, since Claude already knows what a CRM is.

Add a validation/verification step before destructive or batch operations — e.g., instruct to run get-record or list-records to confirm the target before delete-record, and to preview bulk-api-request inputs before execution.

Consider moving the 17-row Popular actions table to a references file and keeping a short 'key actions' summary inline, to tighten the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands and a tight best-practices list; the only noticeable padding is the generic intro describing what a CRM platform is and its business benefits, which Claude does not need.	4 / 5
Actionability	Guidance is fully executable — copy-paste-ready commands for install, login, connection, action search/run, and proxy, with real flags and a worked --input JSON example covering the common cases.	5 / 5
Workflow Clarity	The connect-and-poll sequence has clear state checkpoints and a feedback loop, but the skill exposes destructive and batch operations (delete-record, bulk-api-request, unlink-records) without any validation/verification step before running them, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The single file is well organized into clear sections (Overview, Working with SugarCRM, Popular actions, Best practices) with no nested references and easy navigation; it is over 50 lines with a sizable inline actions table that could arguably be split, so it sits just below the ideal one-level-deep split of anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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 concise, well-structured description that clearly states what the skill does and when to use it, anchored to a specific named product. The main weakness is the generic verb 'manage' rather than enumerating concrete capabilities.

Suggestions

Replace the generic 'Manage crm and sales data, records, and workflows' with a few concrete actions (e.g., 'Create, update, and search CRM records, manage opportunities and leads, and link related records').

Broaden the 'when' trigger with additional natural phrasings (e.g., 'when the user wants to manage CRM records, sales opportunities, contacts, or leads').

Dimension	Reasoning	Score
Specificity	It names the domain and a few actions ('Manage crm and sales data, records, and workflows'), but 'manage' is generic rather than a list of several specific concrete actions, so it does not reach the comprehensive coverage of anchors 4-5.	3 / 5
Completeness	Both 'what' (SugarCRM integration; manage crm and sales data, records, and workflows) and 'when' ('Use when the user wants to interact with SugarCRM data') are explicitly present, but the single trigger phrase keeps it just short of the fully comprehensive anchor 5.	4 / 5
Trigger Term Quality	Natural keywords users would say are present — 'CRM', 'sales data', 'records', 'workflows', 'SugarCRM' — giving good coverage, though a few common synonyms/phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product 'SugarCRM' creates a clear niche with distinct triggers and minimal conflict risk with other skills.	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/sugarcrm/SKILL.md
Commit: f484c82

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