Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asgard-ai-platform/tw-ecom-invoice-void
Void Taiwan e-invoices within the same bimonthly window, or issue allowances (折讓) for cross-period corrections.
Passed 20 of 22 test cases with the skill, and 13 of 22 without it.
and 8 more in the full report
7 fixed13 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
A buyer placed an order on November 5th and requested a return on December 20th. The operations team asks if an allowance is needed since December is a month later. What is the correct decision?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends an invoice void instead of an allowance. | Missed | Passed |
| States that November and December fall in the same bimonthly tax period. | Missed | Passed |
The instructions your model reads when the skill loads.
STATUS: SKELETON — body pending.
tw-tax-basicsTODO: void vs 折讓, bimonthly boundary, accounting implications.
NOTE (填充時): 此 skill 只寫「選哪條路」的決策邏輯，不重複 API 呼叫細節。
tw-ecom-invoice-ezpay 已有完整的 void_invoice / issue_allowance / trigger_allowance 步驟；
tw-ecom-invoice-universalec 同理。此 skill 的 Implementation guidance 應只提供判斷框架，
並用 "→ see tw-ecom-invoice-ezpay / -universalec" 指向 API 層。
TODO: given refund date vs issuance date → void or 折讓.
TODO: 決策路徑後的 SOP（accounting entries, customer notification, 字軌影響）。 不重複 void_invoice / issue_allowance / trigger_allowance 的 API 參數 — 那些在 ezpay/universalec skill。
TODO: 5-6 pitfalls (boundary off-by-one, 字軌 reservation, lottery invalidation, allowance numbering).
TODO.
test cases passed, vs 13 / 22 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.