square-automation

Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.

1.21x

Quality

61%

Does it follow best practices?

Impact

90%

1.21x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/square-automation/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, information-dense body with concrete tool names, parameters, and per-workflow sequences. Its weaknesses are repeated pagination/pitfall content across sections, the absence of validation or confirmation steps before destructive cancels/updates, and an entirely inlined structure with no progressive disclosure to reference files.

Suggestions

Add verify-before-act steps for destructive operations (e.g., confirm invoice status and re-confirm the version immediately before SQUARE_CANCEL_INVOICE, or ask the user before cancelling).

Deduplicate pagination guidance — state the cursor-following pattern once in Common Patterns and remove it from each workflow's Pitfalls.

Move per-tool parameter and pitfall detail into reference files (e.g., references/payments.md, references/invoices.md) and keep SKILL.md as a workflow overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is dense and avoids explaining concepts Claude already knows, but pagination instructions appear in four separate workflows plus a Common Patterns section, and version/ID-resolution pitfalls are repeated across per-workflow "Pitfalls" and the global "Known Pitfalls" section — mostly efficient but could be tightened, matching anchor 3.	3 / 5
Actionability	Concrete, executable guidance throughout: exact tool names (e.g., "SQUARE_LIST_PAYMENTS"), specific parameters ("begin_time"/"end_time", "location_ids"), tagged sequences ([Required]/[Prerequisite]), and format examples ("2024-01-01T00:00:00Z"). Minor gaps — no example tool-call payloads — keep it at anchor 4 rather than 5.	4 / 5
Workflow Clarity	Sequences are clearly ordered with prerequisites and the setup section has checkpoints (confirm connection ACTIVE before running workflows), but destructive operations ("SQUARE_CANCEL_PAYMENT", "SQUARE_CANCEL_INVOICE", "SQUARE_UPDATE_ORDER") lack any verify-before-act or confirmation steps, which caps workflow clarity at 3 per the destructive/batch-operations rule.	3 / 5
Progressive Disclosure	The single-file body is well-sectioned with clear headers and a quick-reference table, but ~175 lines of per-tool parameters and pitfalls are inlined in SKILL.md rather than split into reference files, matching anchor 3 (some structure, content that could be separate is inline) more than the well-split anchor 4 or 5.	3 / 5
	Total	13 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, domain-specific description that names concrete capability areas (payments, orders, invoices, locations) and a distinct tool stack. Its main weakness is the missing explicit "Use when..." trigger guidance, which caps completeness and slightly weakens trigger-term and distinctiveness performance.

Suggestions

Add an explicit trigger clause such as "Use when the user wants to manage Square payments, orders, invoices, or locations" to satisfy the completeness requirement.

Include natural synonyms users might say (e.g., charges, refunds, POS, billing) to broaden trigger-term coverage.

State the concrete actions per domain (e.g., "list and cancel payments", "search and update orders") instead of the single generic verb "Automate".

Dimension	Reasoning	Score
Specificity	"Automate Square tasks... payments, orders, invoices, locations" lists several specific capability areas with concrete objects, but relies on the single generic verb "Automate" rather than distinct concrete actions per domain, so it falls short of the comprehensive anchor 5 and clearly above anchor 3.	4 / 5
Completeness	The description has a clear "what" (automating Square payments, orders, invoices, locations) but no "Use when..." clause or equivalent trigger guidance — "Always search tools first for current schemas" is behavioral instruction, not usage triggering — which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"Square", "payments", "orders", "invoices", "locations" are terms users would naturally say, giving good keyword coverage, but common synonyms like "charges", "refunds", "POS", or "billing" are missing, matching anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	"Automate Square tasks via Rube MCP (Composio)" carves a clear niche with minimal conflict risk, but without an explicit trigger clause it could still overlap with other Square- or ecommerce-related skills, matching anchor 4 (mostly distinct, minor overlap) rather than 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/square-automation/SKILL.md
Commit: c9856ea

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.