Passed 19 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill86%
Checks it passed that the model alone missed
The response enforces mutual exclusivity in the UI when B2B tax invoice is selected.
The response validates that selected donation codes match the 3-7 digit numeric pattern.
The response recommends syncing updated carrier choices back to user profile during checkout.
and 8 more in the full report
8 fixed11 passed either way3 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+19%
Agent turns
0%
Response time
-3%
Model gemini-3.6-flashMeasured 8/28/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
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.
What was checked, without and with the skill
Checked
Without skill
With skill
The response frames carrier as a Taiwan e-invoice electronic carrier (載具) rather than a shipping or freight carrier like FedEx or UPS.
Missed
Passed
The response specifies validation rules for mobile barcodes using a leading slash followed by seven alphanumeric characters.
Missed
Passed
case-01 · gemini-3.6-flash · 8/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md50 linessingle file
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