square
Work with Square: list locations and payments, create orders, push Terminal checkouts, charge payment sources, and refund payments. Trigger phrases: square, square terminal, process payment, refund payment, point of sale.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- square
- tagline
- Work with a Square seller account: list locations and payments, create orders, push a checkout to a physical Square Terminal for in-person payment, charge a payment source directly, cancel a pending Terminal checkout, and refund a payment. Reach for this when the user needs to take or return money through Square.
- metadata
- { "includeInPrompt": true }
- description
- Work with Square: list locations and payments, create orders, push Terminal checkouts, charge payment sources, and refund payments. Trigger phrases: square, square terminal, process payment, refund payment, point of sale.
- catalog_auth
- provider OAuth 2.0 or personal access token via the secure credential flow
- catalog_hosts
- [ "connect.squareup.com", "connect.squareupsandbox.com" ]
02 资源文件 1
- 脚本bin/square.py11.6 KB
03 SKILL.md 正文
Square
Purpose
Work with a Square seller account: list locations and payments, create orders, push a checkout to a physical Square Terminal for in-person payment, charge a payment source directly, cancel a pending Terminal checkout, and refund a payment. Reach for this when the user needs to take or return money through Square.
Tooling
All commands go through bin/square.py. Sandbox is the default (--env sandbox); sandbox never moves real money. Add --env prod for production:
bin/square.py auth # verify the token (sandbox)
bin/square.py locations # list seller locations
bin/square.py payments --limit 10 # list payments
bin/square.py payment-get --payment-id PAY_ID # one payment
bin/square.py order-create --file order.json # create an order (moves no money)
bin/square.py checkout-create --device-id DEV_ID \
--amount-cents 1200 --currency USD \
--confirm "present $12.00 USD charge on terminal DEV_ID" # push charge to a Terminal
bin/square.py checkout-get --checkout-id CO_ID # Terminal checkout status
bin/square.py checkout-cancel --checkout-id CO_ID \
--confirm "cancel terminal checkout CO_ID" # cancel a pending checkout
bin/square.py charge --source-id SRC_ID \
--amount-cents 1200 --currency USD \
--confirm "charge $12.00 USD to payment source SRC_ID" # charge a payment source
bin/square.py refund --payment-id PAY_ID \
--amount-cents 1200 --currency USD \
--confirm "refund $12.00 USD on payment PAY_ID" # send money back
Amounts are in the currency's smallest unit (--amount-cents 1200 is $12.00). order-create takes a Square order object in JSON and creates an order record only; no money moves until a payment is attached.
Auth
- Provider id:
square(credential is collected ascustom.square) - Collection: OAuth 2.0 bearer via the secure credential flow (
credentials.request_api_access) for third-party apps, or a personal access token for a single account; the runtime performs the token exchange/refresh and hands the CLI a fresh Bearer token, same pattern as the slack and x connectors - Auth scheme:
Authorization: Bearer <token>on every request - Allowed hosts:
connect.squareup.com,connect.squareupsandbox.com - Sandbox is the CLI default and is mandatory for testing:
https://connect.squareupsandbox.com. Switch to production only with--env prodon the command and a production credential stored. - Status check:
bin/square.py auth
Operating Rules
- Sandbox is the default and is mandatory for testing. Never run a first-time flow against
--env prod. Confirm the flow works in sandbox, then switch. - Terminal checkout and direct charges are HIGH actuations.
POST /v2/terminals/checkoutspresents a charge on a physical Terminal; a customer tapping or inserting a card captures real funds.POST /v2/paymentscharges a payment source immediately. Both require--confirmwith the exact string the CLI echoes (it names the amount, the currency and the target) on every call, in sandbox and in production. Missing or mismatched confirmation refuses the call. - Refunds are MEDIUM and move real money back.
POST /v2/refundsrequires--confirmwith the exact echoed string on every call (this is stricter than the standing first-use-only rule, chosen because a mistaken refund is hard to take back). - Cancelling a pending Terminal checkout requires
--confirmevery time; it has no effect once the payment completed. - Square charges processing fees per transaction; check squareup.com pricing for current rates. Every write uses an idempotency key so retries cannot double-charge.
- Never exfiltrate the credential: the CLI only ever handles surrogates (see
bin/square.py). Do not print, log, or transmit the token.
Files
- SKILL.md
- bin/square.py
Maturity
Draft: written from Square's public API docs; not yet live-tested end-to-end.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).