Name: capsule-crm
Rating: 63.2 (1 reviews)
Author: membranedev

capsule-crm

Capsule CRM integration. Manage crm and sales data, records, and workflows. Use when the user wants to interact with Capsule CRM 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/capsule-crm/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 highly actionable, well-structured CLI integration guide with strong command examples and a clear connection-state workflow. Its main weakness is the absence of validation/verification for destructive and batch data operations, which caps workflow clarity.

Suggestions

Add validation/verification checkpoints for destructive and batch operations — e.g., confirm with the user before running delete-* actions, and verify the returned output after create/update runs.

Trim the opening paragraph explaining what a CRM is and who uses it; Claude already knows this and it consumes tokens without adding guidance.

Consider moving the Popular actions table into a separate reference file (e.g. ACTIONS.md) to keep SKILL.md a lean overview and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Largely lean and command-driven with concrete CLI examples throughout; matches anchor 4 (efficient, minor over-explanation) rather than 5 because the opening paragraph explains what a CRM is and who uses it, and phrases like 'so you can focus on the integration logic rather than auth plumbing' add little guidance value.	4 / 5
Actionability	Provides copy-paste-ready, executable commands for every stage (install, login, connection ensure/get --wait, action list/run, request proxy) plus a concrete popular-actions table and a proxy-flag table, matching anchor 5 (fully executable, covers common cases).	5 / 5
Workflow Clarity	The connection flow is well sequenced with an explicit state-polling feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the skill exposes destructive and batch operations (delete-project, delete-task, update-*) with no validation or verification steps, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Well-organized into clear headed sections with no nested references and only an external docs link, matching anchor 4; not 5 because the skill exceeds 50 lines and inlines a lengthy actions table that could arguably live in a separate reference file.	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 clear, third-person description that states both what the skill does and when to use it, with a distinct branded trigger. It is held back from the top band by a generic action verb ('Manage') and a single narrow trigger phrase.

Suggestions

Replace the generic verb 'Manage' with concrete actions (e.g., 'create, update, and delete contacts, opportunities, tasks, and projects') to raise capability specificity.

Broaden the 'Use when' clause with more natural trigger phrases (e.g., contacts, leads, sales pipeline, opportunities, .csv exports) so Claude matches a wider range of user requests.

Dimension	Reasoning	Score
Specificity	Names the domain ('Capsule CRM') and enumerates objects ('crm and sales data, records, and workflows') but relies on a single generic verb ('Manage'), matching anchor 3 (domain + 1-2 concrete actions, not comprehensive) rather than 2 because it lists several concrete objects, and not 4 because the action is generic rather than multiple specific verbs.	3 / 5
Completeness	Explicitly answers both what ('Manage crm and sales data, records, and workflows') and when ('Use when the user wants to interact with Capsule CRM data'), matching anchor 4; not 5 because the 'when' offers a single trigger phrase rather than the multiple concrete triggers in the anchor-5 example.	4 / 5
Trigger Term Quality	Includes natural keywords a user would say ('Capsule CRM', 'sales data', 'records', 'workflows', 'interact with Capsule CRM data') — good coverage matching anchor 4, but not 5 because common synonyms like 'contacts', 'leads', 'pipeline', or 'opportunities' are absent.	4 / 5
Distinctiveness Conflict Risk	Names a specific branded product ('Capsule CRM integration') giving it a clear niche with minimal conflict risk, matching anchor 5; it would only trigger for users seeking that exact product.	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/capsule-crm/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.