CtrlK
BlogDocsLog inGet started
Tessl Logo

square-automation

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/square-automation/SKILL.md

The canonical home for this skill is square-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a well-structured, actionable overview of Square workflows with concrete tool sequences, but it is held back by redundant pitfalls, a filler 'When to Use' line, and missing validation feedback loops for destructive operations.

Suggestions

Add explicit validate→fix→retry checkpoints to destructive workflows (e.g., for UPDATE_ORDER/CANCEL_INVOICE: fetch current version, attempt the call, and on a 409 re-fetch and retry rather than just warning about version mismatches).

Remove redundant pitfalls — keep each pitfall in one place (either per-workflow or in 'Known Pitfalls', not both) and delete the filler 'When to Use' line.

Consider moving the per-workflow 'Key parameters' detail and 'Quick Reference' table into a reference file so SKILL.md stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized sections, but pitfalls are repeated across 'Core Workflows' and 'Known Pitfalls', and the trailing 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview.') is pure filler that could be trimmed.

3 / 5

Actionability

Provides concrete tool sequences with exact slugs (e.g., 'SQUARE_LIST_PAYMENTS'), named parameters, and formats (RFC 3339), giving mostly executable guidance with only minor gaps like missing example call payloads.

4 / 5

Workflow Clarity

Setup and each workflow are clearly sequenced with a setup checkpoint ('Confirm connection status shows ACTIVE'), but destructive operations (cancel payment, cancel invoice, update order) lack explicit validate→fix→retry feedback loops, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-structured single-file overview with clear section navigation (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) and no nested references; minor organization gaps since some detail could live in reference files.

4 / 5

Total

14

/

20

Passed

Description

70%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 and clearly distinct, naming concrete Square capability areas, but it omits any explicit 'Use when...' trigger guidance, capping completeness. Adding a usage-trigger clause would raise it to a top-tier description.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants to manage Square payments, search/update orders, handle invoices, or look up business locations.') to satisfy the 'when' half of completeness.

Include more natural synonyms and file/API terms users say (e.g., 'Square API', 'refunds', 'payment history') to broaden trigger coverage.

Soften or relocate the technical stack mention ('Rube MCP (Composio)') so natural trigger terms lead the description.

DimensionReasoningScore

Specificity

Lists several concrete action areas — 'payments, orders, invoices, locations' — naming the domain plus specific capabilities, though they are categories rather than fine-grained actions, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear ('Automate Square tasks... payments, orders, invoices, locations') but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural user terms like 'Square', 'payments', 'orders', and 'invoices', but mixes in technical jargon ('Rube MCP', 'Composio') and misses common synonyms like 'refunds' or 'Square API'.

4 / 5

Distinctiveness Conflict Risk

The Square-specific niche ('Square tasks via Rube MCP (Composio)') with payments/orders/invoices gives a clear, distinct trigger set with minimal conflict risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.