[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5DG2G4T8XG7VPMC2SGDBV":3,"skill-same:01M7F5DG2G4T8XG7VPMC2SGDBV":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F5DG2G4T8XG7VPMC2SGDBV","square-automation",null,"Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fsquare-automation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: square-automation\ndescription: \"Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Square Automation via Rube MCP\n\nAutomate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Square connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `square`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `square`\n3. If connection is not ACTIVE, follow the returned auth link to complete Square OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Monitor Payments\n\n**When to use**: User wants to view payment history or check payment status\n\n**Tool sequence**:\n1. `SQUARE_LIST_PAYMENTS` - Retrieve payments with optional filters [Required]\n2. `SQUARE_CANCEL_PAYMENT` - Cancel a pending payment if needed [Optional]\n\n**Key parameters**:\n- `begin_time` \u002F `end_time`: RFC 3339 timestamps for date range filtering\n- `sort_order`: 'ASC' or 'DESC' for chronological ordering\n- `cursor`: Pagination cursor from previous response\n- `location_id`: Filter payments by specific location\n\n**Pitfalls**:\n- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')\n- Pagination required for large result sets; follow `cursor` until absent\n- Only pending payments can be cancelled; completed payments require refunds\n- `SQUARE_CANCEL_PAYMENT` requires exact `payment_id` from list results\n\n### 2. Search and Manage Orders\n\n**When to use**: User wants to find orders by criteria or update order details\n\n**Tool sequence**:\n1. `SQUARE_LIST_LOCATIONS` - Get location IDs for filtering [Prerequisite]\n2. `SQUARE_SEARCH_ORDERS` - Search orders with filters [Required]\n3. `SQUARE_RETRIEVE_ORDER` - Get full details of a specific order [Optional]\n4. `SQUARE_UPDATE_ORDER` - Modify order state or details [Optional]\n\n**Key parameters**:\n- `location_ids`: Array of location IDs to search within (required for search)\n- `query`: Search filter object with date ranges, states, fulfillment types\n- `order_id`: Specific order ID for retrieve\u002Fupdate operations\n- `cursor`: Pagination cursor for search results\n\n**Pitfalls**:\n- `location_ids` is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS first\n- Order states include: OPEN, COMPLETED, CANCELED, DRAFT\n- UPDATE_ORDER requires the current `version` field to prevent conflicts\n- Search results are paginated; follow `cursor` until absent\n\n### 3. Manage Locations\n\n**When to use**: User wants to view business locations or get location details\n\n**Tool sequence**:\n1. `SQUARE_LIST_LOCATIONS` - List all business locations [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible locations\n- Response includes `id`, `name`, `address`, `status`, `timezone`\n\n**Pitfalls**:\n- Location IDs are required for most other Square operations (orders, payments)\n- Always cache location IDs after first retrieval to avoid redundant calls\n- Inactive locations may still appear in results; check `status` field\n\n### 4. Invoice Management\n\n**When to use**: User wants to list, view, or cancel invoices\n\n**Tool sequence**:\n1. `SQUARE_LIST_LOCATIONS` - Get location ID for filtering [Prerequisite]\n2. `SQUARE_LIST_INVOICES` - List invoices for a location [Required]\n3. `SQUARE_GET_INVOICE` - Get detailed invoice information [Optional]\n4. `SQUARE_CANCEL_INVOICE` - Cancel a scheduled or unpaid invoice [Optional]\n\n**Key parameters**:\n- `location_id`: Required for listing invoices\n- `invoice_id`: Required for get\u002Fcancel operations\n- `cursor`: Pagination cursor for list results\n- `limit`: Number of results per page\n\n**Pitfalls**:\n- `location_id` is required for LIST_INVOICES; resolve via LIST_LOCATIONS first\n- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled\n- CANCEL_INVOICE requires the invoice `version` to prevent race conditions\n- Cancelled invoices cannot be uncancelled\n\n## Common Patterns\n\n### ID Resolution\n\n**Location name -> Location ID**:\n```\n1. Call SQUARE_LIST_LOCATIONS\n2. Find location by name in response\n3. Extract id field (e.g., 'L1234ABCD')\n```\n\n**Order lookup**:\n```\n1. Call SQUARE_SEARCH_ORDERS with location_ids and query filters\n2. Extract order_id from results\n3. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER\n```\n\n### Pagination\n\n- Check response for `cursor` field\n- Pass cursor value in next request's `cursor` parameter\n- Continue until `cursor` is absent or empty\n- Use `limit` to control page size\n\n### Date Range Filtering\n\n- Use RFC 3339 format: `2024-01-01T00:00:00Z`\n- For payments: `begin_time` and `end_time` parameters\n- For orders: Use query filter with date_time_filter\n- All timestamps are in UTC\n\n## Known Pitfalls\n\n**ID Formats**:\n- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')\n- Payment IDs and Order IDs are longer alphanumeric strings\n- Always resolve location names to IDs before other operations\n\n**Versioning**:\n- UPDATE_ORDER and CANCEL_INVOICE require current `version` field\n- Fetch the resource first to get its current version\n- Version mismatch returns a 409 Conflict error\n\n**Rate Limits**:\n- Square API has per-endpoint rate limits\n- Implement backoff for bulk operations\n- Pagination should include brief delays for large datasets\n\n**Response Parsing**:\n- Responses may nest data under `data` key\n- Money amounts are in smallest currency unit (cents for USD)\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List payments | SQUARE_LIST_PAYMENTS | begin_time, end_time, location_id, cursor |\n| Cancel payment | SQUARE_CANCEL_PAYMENT | payment_id |\n| Search orders | SQUARE_SEARCH_ORDERS | location_ids, query, cursor |\n| Get order | SQUARE_RETRIEVE_ORDER | order_id |\n| Update order | SQUARE_UPDATE_ORDER | order_id, version |\n| List locations | SQUARE_LIST_LOCATIONS | (none) |\n| List invoices | SQUARE_LIST_INVOICES | location_id, cursor |\n| Get invoice | SQUARE_GET_INVOICE | invoice_id |\n| Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Square Automation via Rube MCP\n\nAutomate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Square connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `square`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `square`\n3. If connection is not ACTIVE, follow the returned auth link to complete Square OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Monitor Payments\n\n**When to use**: User wants to view payment history or check payment status\n\n**Tool sequence**:\n1. `SQUARE_LIST_PAYMENTS` - Retrieve payments with optional filters [Required]\n2. `SQUARE_CANCEL_PAYMENT` - Cancel a pending payment if needed [Optional]\n\n**Key parameters**:\n- `begin_time` \u002F `end_time`: RFC 3339 timestamps for date range filtering\n- `sort_order`: 'ASC' or 'DESC' for chronological ordering\n- `cursor`: Pagination cursor from previous response\n- `location_id`: Filter payments by specific location\n\n**Pitfalls**:\n- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')\n- Pagination required for large result sets; follow `cursor` until absent\n- Only pending payments can be cancelled; completed payments require refunds\n- `SQUARE_CANCEL_PAYMENT` requires exact `payment_id` from list results\n\n### 2. Search and Manage Orders\n\n**When to use**: User wants to find orders by criteria or update order details\n\n**Tool sequence**:\n1. `SQUARE_LIST_LOCATIONS` - Get location IDs for filtering [Prerequisite]\n2. `SQUARE_SEARCH_ORDERS` - Search orders with filters [Required]\n3. `SQUARE_RETRIEVE_ORDER` - Get full details of a specific order [Optional]\n4. `SQUARE_UPDATE_ORDER` - Modify order state or details [Optional]\n\n**Key parameters**:\n- `location_ids`: Array of location IDs to search within (required for search)\n- `query`: Search filter object with date ranges, states, fulfillment types\n- `order_id`: Specific order ID for retrieve\u002Fupdate operations\n- `cursor`: Pagination cursor for search results\n\n**Pitfalls**:\n- `location_ids` is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS first\n- Order states include: OPEN, COMPLETED, CANCELED, DRAFT\n- UPDATE_ORDER requires the current `version` field to prevent conflicts\n- Search results are paginated; follow `cursor` until absent\n\n### 3. Manage Locations\n\n**When to use**: User wants to view business locations or get location details\n\n**Tool sequence**:\n1. `SQUARE_LIST_LOCATIONS` - List all business locations [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible locations\n- Response includes `id`, `name`, `address`, `status`, `timezone`\n\n**Pitfalls**:\n- Location IDs are required for most other Square operations (orders, payments)\n- Always cache location IDs after first retrieval to avoid redundant calls\n- Inactive locations may still appear in results; check `status` field\n\n### 4. Invoice Management\n\n**When to use**: User wants to list, view, or cancel invoices\n\n**Tool sequence**:\n1. `SQUARE_LIST_LOCATIONS` - Get location ID for filtering [Prerequisite]\n2. `SQUARE_LIST_INVOICES` - List invoices for a location [Required]\n3. `SQUARE_GET_INVOICE` - Get detailed invoice information [Optional]\n4. `SQUARE_CANCEL_INVOICE` - Cancel a scheduled or unpaid invoice [Optional]\n\n**Key parameters**:\n- `location_id`: Required for listing invoices\n- `invoice_id`: Required for get\u002Fcancel operations\n- `cursor`: Pagination cursor for list results\n- `limit`: Number of results per page\n\n**Pitfalls**:\n- `location_id` is required for LIST_INVOICES; resolve via LIST_LOCATIONS first\n- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled\n- CANCEL_INVOICE requires the invoice `version` to prevent race conditions\n- Cancelled invoices cannot be uncancelled\n\n## Common Patterns\n\n### ID Resolution\n\n**Location name -> Location ID**:\n```\n1. Call SQUARE_LIST_LOCATIONS\n2. Find location by name in response\n3. Extract id field (e.g., 'L1234ABCD')\n```\n\n**Order lookup**:\n```\n1. Call SQUARE_SEARCH_ORDERS with location_ids and query filters\n2. Extract order_id from results\n3. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER\n```\n\n### Pagination\n\n- Check response for `cursor` field\n- Pass cursor value in next request's `cursor` parameter\n- Continue until `cursor` is absent or empty\n- Use `limit` to control page size\n\n### Date Range Filtering\n\n- Use RFC 3339 format: `2024-01-01T00:00:00Z`\n- For payments: `begin_time` and `end_time` parameters\n- For orders: Use query filter with date_time_filter\n- All timestamps are in UTC\n\n## Known Pitfalls\n\n**ID Formats**:\n- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')\n- Payment IDs and Order IDs are longer alphanumeric strings\n- Always resolve location names to IDs before other operations\n\n**Versioning**:\n- UPDATE_ORDER and CANCEL_INVOICE require current `version` field\n- Fetch the resource first to get its current version\n- Version mismatch returns a 409 Conflict error\n\n**Rate Limits**:\n- Square API has per-endpoint rate limits\n- Implement backoff for bulk operations\n- Pagination should include brief delays for large datasets\n\n**Response Parsing**:\n- Responses may nest data under `data` key\n- Money amounts are in smallest currency unit (cents for USD)\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List payments | SQUARE_LIST_PAYMENTS | begin_time, end_time, location_id, cursor |\n| Cancel payment | SQUARE_CANCEL_PAYMENT | payment_id |\n| Search orders | SQUARE_SEARCH_ORDERS | location_ids, query, cursor |\n| Get order | SQUARE_RETRIEVE_ORDER | order_id |\n| Update order | SQUARE_UPDATE_ORDER | order_id, version |\n| List locations | SQUARE_LIST_LOCATIONS | (none) |\n| List invoices | SQUARE_LIST_INVOICES | location_id, cursor |\n| Get invoice | SQUARE_GET_INVOICE | invoice_id |\n| Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fsquare-automation",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill square-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill square-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill square-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fsquare-automation\u002FSKILL.md",true,[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]