Name: square
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

square

Square integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Square data.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/square/SKILL.md

Quality

Content

56%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 delivers a well-sequenced, executable workflow with a genuine connection-state feedback loop, but it is dragged down by a large amount of inlined, partly-fabricated padding that wastes tokens and should live in a separate reference file.

Suggestions

Delete the fabricated "Recipe *" entity list (Recipe Machine Learning, Recipe AI, Recipe Disaster Recovery, etc.) which is irrelevant padding unrelated to Square.

Move the full entity list and popular-actions table into a separate reference file and keep SKILL.md as a concise overview that links to it.

Replace the repeated "No description" entries in the popular-actions table with real one-line descriptions so the table is actually actionable.

Dimension	Reasoning	Score
Conciseness	Nearly half the body is a ~130-item bullet list of entity names (lines 23-154) including fabricated padding like "Recipe Machine Learning", "Recipe Disaster Recovery", and "Recipe Artificial Intelligence" that are irrelevant to using the integration.	2 / 5
Actionability	It provides concrete, executable commands (npm install, membrane login, connection ensure, action list/run, request) with flags, though the popular-actions table repeats "No description" for every row and uses placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	A clear install -> authenticate -> connect -> poll-for-ready -> search -> run -> proxy sequence exists, with an explicit feedback loop for connection states (READY/BUILDING/CLIENT_ACTION_REQUIRED), but there is no verify/retry guidance for action-run outcomes.	4 / 5
Progressive Disclosure	Section headers give reasonable structure, but there are no reference files at all and the large entity dump plus 20-row action table are inlined content that clearly belongs in a separate reference file.	3 / 5
	Total	13 / 20 Passed

Description

62%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 answers both what and when with an explicit Use-when clause and a distinctive brand anchor, but it is generic in its verbs and trigger terms and lists entities that do not reflect Square's real API.

Suggestions

Replace the generic verb "Manage" with concrete Square actions (e.g., "Create and list payments, orders, invoices, and customers").

Expand the trigger clause with feature-level keywords users actually say (e.g., payments, refunds, catalog, invoices) instead of only "Square data".

Align the listed entities with Square's actual API objects rather than generic Organizations/Goals/Filters.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users, Goals, Filters" names the domain plus concrete objects with a verb, but the single generic verb "Manage" is not as specific as extract/fill/merge, and the listed entities do not match Square's actual API surface.	3 / 5
Completeness	It states both the what ("Square integration. Manage Organizations, Users, Goals, Filters.") and an explicit when ("Use when the user wants to interact with Square data"), but the when trigger is generic and could be more specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Square data" surfaces the natural keyword "Square" but offers no synonyms or feature-level terms (payments, orders, invoices), so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The "Square integration" brand anchor gives it a clear niche with minimal conflict risk, though the generic entity list (Organizations, Users, Goals, Filters) creates minor overlap with general SaaS skills.	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: membranedev/application-skills
Path: skills/square/SKILL.md
Commit: f484c82

Reviewed: 4 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.