CtrlK
BlogDocsLog inGet started
Tessl Logo

sales-simplify

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

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sales-simplify/SKILL.md
SKILL.md
Quality
Evals
Security

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 clean, executable Membrane CLI integration guide with strong actionability and good structure. The main gap is the absence of validation/error-recovery checkpoints in the connection and action-run workflow.

Suggestions

Add explicit validation checkpoints, e.g. after `membrane connect` confirm the connectionId appears in `membrane connection list`, and after `membrane action run` show how to detect and recover from an error response.

Trim the introductory CRM product description; Claude only needs the integration mechanics, not what Sales Simplify the product is.

Resolve the heading-level inconsistency and fold the bare 'Popular actions' section (which restates the earlier discovery command) into 'Searching for actions' to avoid redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and a flag table, but the opening CRM product description ('designed to help sales teams manage leads...automate sales processes') is background Claude does not need.

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands for install, login, connection, action discovery, action runs with JSON input, and proxy requests, covering the common cases.

5 / 5

Workflow Clarity

The connection flow is sequenced (install -> login -> connect -> search -> run), but there are no validation checkpoints or error-recovery loops for the external API operations, leaving the 'check that the connection/actions succeeded' step implicit.

3 / 5

Progressive Disclosure

Content is organized into clear sections with no nested or broken references, and a single self-contained file is appropriate here; minor organization gaps (inconsistent heading depth, a bare 'Popular actions' section restating a prior command) keep it below the top anchor.

4 / 5

Total

16

/

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.

The description is concrete and scoped to a distinct niche with a proper 'Use when' trigger. It could reach the top band with more comprehensive, synonym-rich trigger phrases.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('Manage Organizations, Users, Goals, Filters') rather than vague language, but the action set is not comprehensive enough to reach the top anchor.

4 / 5

Completeness

Both 'what' (manage Organizations, Users, Goals, Filters) and 'when' (the 'Use when...' clause) are present, with the 'when' slightly generic rather than tied to concrete trigger phrases.

4 / 5

Trigger Term Quality

It includes natural keywords ('Sales Simplify', 'Sales Simplify data') and an explicit 'Use when the user wants to interact with Sales Simplify data' trigger, but is missing common synonyms or file/extension variations.

4 / 5

Distinctiveness Conflict Risk

It targets a clearly named niche CRM ('Sales Simplify') with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.