salesforce-automation
Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.
72
58%
Does it follow best practices?
Impact
96%
1.71xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/salesforce-automation/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly identifying Salesforce-specific entities and the integration mechanism. However, it lacks an explicit 'Use when...' trigger clause, which caps completeness, and could benefit from more natural user-facing trigger terms beyond technical Salesforce jargon.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Salesforce, CRM tasks, managing leads/contacts/accounts, sales pipeline, or running SOQL queries.'
Include common user-facing synonyms like 'CRM', 'sales pipeline', 'deal tracking', or 'customer records' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete entities and actions: leads, contacts, accounts, opportunities, SOQL queries, and includes the operational guidance to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Salesforce tasks involving leads, contacts, accounts, opportunities, SOQL queries), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'Salesforce', 'leads', 'contacts', 'accounts', 'opportunities', 'SOQL queries', but misses common user variations like 'CRM', 'sales pipeline', 'deal tracking', or 'Salesforce automation'. The mention of 'Rube MCP (Composio)' is technical jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific Salesforce domain, named integration (Rube MCP/Composio), and Salesforce-specific entities like SOQL queries. Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid catalog of Salesforce tools and their parameters, with useful SOQL examples and a comprehensive quick reference table. However, it lacks concrete end-to-end tool invocation examples, has no post-operation validation steps in workflows, and contains notable redundancy between the workflow sections and the quick reference table. The content would benefit from being more concise and more actionable with real invocation examples.
Suggestions
Add at least one concrete, end-to-end example showing the exact arguments passed to a tool (e.g., a full SALESFORCE_CREATE_LEAD call with all required parameters), rather than just listing parameter names.
Add validation/verification steps after create and update operations (e.g., 'After creating a lead, search for it to confirm creation succeeded') to improve workflow reliability.
Remove redundancy between the per-workflow 'Key parameters' / 'Pitfalls' sections and the Quick Reference table—consolidate into one authoritative location.
Remove the '[Optional]' annotations on every tool step and instead describe the decision logic for when to use each tool (e.g., 'If user provides search criteria, use SALESFORCE_SEARCH_LEADS first; otherwise list all').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but contains significant repetition—pitfalls are restated across sections (e.g., required fields mentioned in both key parameters and pitfalls), and the quick reference table largely duplicates information already covered in the core workflows. The '[Optional]' annotations on every tool step add noise without value. | 2 / 3 |
Actionability | The skill lists specific tool names, parameters, and SOQL examples which are helpful, but it never shows a concrete end-to-end invocation of any tool (e.g., actual JSON arguments to pass to RUBE_SEARCH_TOOLS or SALESFORCE_CREATE_LEAD). The guidance is more of a reference catalog than executable, copy-paste-ready instructions. | 2 / 3 |
Workflow Clarity | The setup section has a clear 4-step sequence with a validation checkpoint (confirm ACTIVE status). However, the core workflows list tools as optional steps without clear sequencing or decision logic, and there are no validation/verification steps after create or update operations (e.g., confirming a lead was created successfully). | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers and a quick reference table, which aids navigation. However, with no bundle files, all content is inline in a single long document (~150+ lines). The detailed per-object workflows and SOQL patterns could be split into separate reference files, and the external link to Composio docs is the only reference provided. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.