square-automation

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

1.21x

Quality

63%

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

68%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.

The body is compact, concrete, and well-structured with good tool sequencing and a useful quick-reference table. Its main weakness is missing explicit validation/verification checkpoints for destructive order and invoice operations, which caps workflow clarity at 3.

Suggestions

Add explicit validation checkpoints before destructive operations: e.g. before SQUARE_UPDATE_ORDER, instruct to SQUARE_RETRIEVE_ORDER first to fetch the current version and confirm the target, then verify the updated state afterward.

De-duplicate the per-workflow 'Pitfalls' and the top-level 'Known Pitfalls' section to tighten conciseness — fold versioning and ID-format notes into the relevant workflows.

Provide at least one fully-specified example tool call (parameters filled in) for a representative workflow such as searching orders, to lift actionability toward 5.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and mostly lean — tool sequences, key parameters, and pitfalls are presented compactly without explaining concepts Claude already knows; a few sections like 'Known Pitfalls' overlap with per-workflow 'Pitfalls' and could be trimmed.	4 / 5
Actionability	Concrete tool slugs, required parameters, ID-resolution steps, and a quick-reference table give mostly executable guidance; it lacks full copy-paste-ready tool-call payloads, which is the gap keeping it below 5.	4 / 5
Workflow Clarity	Sequences are clearly listed with prerequisite steps, but operations like UPDATE_ORDER and CANCEL_INVOICE are destructive and the body lacks explicit validate-before-commit checkpoints; the rubric caps destructive/batch workflows at 3 when validation is missing.	3 / 5
Progressive Disclosure	Content is well structured with clearly labeled sections and a quick-reference table, and there are no bundle files to navigate to; minor organization gaps (overlapping pitfall sections) keep it from 5.	4 / 5
	Total	15 / 20 Passed

Description

58%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.

The description is specific about the Square domains it covers but omits an explicit 'Use when...' trigger clause, which the rubric caps at completeness 3. Trigger term coverage is adequate but lacks natural user phrasings and synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to list or cancel Square payments, search or update Square orders, or manage Square invoices and locations.'

Expand trigger terms with natural user phrasings and synonyms such as 'Square payments', 'Square orders', 'send/cancel an invoice', 'refund a payment'.

Name the concrete actions per domain (e.g. 'list and cancel payments, search and update orders, list and cancel invoices') to lift specificity from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete action domains — 'payments, orders, invoices, locations' — naming the specific Square resources it automates, with minor gaps in coverage of the actual actions performed.	4 / 5
Completeness	The 'what' is clear (automate Square tasks via Rube MCP) but there is no explicit 'Use when...' clause; the rubric caps completeness at 3 when trigger guidance is missing.	3 / 5
Trigger Term Quality	Includes relevant keywords (Square, payments, orders, invoices) but lacks common user phrasings like 'Square payments', 'process a refund', or 'send an invoice', and offers no synonyms.	3 / 5
Distinctiveness Conflict Risk	Square-via-Rube-MCP is a clearly distinct niche from other skills, with minimal overlap risk; only the broad 'Square tasks' phrasing slightly tempers it.	4 / 5
	Total	14 / 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: a9fa86d

Reviewed: about 18 hours 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.