Content
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, required parameters, and SOQL examples. However, it reads more like API documentation than an actionable skill—workflows are lists of optional tools rather than guided sequences, and there are no concrete examples of actual MCP tool invocations with real parameters. The content is moderately verbose with repeated information across sections.
Suggestions
Add at least one concrete end-to-end example showing actual MCP tool invocation with real parameters (e.g., calling RUBE_SEARCH_TOOLS, then SALESFORCE_CREATE_LEAD with specific JSON arguments and expected response).
Replace the '[Optional]' tool lists with actual decision-guided workflows: 'If user wants to create a lead → call X with {params}; verify success by checking response for Id field'.
Add validation/verification steps after write operations (create, update, delete) such as confirming the returned ID or re-querying to verify the change.
Consolidate repeated information—remove pitfalls that merely restate required fields already listed in key parameters, and consider whether the quick reference table can replace the verbose per-workflow parameter listings.
| 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 an MCP tool (e.g., actual JSON call with parameters). The tool sequences are more like menus of options than executable guidance—every step is marked '[Optional]' with no concrete example of calling a tool with real arguments. | 2 / 3 |
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 present lists of optional tools rather than guided multi-step processes. There are no validation/verification steps after operations (e.g., confirming a lead was created successfully, verifying an update took effect). | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with headers and a quick reference table, but it's monolithic at ~150+ lines with no external references for detailed content. The detailed SOQL patterns, all five workflow sections, and the full reference table could benefit from being split into separate files, especially since there are no bundle files to offload to. | 2 / 3 |
Total | 8 / 12 Passed |