Name: centralstationcrm
Rating: 59.2 (1 reviews)
Author: membranedev

centralstationcrm

CentralStationCRM integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with CentralStationCRM data.

Quality

68%

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

Quality

Content

75%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 highly actionable with executable commands and a solid connection workflow including state-based checkpoints. It is somewhat padded with unnecessary conceptual explanation and carries a dangling 'Step 2' reference plus unvalidated destructive entries.

Suggestions

Define or remove the dangling 'Step 2' reference (referenced in 'skip to Step 2' but never labeled).

Drop conceptual padding Claude already knows (the CRM definition sentence and 'so you can focus on the integration logic rather than auth plumbing').

Add a brief validation/caution note for destructive actions (e.g., confirm IDs before delete-person) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes minor padding Claude does not need, such as defining what a CRM is ('helps small businesses and sales teams organize contacts...') and editorializing like 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	Fully executable, copy-paste-ready commands are provided throughout (install, login, connection ensure, action list/run, request) plus a flags table and a populated popular-actions table with keys, covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-retry feedback loop, but a referenced 'Step 2' is never defined and destructive actions like delete-person appear in the table with no validation caution.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, but the 20-row popular-actions table is bulk inline content with no bundle files to offload it, leaving minor organization gaps.	4 / 5
	Total	16 / 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 covers both what and when and is anchored to a distinct product, but its capability list is generic and mismatched with the body's actual entities. Tightening the verb and aligning the named objects with the real actions would lift specificity and trigger quality.

Suggestions

Replace the generic 'Manage' with concrete verbs matching the body (e.g., 'List, create, update, and delete People, Companies, Deals, Projects, and Tasks').

Align the entity list (Organizations, Users, Goals, Filters) with the actual actions the skill exposes (People, Companies, Deals, Projects, Tasks).

Expand the 'Use when' clause with concrete natural triggers, e.g., 'Use when the user wants to list or update CRM contacts, deals, projects, or tasks in CentralStationCRM.'

Dimension	Reasoning	Score
Specificity	Names the domain and several entities ('Manage Organizations, Users, Goals, Filters') but relies on a single generic verb ('Manage') rather than distinct concrete actions, and the listed entities do not match the skill body's actual People/Companies/Deals/Projects/Tasks.	3 / 5
Completeness	Both a 'what' ('Manage Organizations, Users, Goals, Filters') and a 'when' ('Use when the user wants to interact with CentralStationCRM data') are present, but the 'when' clause is generic and could name concrete trigger scenarios.	4 / 5
Trigger Term Quality	The only natural keyword is the product name 'CentralStationCRM' (repeated in 'interact with CentralStationCRM data'); no synonyms, common variations, or related natural phrases are included.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ('CentralStationCRM integration') gives it a clear distinct niche with minimal conflict risk, though the generic 'interact with data' phrasing leaves minor overlap with other CRM skills.	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/centralstationcrm/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.