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 reasonably specific about Salesforce capabilities and names concrete entities, making it distinctive. However, it lacks an explicit 'Use when...' clause, which limits completeness, and the trigger terms could be broader to capture more natural user language like 'CRM' or 'sales pipeline'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Salesforce, CRM tasks, managing leads/contacts/accounts/opportunities, or running SOQL queries.'
Include common user-facing synonyms like 'CRM', 'sales pipeline', 'deal tracking', '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. The 'when' is only implied. | 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 | Clearly scoped to Salesforce via a specific integration (Rube MCP/Composio), with distinct entity types and SOQL queries that are 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 comprehensive catalog of Salesforce operations via Rube MCP with useful tool names, parameters, and SOQL examples. However, it suffers from redundancy (pitfalls repeated, quick reference duplicating workflow sections), lacks complete executable examples showing actual tool invocations with parameters, and marks all workflow steps as '[Optional]' without clear decision guidance. Adding verification steps after data-modifying operations and showing at least one complete end-to-end example would significantly improve it.
Suggestions
Add at least one complete end-to-end example showing actual tool calls with full parameters (e.g., creating a lead from start to finish including the RUBE_SEARCH_TOOLS call and verification).
Add verification/confirmation steps after data-modifying operations (create, update, delete) to validate success before proceeding.
Remove redundancy between the per-workflow pitfalls/key parameters and the quick reference table—consolidate into one authoritative location.
Replace '[Optional]' on every workflow step with decision criteria or conditional guidance (e.g., 'If lead exists, search first; otherwise skip to create').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but contains significant redundancy—pitfalls are repeated 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 complete executable workflow (e.g., actual tool call with full parameters). The guidance is more of a reference catalog than step-by-step executable instructions. The critical instruction to 'always call RUBE_SEARCH_TOOLS first' is good but the actual invocation pattern is never demonstrated. | 2 / 3 |
Workflow Clarity | The setup section has a clear 4-step sequence with a validation checkpoint (confirm ACTIVE status). However, the core workflows mark every step as '[Optional]' without guidance on when to use which combination, and there are no validation/verification steps after operations (e.g., confirming a lead was created successfully). For CRM operations that could affect production data, missing verification steps is a gap. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, but it's a long monolithic file (~150+ lines) that could benefit from splitting detailed workflow sections or the quick reference table into separate files. The external link to Composio docs is good, but there's no internal file decomposition for the substantial amount of content present. | 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
7cc63f3
- 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.