Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

E-Invoice Carriers (載具) · asgard-ai-platform | DecimalAI

asgard-ai-platform/tw-ecom-invoice-carrier

NewSkillScoreMaintained

Handle Taiwan e-invoice carriers (載具) — 手機條碼, 自然人憑證, 會員載具, plus 捐贈碼 donation flow. Covers carrier validation, scan-to-store UX, member-carrier consolidation, and prize-draw winner notification. Use when designing carrier scanning UX, debugging invalid-carrier rejections, or implementing donation-code flow. STATUS: SKELETON — body pending.

by asgard-ai-platform

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Frontend / UI pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/asgard-ai-platform-tw-ecom-invoice-carrier/SKILL.md

decimalai skills pull asgard-ai-platform-tw-ecom-invoice-carrier --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/asgard-ai-platform-tw-ecom-invoice-carrier/SKILL.md https://app.decimal.ai/s/asgard-ai-platform-tw-ecom-invoice-carrier/SKILL.md

Raw file: /s/asgard-ai-platform-tw-ecom-invoice-carrier/SKILL.md ↗ · machine-readable summary at /s/asgard-ai-platform-tw-ecom-invoice-carrier.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 27h ago

Yes — +36% lift+19% tokens0% turns86% of whole cases pass with skill (19/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	-3%	0%
case-05	✗→✓	▲ Improved	7%	0%
case-07	✗→✓	▲ Improved	0%	0%
case-08	✗→✓	▲ Improved	-8%	0%
case-14	✗→✓	▲ Improved	42%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

asgard-ai-platform / skills

tw-ecom-invoice-carrier/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

Skill contents

SKILL.md

E-Invoice Carriers (載具)

> STATUS: SKELETON — body pending.

When to use this skill

Designing carrier-scan UX at checkout
Implementing member-carrier consolidation
Adding 捐贈碼 donation flow
Handling prize-draw (中獎) winner notification
Debugging carrier-format rejections

Do NOT use when

Landscape overview → tw-einvoice-guide
Specific 加值中心 API → tw-ecom-invoice-ezpay / -universalec

Core concepts

TODO: carrier types, format specs, validation rules. NOTE (填充時): 格式規格（手機條碼 / + 7 alphanumeric、自然人憑證 2 letters + 14 digits）已在 tw-ecom-invoice-ezpay Gotchas 中詳細說明。此 skill 不重複格式規格；改聚焦在 UX 層面：validation 在哪層做、錯誤訊息設計、掃碼元件選型。

Decision tree

TODO: which carrier to default to given context (e.g., 有會員帳號 → 會員載具；無帳號 → 引導填手機條碼；B2B → 不需載具).

Implementation guidance

TODO: scan widget 選型與整合、client-side validation 流程、member-carrier linking（會員帳號與手機條碼綁定）。不重複 issue_invoice carrier_type / carrier_num 參數說明 — 那些在 ezpay/universalec skill。

Gotchas

TODO: 5-6 pitfalls.

IRON LAW

TODO.

Output Format

TODO.

tw-einvoice-guide

_Last verified: 2026-04_

Want to see if asgard-ai-platform/tw-ecom-invoice-carrier would activate on your phrasing? Try it before you install — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/28/2026, 07:02 UTC · 22 cases

Lift

+36%

86% vs 50%

Agent turns

1.0 vs 1.0

Tokens

+19%

3,401.95 vs 2,860.55

fail → pass · 8pass → pass · 11fail → fail · 3

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-11 We are re-architecting our Taiwan store checkout invoice selection module. What default invoice type should be selected for logged-in members versus guest users?	pass→pass	19,785	18,646	-6%	1	1	0%	2,699	3,241	+20%	0	0	—
case-04 A developer is configuring the checkout invoice form and wants to reuse the mobile barcode text field regex for donation codes (捐贈碼). How should the donation code input validation and workflow be structured?	fail→fail	20,339	15,575	-23%	1	1	0%	3,520	3,169	-10%	0	0	—
case-01 We are adding a member carrier consolidation feature where store members can link their mobile barcode to their account. Please create a technical design guide with a step-by-step user interaction flow, state management considerations, and frontend validation patterns for carrier registration.	fail→pass	51,750	27,698	-46%	1	1	0%	4,803	4,654	-3%	0	0	—
case-02 We are building an e-commerce checkout page for Taiwanese customers where users can input their mobile invoice barcode. Designers want to know how to handle the barcode scanning input component on mobile web. Provide a component selection and interaction recommendation.	pass→pass	19,261	21,193	+10%	1	1	0%	2,949	3,198	+8%	0	0	—
case-03 Our checkout team argues that mobile barcode validity should only be checked by calling the Ministry of Finance API on final order submit to prevent client-side bypass. Provide a recommended validation architecture for mobile barcode input.	pass→pass	17,263	17,204	-0%	1	1	0%	2,741	3,264	+19%	0	0	—
case-05 When a member logs into our online shop and completes a purchase using a mobile barcode, should the system silently bind this mobile barcode as their default member carrier for future orders? Detail the UX rules for member carrier binding.	fail→pass	16,717	16,252	-3%	1	1	0%	2,810	2,993	+7%	0	0	—
case-06 We need to add support for Citizen Digital Certificate carriers (自然人憑證載具) on our invoice settings page. What validation rules should be implemented on the frontend for this carrier type?	pass→pass	13,865	10,171	-27%	1	1	0%	2,605	2,223	-15%	0	0	—
case-07 In our invoice UI design, a user wants to enter both their company tax ID (統一編號) for business expense claiming and their personal mobile barcode to win invoice prizes. How should the checkout form handle this option combination?	fail→pass	16,822	13,932	-17%	1	1	0%	2,595	2,588	-0%	0	0	—
case-08 Our customer service team wants us to build an automated email notification system that alerts customers whenever an invoice issued to their mobile barcode wins a prize in the Taiwan lottery. Explain how prize notifications should be handled.	fail→pass	17,015	14,457	-15%	1	1	0%	2,973	2,741	-8%	0	0	—
case-09 Users frequently report errors when entering their mobile barcode on our checkout page. Design user-friendly error messages for common entry mistakes like missing slashes or invalid characters.	pass→pass	12,720	21,727	+71%	1	1	0%	2,058	4,643	+126%	0	0	—
case-10 How should the frontend input handler process raw text entered by a user into the Taiwan mobile invoice barcode field before running regex validation?	pass→pass	17,597	16,234	-8%	1	1	0%	2,583	3,321	+29%	0	0	—
case-12 Our retail app has both physical kiosk mode and web checkout mode. How should the carrier barcode input field handle input from handheld hardware barcode scanners?	pass→pass	21,442	19,527	-9%	1	1	0%	3,036	3,595	+18%	0	0	—
case-13 Design a member account invoice preference screen where members can manage their saved carriers. What fields and interactions should be included?	fail→fail	18,095	19,572	+8%	1	1	0%	3,144	3,691	+17%	0	0	—
case-14 During peak sale events, real-time validation calls to check if a mobile barcode exists might time out. How should the checkout UX handle carrier validation during high-concurrency periods?	fail→pass	15,928	18,456	+16%	1	1	0%	2,362	3,355	+42%	0	0	—
case-15 We want to optimize the donation invoice flow at checkout. How should the UX assist users who want to donate their invoice but do not know the exact donation code?	fail→pass	15,605	17,734	+14%	1	1	0%	2,446	3,702	+51%	0	0	—
case-16 What visual state indicators should be displayed on the mobile carrier input field during typing, blur, and submit events?	fail→fail	17,027	16,914	-1%	1	1	0%	2,349	3,200	+36%	0	0	—
case-17 If an asynchronous invoice issuance job fails because a user's mobile barcode was rejected post-checkout, what post-purchase recovery workflow should the application present to the customer?	pass→pass	16,578	21,382	+29%	1	1	0%	2,517	3,463	+38%	0	0	—
case-18 Where should a logged-in user's default carrier selection (mobile barcode vs member carrier) be stored in our application architecture?	fail→pass	14,117	12,655	-10%	1	1	0%	2,217	2,446	+10%	0	0	—
case-19 A developer on our team asks why the Member Carrier option doesn't ask the user for a barcode starting with a slash. Explain the UX difference between Member Carrier and Mobile Barcode.	fail→pass	13,848	15,352	+11%	1	1	0%	2,004	2,565	+28%	0	0	—
case-20 Can you provide a high-level overview of Taiwan's overall E-Invoice regulatory framework, including turnkey options, B2C vs B2B tax requirements, and Ministry of Finance compliance phases?	pass→pass	22,431	21,727	-3%	1	1	0%	3,387	3,902	+15%	0	0	—
case-21 We are integrating ezPay invoice API. Show me the exact JSON payload format and field parameters (MerchantID, Pos, CarrierType, CarrierNum) required to call the ezPay issue invoice endpoint.	pass→pass	18,345	30,116	+64%	1	1	0%	2,898	5,169	+78%	0	0	—
case-22 What are the required HTTP body parameters and signature generation rules for issuing a B2B invoice through UniversalEC gateway API?	pass→pass	26,939	22,914	-15%	1	1	0%	4,236	3,720	-12%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +36 percentage points is the difference between those two pass rates over the 22 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 50%
Pass rate with the skill: 86.4%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 0
Skill version measured: v1
Run completed: 8/28/2026, 07:02 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

We are adding a member carrier consolidation feature where store members can link their mobile barcode to their account. Please create a technical design guide with a step-by-step user interaction flow, state management considerations, and frontend validation patterns for carrier registration.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signalsno signals yet

BenchmarkRun a verified benchmark with positive lift

Live evalNeeds ≥20 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

No signals yet — run a benchmark or collect evaluated traces to earn a score.

Verified on gemini-3.6-flash · re-tested yesterday

Other measured skills in the registry, with their headline benchmark lift.