square-automation
Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.
71
60%
Does it follow best practices?
Impact
90%
1.21xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/square-automation/SKILL.mdQuality
Discovery
57%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 identifies a clear niche (Square automation via Rube MCP/Composio) with good distinctiveness, but lacks specific concrete actions and an explicit 'Use when...' clause. The listed categories (payments, orders, invoices, locations) are too high-level to fully convey the skill's capabilities.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to interact with Square for processing payments, managing orders, creating invoices, or looking up locations.'
Replace category nouns with specific actions, e.g., 'Process payments, create and manage orders, generate invoices, look up store locations' instead of just listing 'payments, orders, invoices, locations'.
Include additional natural trigger terms users might say, such as 'refunds', 'Square API', 'catalog', 'customers', or 'point of sale'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Square) and lists some action areas (payments, orders, invoices, locations), but these are categories rather than specific concrete actions like 'create invoices' or 'process payments'. The instruction to 'search tools first' is a procedural note rather than a capability. | 2 / 3 |
Completeness | The 'what' is partially addressed (automate Square tasks via Rube MCP), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the domain keywords listed. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Square', 'payments', 'orders', 'invoices', 'locations', and 'Rube MCP (Composio)' which are useful triggers. However, it misses common user variations like 'payment processing', 'refunds', 'catalog', 'customers', or 'Square API'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Square' and 'Rube MCP (Composio)' creates a very specific niche that is unlikely to conflict with other skills. This is clearly distinguishable from general payment or order management skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent skill document with clear workflow sequencing and good structural organization, but it suffers from significant redundancy across sections (pitfalls repeated in both per-workflow and global sections) and lacks concrete, executable tool invocation examples. The content would benefit from deduplication and from showing at least one complete tool call with actual parameter values rather than just listing parameter names.
Suggestions
Add at least one concrete, complete tool invocation example per workflow showing actual parameter values (e.g., a full RUBE_SEARCH_TOOLS call with the square toolkit, or a SQUARE_SEARCH_ORDERS call with a real query filter structure).
Consolidate pitfalls into a single section and reference it from workflows, rather than repeating pagination, version, and location_id guidance in every workflow AND in the Known Pitfalls section.
Remove or condense the 'Common Patterns' section—pagination and date filtering are already covered in individual workflows and could be a brief 2-line note rather than a repeated subsection.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across sections (e.g., pagination, location_id requirements, version fields mentioned multiple times), and the 'Known Pitfalls' section largely restates what was already covered in individual workflow pitfalls. The 'Common Patterns' section also repeats pagination and date filtering guidance. Could be tightened by ~30%. | 2 / 3 |
Actionability | The skill provides clear tool names, parameter lists, and sequences, but lacks executable code or concrete tool invocation examples with actual parameter structures. The 'Common Patterns' section uses pseudocode-style numbered lists rather than showing actual tool call syntax. Key parameters are listed but not shown in context of a real invocation. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit prerequisite steps, labeled as [Required]/[Optional]/[Prerequisite]. The setup section includes a verification flow. Version conflict handling and pagination loops serve as validation checkpoints. The pitfalls sections call out error conditions and recovery paths (e.g., version mismatch returns 409, only certain invoice states can be cancelled). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a quick reference table, but it's a monolithic document (~180 lines) with no references to external files. The detailed pitfalls, common patterns, and per-workflow documentation could benefit from being split into separate reference files. However, with no bundle files provided, there's nothing to split into, so the inline approach is somewhat justified. | 2 / 3 |
Total | 9 / 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
c911a92
- 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.