square-automation

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

Install with Tessl CLI

npx tessl i github:davepoon/buildwithclaude --skill square-automation

What are skills?

Review — 51%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

40%

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 Composio) with good distinctiveness, but suffers from listing categories rather than concrete actions and completely lacks explicit trigger guidance. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Square payments, creating invoices, managing orders, or working with Square locations'

Convert category nouns to concrete actions: instead of 'payments, orders, invoices', use 'process payments, create/manage orders, generate invoices, look up locations'

Add common user variations like 'POS', 'point of sale', 'Square billing', or 'payment processing' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (Square tasks via Rube MCP/Composio) and lists some actions (payments, orders, invoices, locations), but these are categories rather than concrete actions like 'create invoices' or 'process payments'.	2 / 3
Completeness	Describes what it does (automate Square tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Square', 'payments', 'orders', 'invoices', 'locations', and 'Composio', but missing common variations users might say like 'payment processing', 'POS', 'point of sale', or 'billing'.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche with 'Square' and 'Rube MCP (Composio)' as clear identifiers; unlikely to conflict with other skills due to the specific platform and integration mentioned.	3 / 3
	Total	8 / 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 skill provides solid workflow structure with clear sequencing and validation checkpoints for Square API operations. However, it lacks concrete executable examples (actual JSON payloads or API calls) and contains some redundancy across sections. The content would benefit from splitting detailed reference material into separate files and adding copy-paste ready examples.

Suggestions

Add concrete JSON request/response examples for at least one workflow (e.g., actual SQUARE_SEARCH_ORDERS call with query filter structure)

Consolidate repeated information (pagination, RFC 3339 format, versioning) into a single 'Common Patterns' section and reference it from workflows

Move the detailed pitfalls and Quick Reference table to a separate REFERENCE.md file to reduce main skill length

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy (e.g., repeating pagination patterns across workflows, explaining RFC 3339 format multiple times). The Quick Reference table at the end duplicates information already covered in workflows.	2 / 3
Actionability	Provides tool names and parameter lists but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style numbered steps rather than actual API calls or JSON payloads. No concrete request/response examples are provided.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with explicit tool ordering, prerequisite steps marked, and optional vs required steps labeled. Includes validation checkpoints (verify connection is ACTIVE, check version fields) and error recovery guidance (version mismatch handling, pagination continuation).	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in a single file. The extensive pitfalls and patterns sections could be split into separate reference files. The external toolkit docs link is good, but no internal file references for advanced topics.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 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

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.