Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asgard-ai-platform/tw-ecom-invoice-ezpay
Issue and manage Taiwan e-invoices via ezPay (加值服務中心) through mcp-ezpay-einvoice.
Passed 21 of 23 test cases with the skill, and 11 of 23 without it.
and 13 more in the full report
10 fixed11 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
A customer who purchased hardware from our Taiwan online shop in March is requesting a partial refund for one defective component today (in May). We handle e-invoices through the ezPay platform. Can you create an operational plan to handle this refund properly without violating tax compliance? Please output the response using the standard ezPay invoice task format: start with a Context block detailing environment and carrier strategies, followed by a Tool Plan table, a Correction Path section detailing how to handle cross-period or partial adjustments, an Assumptions & Open Questions section, a Reconciliation section covering MOF platform sync, and the final Deliverable.
| Checked | Without skill | With skill |
|---|---|---|
| Specifies calling issue_allowance to record partial refund items. | Missed | Passed |
| Specifies calling trigger_allowance with status C to confirm the allowance. | Missed | Passed |
| Includes a step-by-step Tool Plan table listing execution steps. | Passed | Passed |
The instructions your model reads when the skill loads.
/XXXXXXX), 自然人憑證, or 會員載具 — so the invoice is not printed on paperstatus="3") that must go live on a later date (e.g., subscription renewal)LIB10002 encryption failures, INV20002 void-window errors, ALW10001 allowance-over-invoice errorstw-einvoice-guide for the MOF-direct pattern and conceptsmcp-ezpay-einvoice or the ezPay developer portal at https://inv.ezpay.com.tw/tw-einvoice-guide. This skill assumes you know the landscapeezPay is a 加值服務中心 — a middleman that batches merchant invoice requests, uploads them to the 財政部電子發票整合服務平台 on the merchant's behalf, and relays carrier / 捐贈碼 lookups back. The merchant's legal counterparty for tax purposes is still 財政部; ezPay is an operational convenience, not the source of truth.
mcp-ezpay-einvoice wraps 7 tools over the ezPay API:
issue_invoice, trigger_invoice, void_invoice, query_invoiceissue_allowance, trigger_allowance, void_allowanceCategory. category="B2B" requires buyer_ubn (統編) — omit it and the invoice silently becomes B2C (lottery-eligible, wrong tax reporting). category="B2C" attaches a carrier or prints paper.
Carriers. carrier_type="0" + carrier_num="/ABC1234" for 手機條碼 (slash + 7 chars). carrier_type="1" for 自然人憑證 (2 letters + 14 digits). carrier_type="2" for ezPay 會員載具. love_code (3-7 digits) for 捐贈碼 — mutually exclusive with carriers.
字軌. 財政部 assigns invoice-number ranges (字軌) per bimonthly period (e.g., TE00000000-TE99999999). ezPay draws from this pool on issuance. Exhausting the range blocks issuance — the MOF assigns the next period's range in advance, but only if you requested it.
Void vs allowance. void_invoice only works inside the same bimonthly period the invoice was issued (see Gotchas). After the period closes, corrections must go through issue_allowance → trigger_allowance (status C=confirm, D=cancel).
What is the user asking for?
│
test cases passed, vs 11 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.