Content
56%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of Square automation via Rube MCP with clear workflow sequences and useful pitfall documentation. However, it suffers from redundancy across sections (pitfalls and patterns repeated multiple times), lacks concrete executable examples showing actual tool invocation syntax, and could benefit from consolidation or splitting into separate reference files. The setup section is well-structured but the body content explains things Claude likely already knows (pagination, RFC 3339 format).
Suggestions
Add concrete tool invocation examples showing actual parameter JSON structures (e.g., the exact query object format for SQUARE_SEARCH_ORDERS) instead of pseudocode steps.
Consolidate pitfalls into a single section rather than repeating them in both per-workflow sections and the 'Known Pitfalls' section — this would significantly reduce token usage.
Remove explanations of concepts Claude already knows (RFC 3339 format, pagination patterns, what rate limits are) and replace with just the specific values/thresholds relevant to Square.
Add explicit error recovery steps for destructive operations like CANCEL_PAYMENT and CANCEL_INVOICE (e.g., verify status before cancelling, confirm result after).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes redundant information across sections. The 'Known Pitfalls' section repeats points already covered in per-workflow pitfalls (e.g., versioning, pagination, ID resolution). The 'Common Patterns' section also duplicates guidance from the workflows. The 'When to Use' footer is vacuous. Claude already knows RFC 3339 format and basic pagination patterns. | 3 / 5 |
Actionability | The skill provides tool names, parameter lists, and sequences, but lacks executable code or concrete MCP call examples with actual parameter structures. The 'Common Patterns' section uses pseudocode-like numbered steps rather than showing actual tool invocation syntax. Key details like the exact JSON structure for search queries or update payloads are missing. | 3 / 5 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps (Required/Optional/Prerequisite), and there are implicit validation points (check connection is ACTIVE, check version before update, follow cursor until absent). However, explicit validation checkpoints and error recovery loops are mostly absent — for example, no guidance on what to do if UPDATE_ORDER returns a 409 conflict beyond mentioning it exists. | 4 / 5 |
Progressive Disclosure | The content is a single monolithic file with no bundle files or external references. At ~180 lines with significant repetition between sections (pitfalls repeated in per-workflow and Known Pitfalls), the content would benefit from splitting detailed API reference and pitfalls into separate files. The quick reference table is helpful but the overall structure could be tighter. | 3 / 5 |
Total | 13 / 20 Passed |