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

69%

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.

A dense, well-structured reference for MCP-driven Salesforce automation with concrete tool slugs and parameters. Its main weaknesses are the absence of validation/verification checkpoints in the data-mutating workflows (notably the batch mass-transfer operation) and some duplicated content between the workflow sections and the Quick Reference table.

Suggestions

Add a verification step before destructive or batch operations, e.g. confirm the record list with the user before SALESFORCE_MASS_TRANSFER_OWNERSHIP and re-query to confirm updates took effect.

Remove the duplicated ID-format guidance (stated in both the lead workflow pitfalls and the Known Pitfalls section) and consolidate it in one place.

Consider moving the Quick Reference table into a references/ file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Largely lean — terse tool sequences with [Optional]/[Required] markers and pitfall bullets that assume Salesforce/SOQL knowledge — but the ID-format pitfall is stated twice and the Quick Reference table duplicates workflow tool slugs.	4 / 5
Actionability	Concrete tool slugs, required parameter names, and copy-paste-ready SOQL snippets make the guidance mostly executable; minor gaps remain since full tool-call payloads and the pagination token flow are not shown.	4 / 5
Workflow Clarity	Setup has explicit validation (auth link fallback, 'Confirm connection status shows ACTIVE'), but the CRUD workflows list unvalidated optional steps and mass transfer ownership is a batch operation with no verification checkpoint, capping this at 3.	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and no nested references; at ~190 lines, content like the Quick Reference table could arguably move to a separate reference file, keeping it just below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

70%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 specific, well-scoped description for a distinct niche, but it answers only 'what this does' and omits any 'when to use it' trigger guidance. Adding an explicit 'Use when...' clause with natural trigger phrases would make it fully complete.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Salesforce, CRM records, leads, opportunities, or wants to run SOQL queries.'

State the concrete actions available (create, search, update records) rather than only naming the object types.

Include a couple of natural synonyms users might say, such as 'CRM' or 'deals', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capability areas ('leads, contacts, accounts, opportunities, SOQL queries'), but lists object types rather than the actual actions (create, update, search), leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear ('Automate Salesforce tasks via Rube MCP (Composio)'), but there is no 'Use when...' clause or equivalent trigger guidance; 'Always search tools first for current schemas' is an instruction, not a when-to-use trigger, so completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes good natural keywords users would say ('Salesforce', 'leads', 'contacts', 'opportunities', 'SOQL queries'), though common synonyms like 'CRM records', 'deals', or 'pipeline' are missing.	4 / 5
Distinctiveness Conflict Risk	'Salesforce tasks via Rube MCP (Composio)' plus distinct terms like 'SOQL queries' define a clear niche with minimal conflict 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/salesforce-automation/SKILL.md
Commit: b90e2de

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.