square-automation

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

1.21x

Quality

—

Does it follow best practices?

Impact

90%

1.21x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

62%

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

The body is well-organized with clear tool sequences and a useful quick-reference table, and progressive disclosure is appropriate for a self-contained skill. Weaknesses are repeated pitfall content (conciseness), lack of executable code (actionability), and missing validation/feedback checkpoints for destructive and batch operations (workflow clarity).

Suggestions

Add explicit validation/feedback checkpoints to destructive and batch workflows — e.g. after CANCEL_PAYMENT/CANCEL_INVOICE/UPDATE_ORDER, instruct Claude to re-fetch and confirm the resulting state before proceeding.

Remove or de-duplicate the 'Known Pitfalls' section that restates per-workflow version/ID/pagination guidance already covered above, to tighten token efficiency.

Provide at least one concrete, executable example (actual tool call argument structure or a sample query object) rather than only parameter name lists, to lift actionability.

Dimension	Reasoning	Score
Conciseness	The body is well-structured and mostly lean, but the 'Known Pitfalls' section repeats guidance already given per-workflow (e.g. version requirements, ID resolution, pagination), adding tokens that restate what Claude already learned above.	2 / 3
Actionability	Tool names, parameters, and a Quick Reference table give concrete direction, but there is no executable code or exact call syntax — guidance is descriptive ('Call SQUARE_LIST_PAYMENTS', parameter lists) rather than copy-paste ready.	2 / 3
Workflow Clarity	Each workflow lists a numbered tool sequence and pitfalls, but batch/destructive operations (cancel payment, update order, cancel invoice) lack explicit validation checkpoints or feedback loops, which caps workflow clarity at 2 per the batch/destructive guideline.	2 / 3
Progressive Disclosure	No bundle files exist; the body is a self-contained overview organized into clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Quick Reference) with one external link, fitting the simple-skill / well-organized-sections anchor for a score of 3.	3 / 3
	Total	9 / 12 Passed

Description

65%

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 and distinctive, clearly naming the Square automation domain and its key sub-tasks. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness, and slightly technical phrasing over natural user language.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Square payments, orders, invoices, or locations' to satisfy the 'when should Claude use it' half of completeness.

Prefer natural user phrasing over internal framing — e.g. 'process payments, search orders, send invoices' rather than 'Automate Square tasks'.

Drop or de-emphasize the tooling parenthetical '(Composio)' and 'Always search tools first for current schemas' from the description, as these are implementation details better placed in the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions/objects — 'payments, orders, invoices, locations' — naming the specific Square domain tasks the skill automates, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks any explicit 'Use when...' trigger clause telling Claude when to invoke it; per guidelines, a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('Square', 'payments', 'orders', 'invoices', 'locations') but 'tasks' and the tooling framing ('Rube MCP (Composio)', 'schemas') lean technical and omit common user phrasings like 'process a payment' or 'find an order'.	2 / 3
Distinctiveness Conflict Risk	The Square-specific framing plus the named sub-domains (payments, orders, invoices, locations) carve a clear niche unlikely to overlap with other skills.	3 / 3
	Total	10 / 12 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
Commit: 366e45b

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