Antigravity-awesome-skills square-automation
Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.
git clone https://github.com/sickn33/antigravity-awesome-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills/skills/square-automation" ~/.claude/skills/sickn33-antigravity-awesome-skills-square-automation-4079b4 && rm -rf "$T"
plugins/antigravity-awesome-skills/skills/square-automation/SKILL.mdSquare Automation via Rube MCP
Automate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Square connection via
with toolkitRUBE_MANAGE_CONNECTIONSsquare - Always call
first to get current tool schemasRUBE_SEARCH_TOOLS
Setup
Get Rube MCP: Add
https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
respondsRUBE_SEARCH_TOOLS - Call
with toolkitRUBE_MANAGE_CONNECTIONSsquare - If connection is not ACTIVE, follow the returned auth link to complete Square OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. List and Monitor Payments
When to use: User wants to view payment history or check payment status
Tool sequence:
- Retrieve payments with optional filters [Required]SQUARE_LIST_PAYMENTS
- Cancel a pending payment if needed [Optional]SQUARE_CANCEL_PAYMENT
Key parameters:
/begin_time
: RFC 3339 timestamps for date range filteringend_time
: 'ASC' or 'DESC' for chronological orderingsort_order
: Pagination cursor from previous responsecursor
: Filter payments by specific locationlocation_id
Pitfalls:
- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')
- Pagination required for large result sets; follow
until absentcursor - Only pending payments can be cancelled; completed payments require refunds
requires exactSQUARE_CANCEL_PAYMENT
from list resultspayment_id
2. Search and Manage Orders
When to use: User wants to find orders by criteria or update order details
Tool sequence:
- Get location IDs for filtering [Prerequisite]SQUARE_LIST_LOCATIONS
- Search orders with filters [Required]SQUARE_SEARCH_ORDERS
- Get full details of a specific order [Optional]SQUARE_RETRIEVE_ORDER
- Modify order state or details [Optional]SQUARE_UPDATE_ORDER
Key parameters:
: Array of location IDs to search within (required for search)location_ids
: Search filter object with date ranges, states, fulfillment typesquery
: Specific order ID for retrieve/update operationsorder_id
: Pagination cursor for search resultscursor
Pitfalls:
is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS firstlocation_ids- Order states include: OPEN, COMPLETED, CANCELED, DRAFT
- UPDATE_ORDER requires the current
field to prevent conflictsversion - Search results are paginated; follow
until absentcursor
3. Manage Locations
When to use: User wants to view business locations or get location details
Tool sequence:
- List all business locations [Required]SQUARE_LIST_LOCATIONS
Key parameters:
- No required parameters; returns all accessible locations
- Response includes
,id
,name
,address
,statustimezone
Pitfalls:
- Location IDs are required for most other Square operations (orders, payments)
- Always cache location IDs after first retrieval to avoid redundant calls
- Inactive locations may still appear in results; check
fieldstatus
4. Invoice Management
When to use: User wants to list, view, or cancel invoices
Tool sequence:
- Get location ID for filtering [Prerequisite]SQUARE_LIST_LOCATIONS
- List invoices for a location [Required]SQUARE_LIST_INVOICES
- Get detailed invoice information [Optional]SQUARE_GET_INVOICE
- Cancel a scheduled or unpaid invoice [Optional]SQUARE_CANCEL_INVOICE
Key parameters:
: Required for listing invoiceslocation_id
: Required for get/cancel operationsinvoice_id
: Pagination cursor for list resultscursor
: Number of results per pagelimit
Pitfalls:
is required for LIST_INVOICES; resolve via LIST_LOCATIONS firstlocation_id- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled
- CANCEL_INVOICE requires the invoice
to prevent race conditionsversion - Cancelled invoices cannot be uncancelled
Common Patterns
ID Resolution
Location name -> Location ID:
1. Call SQUARE_LIST_LOCATIONS 2. Find location by name in response 3. Extract id field (e.g., 'L1234ABCD')
Order lookup:
1. Call SQUARE_SEARCH_ORDERS with location_ids and query filters 2. Extract order_id from results 3. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER
Pagination
- Check response for
fieldcursor - Pass cursor value in next request's
parametercursor - Continue until
is absent or emptycursor - Use
to control page sizelimit
Date Range Filtering
- Use RFC 3339 format:
2024-01-01T00:00:00Z - For payments:
andbegin_time
parametersend_time - For orders: Use query filter with date_time_filter
- All timestamps are in UTC
Known Pitfalls
ID Formats:
- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')
- Payment IDs and Order IDs are longer alphanumeric strings
- Always resolve location names to IDs before other operations
Versioning:
- UPDATE_ORDER and CANCEL_INVOICE require current
fieldversion - Fetch the resource first to get its current version
- Version mismatch returns a 409 Conflict error
Rate Limits:
- Square API has per-endpoint rate limits
- Implement backoff for bulk operations
- Pagination should include brief delays for large datasets
Response Parsing:
- Responses may nest data under
keydata - Money amounts are in smallest currency unit (cents for USD)
- Parse defensively with fallbacks for optional fields
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| List payments | SQUARE_LIST_PAYMENTS | begin_time, end_time, location_id, cursor |
| Cancel payment | SQUARE_CANCEL_PAYMENT | payment_id |
| Search orders | SQUARE_SEARCH_ORDERS | location_ids, query, cursor |
| Get order | SQUARE_RETRIEVE_ORDER | order_id |
| Update order | SQUARE_UPDATE_ORDER | order_id, version |
| List locations | SQUARE_LIST_LOCATIONS | (none) |
| List invoices | SQUARE_LIST_INVOICES | location_id, cursor |
| Get invoice | SQUARE_GET_INVOICE | invoice_id |
| Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.