Name: salesloft
Rating: 53.6 (1 reviews)
Author: membranedev

salesloft

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

Quality

60%

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

Quality

Content

63%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 body is a strong, actionable CLI integration guide with concrete commands and a real polling/feedback loop for connection readiness. Weaknesses are mild over-explanation in the intro, placeholder-only examples, and an inlined action-reference table that has no progressive-disclosure offloading.

Suggestions

Trim the introductory paragraph explaining what Salesloft and SDRs are; Claude already knows this, and a one-line product context is enough.

Move the 'Popular actions' table into a references/ file (e.g. actions.md) and keep only the 3-5 most-used actions inline, with a clear link to the rest.

Add one fully-worked end-to-end example with concrete values (a real connection id, action id, and --input JSON) to lift actionability from placeholder-level to copy-paste-complete.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ('Salesloft is a sales engagement platform... used by SDRs and account executives') and phrases like 'This will burn less tokens' explain context Claude largely does not need. It is not score 4 because the over-explanation is more than minor, and not score 2 because the bulk is tight CLI reference rather than padded.	3 / 5
Actionability	It provides copy-paste-ready commands for the full lifecycle (install, login, connection ensure, action list, action run, request) plus a proxy-options table. It is not score 5 because placeholders like CONNECTION_ID, actionId, and 'QUERY' are left abstract without a concrete worked example showing real values.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run sequence, with a genuine feedback loop in the connection-state handling (poll until READY, branch on CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR). It is not score 5 because the steps are not explicitly numbered and the 'Step 2' references are loosely labeled, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	Sections are reasonably organized with headers, but the 20-row 'Popular actions' table is bulk reference data inlined in SKILL.md with no separate reference files and no bundle directory to offload it. It is not score 4 because content that would benefit from a separate file is inlined and navigation is flat.	3 / 5
	Total	14 / 20 Passed

Description

57%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 successfully states both what the skill does and when to use it with a third-person voice and an explicit trigger clause. Its main weakness is generic action language ('manage') and limited trigger-term coverage, which keep specificity and trigger quality in the mid range.

Suggestions

Replace the generic verb 'Manage' with concrete Salesloft actions (e.g. 'Search and list people, accounts, and cadences; enroll contacts in cadences; send and track emails').

Expand the 'Use when' clause with multiple natural trigger phrases users would say, such as 'when the user mentions Salesloft, cadences, SDR outreach, or prospect engagement'.

Add file-format or object synonyms (people/contacts, accounts, cadences, emails, calls) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Salesloft integration') but the only actions are the generic verb 'Manage' applied to 'sales data, records, and workflows', which is abstract rather than concrete. It is below score 3 because 'manage' is not a specific action like 'extract' or 'fill forms'.	2 / 5
Completeness	It answers both 'what' ('Manage sales data, records, and workflows') and 'when' ('Use when the user wants to interact with Salesloft data') with an explicit Use-when clause, so it clears the cap of 3. It is not score 5 because the 'what' is generic and the trigger phrase is singular rather than a set of concrete trigger phrases.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Salesloft data' provides the natural keyword 'Salesloft', but it is a single trigger phrasing missing common variations or synonyms (e.g. cadences, outreach, contacts, prospects). It is not score 4 because keyword coverage is narrow rather than just missing a few terms.	3 / 5
Distinctiveness Conflict Risk	'Salesloft integration' ties the skill to a named product, giving it a clear niche with minimal conflict risk. It is not score 5 because the trigger ('interact with Salesloft data') is somewhat broad and could lightly overlap with generic CRM or sales-engagement skills.	4 / 5
	Total	13 / 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/salesloft/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.