Name: salesforce
Rating: 60 (1 reviews)
Author: membranedev

salesforce

Salesforce integration. Manage crm and marketing automation data, records, and workflows. Use when the user wants to interact with Salesforce data.

Quality

70%

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

Quality

Content

67%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 a well-structured, action-oriented guide with concrete CLI commands, a useful action catalog, and a strongly validated connection workflow. Its main weaknesses are an unnecessary introductory explainer of what Salesforce is and the absence of verification guidance around the destructive/batch actions the skill surfaces.

Suggestions

Remove or drastically condense the opening "Salesforce is a leading cloud-based CRM platform..." paragraph; assume Claude already knows what Salesforce is.

Add an explicit validation/verification checkpoint to the "Running actions" workflow for destructive and batch operations (e.g., confirm before delete-multiple-records, verify the returned record count or IDs after batch create/update).

Consider moving the 20-row "Popular actions" catalog and the proxy flag table into a separate reference file referenced one level deep from SKILL.md to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands and tables, but the opening paragraph ("Salesforce is a leading cloud-based CRM platform that helps businesses...") explains a concept Claude already knows, and phrases like "so you can focus on the integration logic rather than auth plumbing" add padding the rubric explicitly penalizes.	3 / 5
Actionability	It provides many concrete, executable commands (npm install, membrane login, connection ensure, action list/run, request) plus a populated actions table, but execution depends on a prior discovery step and uses placeholders like <actionId> and CONNECTION_ID, leaving minor gaps versus copy-paste-ready coverage.	4 / 5
Workflow Clarity	The connection lifecycle is a clear sequence with explicit validation and feedback loops (poll --wait, READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR handling), but the generic "Running actions" step offers no verification checkpoint for the destructive/batch actions (delete-multiple-records, create up to 200) it exposes, which is a notable gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and easy navigation, and there are no nested references; however at ~185 lines with a sizable inline actions catalog and proxy-options table, some of this bulk could live in one-level-deep reference files rather than entirely inline.	4 / 5
	Total	15 / 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.

The description cleanly states a Salesforce-specific niche with explicit what/when guidance and natural trigger terms, and uses correct third-person voice. It is held back from the top band by a generic action verb ("Manage") and a lack of concrete capability examples or synonym coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Salesforce integration", "crm and marketing automation") and lists objects ("data, records, and workflows") but the only action verb is the generic "Manage", so it sits at the 1-2 concrete-actions level rather than comprehensive coverage.	3 / 5
Completeness	Both "what" ("Manage crm and marketing automation data, records, and workflows") and "when" ("Use when the user wants to interact with Salesforce data") are present; the trigger phrase is explicit but somewhat generic rather than concrete scenarios, so it does not reach the level-5 anchor.	4 / 5
Trigger Term Quality	It surfaces natural terms a user would say ("Salesforce", "crm", "marketing automation", "records") and an explicit trigger phrase, but is missing common synonyms and variations (e.g. "CRM data", "Salesforce API", "SOQL"), keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Salesforce integration" with the distinct trigger "interact with Salesforce data" carves a clear niche with minimal overlap risk against other skills.	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/salesforce/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.