salesforce-automation

Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.

1.71x

Quality

67%

Does it follow best practices?

Impact

96%

1.71x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/salesforce-automation/SKILL.md

Quality

Content

68%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 well-structured, lean, and actionable with concrete tool slugs and executable SOQL examples. Its key weakness is workflow clarity: destructive and batch Salesforce operations lack validation feedback loops, which caps that dimension at 3.

Suggestions

Add validate→fix→retry feedback loops to destructive/batch workflows (e.g., after SALESFORCE_CREATE_LEAD, re-query to confirm the record exists; after SALESFORCE_MASS_TRANSFER_OWNERSHIP, verify ownership changed on a sample record).

Show one concrete sample MCP tool invocation (e.g., a RUBE_SEARCH_TOOLS call and a resulting SALESFORCE_CREATE_LEAD call) to make the actionability fully copy-paste ready.

Consider moving the Quick Reference table into a references/ file to reduce redundancy with the inline workflow tool sequences and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge (no padding about what Salesforce/leads/SOQL are); the only trim opportunity is the Quick Reference table duplicating tool slugs already listed in the workflow sections and pitfalls repeated both inline and under Known Pitfalls.	4 / 5
Actionability	Provides concrete tool slugs with key parameters and copy-paste-ready executable SOQL examples, plus the explicit "call RUBE_SEARCH_TOOLS first" instruction; the minor gap is that no sample MCP tool invocation is shown as executable code.	4 / 5
Workflow Clarity	Each workflow has a clear "When to use" and numbered tool sequence, and setup includes an ACTIVE-status checkpoint, but the create/update/mass-transfer/complete-task workflows are destructive or batch database operations with no validate→fix→retry feedback loops, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but it is well-organized into clearly headed sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference); at ~187 lines it exceeds the simple-skill threshold, and the Quick Reference table could be split into a reference file.	4 / 5
	Total	15 / 20 Passed

Description

66%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 specific and distinctive, naming the Salesforce domain and five concrete object areas with strong natural trigger terms. Its main weakness is the absence of an explicit "Use when…" trigger clause, which caps completeness at 3.

Suggestions

Add an explicit "Use when…" trigger clause, e.g. "Use when the user needs to create, search, or update Salesforce records or run SOQL queries."

Replace the generic verb "Automate … tasks" with concrete actions (create, search, update, query) to raise specificity toward 5.

Include common synonyms/variations (e.g. "Salesforce CRM", "records") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Salesforce domain plus five concrete areas (leads, contacts, accounts, opportunities, SOQL queries), but the only action verb is the generic "Automate … tasks", so it falls short of the comprehensive concrete-action anchor at 5.	4 / 5
Completeness	The "what" is clear (Automate Salesforce tasks via Rube MCP across the listed objects), but there is no "Use when…" trigger clause; the trailing sentence is an instruction, not a trigger, so completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would actually say (Salesforce, leads, contacts, accounts, opportunities, SOQL), giving good keyword coverage, though it lacks synonyms and file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	"Salesforce via Rube MCP (Composio)" carves a clear niche with mostly distinct triggers, with only minor overlap risk against other generic CRM skills.	4 / 5
	Total	15 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/salesforce-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 18 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.