Name: salesmsg
Rating: 66.4 (1 reviews)
Author: membranedev

salesmsg

Salesmsg integration. Manage Persons, Organizations, Conversations, Users, Numbers, Templates and more. Use when the user wants to interact with Salesmsg data.

Quality

80%

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

Quality

Content

82%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 well-structured, highly actionable CLI integration guide with a clear connection workflow and explicit state-validation checkpoints. Main weaknesses are a dangling "Step 2" reference, minor redundancy, and no validation guidance for destructive action runs.

Suggestions

Resolve the dangling "skip to Step 2" reference by either labeling the next section as Step 2 or rewording to "skip to Searching for actions".

Add a brief validation/caution note before running mutating or destructive actions (e.g. DELETE via proxy or status-changing actions), such as confirming the target id before execution.

De-duplicate the action-list command that appears in both "Searching for actions" and "Popular actions" to tighten the token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and a flags table, but the opening product-summary paragraph and the duplicated action-list command (in both "Searching for actions" and "Popular actions") are minor padding that could be trimmed, fitting the 4 anchor.	4 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (install, login, connection ensure, connection get --wait, action run, request) with a clear flags table and JSON output conventions, covering the common cases fully.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with explicit validation checkpoints (poll to READY, handle CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR/SETUP_FAILED), but the dangling "skip to Step 2" reference with no labeled Step 2 and no validation emphasis before potentially destructive action runs keep it just below 5.	4 / 5
Progressive Disclosure	Content is organized into clear sections and appropriately punts bulky action catalogs to CLI discovery rather than inlining them; with no bundle files present the single-file structure is well organized with only minor gaps, matching the 4 anchor.	4 / 5
	Total	17 / 20 Passed

Description

78%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 solid, third-person description that names the product, lists multiple capability domains, and includes an explicit "Use when" trigger. It is held back from the top tier by a single generic verb and a somewhat broad trigger clause.

Dimension	Reasoning	Score
Specificity	Lists several specific capability areas ("Manage Persons, Organizations, Conversations, Users, Numbers, Templates and more"), though the single generic verb "Manage" and the open-ended "and more" leave minor coverage gaps that keep it just below a 5.	4 / 5
Completeness	Both "what" ("Manage Persons, Organizations...") and "when" ("Use when the user wants to interact with Salesmsg data") are present, but the "when" trigger is fairly generic and could be more specific about concrete use cases, matching the 4 anchor rather than 5.	4 / 5
Trigger Term Quality	The natural keyword "Salesmsg" appears twice including in the trigger clause ("interact with Salesmsg data"), giving good coverage; it is not a 5 because there are no synonyms or file-extension variants to round out the natural vocabulary.	4 / 5
Distinctiveness Conflict Risk	"Salesmsg" is a distinct named product with a clear niche and explicit product-name trigger, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/salesmsg/SKILL.md
Commit: f484c82

Reviewed: 9 hours 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.