Content
50%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable catalog of Salesforce operations via Rube MCP with clear tool names, required parameters, and useful SOQL examples. However, it reads more like an API reference than an actionable workflow guide—most steps are marked [Optional] with no real decision logic, and there's significant duplication between workflow sections and the quick reference table. It lacks validation steps after operations and concrete tool invocation examples.
Suggestions
Replace [Optional] tags with actual decision guidance (e.g., 'If user provides search criteria, use SALESFORCE_SEARCH_LEADS first; if creating from scratch, skip to SALESFORCE_CREATE_LEAD')
Add at least one concrete end-to-end example showing actual tool invocation with parameters and expected response handling
Add validation/verification steps after create and update operations (e.g., 'Confirm creation by checking the returned ID' or 'Verify update with a follow-up search')
Remove the quick reference table or the detailed workflow sections to eliminate duplication—keep whichever format better serves the use case
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but contains repetitive patterns across workflows (each section follows the same template with [Optional] tags that add little value). The quick reference table duplicates information already covered in the workflow sections. The 'When to Use' footer is vacuous. Some pitfalls are repeated (e.g., ID formats mentioned in both Leads and Known Pitfalls sections). | 3 / 5 |
Actionability | The skill lists tool names and parameters clearly, and provides concrete SOQL examples. However, it lacks executable examples showing actual tool invocations with full parameter structures. Every tool in the workflows is marked [Optional], which provides no real guidance on when to use which tool. The setup steps are concrete but the core workflows are more like reference catalogs than actionable instructions. | 3 / 5 |
Workflow Clarity | The setup section has a clear 4-step sequence with a validation checkpoint (confirm ACTIVE status). However, the core workflows lack true sequencing—they're lists of optional tools rather than guided workflows. There are no validation/verification steps after operations (e.g., confirming a lead was created successfully, verifying SOQL results). For batch operations like MASS_TRANSFER_OWNERSHIP, there's no validation or error recovery guidance. | 3 / 5 |
Progressive Disclosure | The content is structured with clear sections and headers, which aids navigation. However, at ~180 lines with significant repetition, some content (like the full quick reference table or detailed SOQL patterns) could be split into separate reference files. There are no bundle files or external references, and the skill is long enough that it would benefit from them. The instruction to 'always call RUBE_SEARCH_TOOLS first to get current tool schemas' partially mitigates the need for detailed inline documentation. | 3 / 5 |
Total | 12 / 20 Passed |