salesforce-automation
Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill salesforce-automation59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 effectively communicates specific Salesforce capabilities and is highly distinctive, but critically lacks explicit trigger guidance ('Use when...') that would help Claude know when to select this skill. The domain-specific terminology is good but could benefit from more natural user language variations.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Salesforce, CRM data, sales leads, customer accounts, or needs to query sales records.'
Include common user language variations like 'CRM', 'sales pipeline', 'customer data', 'SF' alongside the technical Salesforce terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'leads, contacts, accounts, opportunities, SOQL queries' and includes the actionable guidance to 'search tools first for current schemas.' These are concrete Salesforce entities and operations. | 3 / 3 |
Completeness | Describes what it does (automate Salesforce tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'Salesforce', 'leads', 'contacts', 'accounts', 'opportunities', 'SOQL queries', but missing common user variations like 'CRM', 'sales pipeline', 'customer records', or 'SF'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically mentions 'Salesforce', 'Rube MCP (Composio)', and Salesforce-specific entities like 'SOQL queries'. Unlikely to conflict with other skills due to the specific platform and tooling references. | 3 / 3 |
Total | 9 / 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 comprehensive coverage of Salesforce operations via Rube MCP with good structural organization and useful SOQL examples. However, it lacks executable tool invocation examples, has redundant content between workflows and the quick reference table, and marks all workflow steps as optional which reduces actionability. The setup section is the strongest part with clear validation steps.
Suggestions
Add concrete tool invocation examples showing exact parameter structures (e.g., `SALESFORCE_CREATE_LEAD` with full parameter JSON)
Remove [Optional] markers from workflow steps and instead show decision logic (e.g., 'If searching existing leads first: use SALESFORCE_SEARCH_LEADS')
Consolidate the quick reference table with workflow sections to eliminate redundancy - either keep detailed workflows OR the table, not both
Add validation/verification steps to workflows (e.g., 'Verify lead was created by searching for it' or 'Check response for error codes')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the quick reference table duplicates information from the workflow sections, and some explanations (like ID formats, pagination basics) could be trimmed since Claude understands these concepts. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The SOQL examples are helpful, but actual tool invocation examples showing exact parameter structures are missing - it's more descriptive than copy-paste ready. | 2 / 3 |
Workflow Clarity | Workflows list tool sequences but mark everything as [Optional], which undermines clarity. The setup section has clear steps with validation (check ACTIVE status), but core workflows lack explicit validation checkpoints or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a helpful quick reference table. However, it's somewhat monolithic at ~180 lines - detailed workflow sections could be split into separate files, with SKILL.md serving as a leaner overview pointing to them. | 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 | |
- 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.