Sync Portaly donation notification emails (Gmail) into the supporters SSOT via canonical SUPPORTERS-PIPELINE — checkpoint from last_fetched, read full email bodies (never snippets, since amount/monthly-type can be truncated), dry-run before write, regen the two privacy-partitioned derived views for /about#sponsors, verify no cross-layer privacy leak before commit. TRIGGER when: user says "抓贊助", "更新贊助者", "跑 Portaly", "supporters sync", or routine `twmd-supporters-weekly` fires.
SkillScore77Maintained
Automatic
◆Data Engineer pack
Last verified 8/16/2026
What it changes
Passed 15 of 19 test cases with the skill, and 9 of 19 without it.
Without skill45%
With skill77%
Checks it passed that the model alone missed
Appends an entry to the lessons log.
Reads the last_fetched property from transactions.json.
Limits git staging to the three designated pipeline files.
and 4 more in the full report
7 fixed10 passed either way5 still failing0 broke
Pass-rate lift
+32 pp
Tokens
-21%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/16/2026v117 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
What privacy rule must be verified for the generated about section view before staging files in the supporter pipeline?
What was checked, without and with the skill
Checked
Without skill
With skill
Verifies that individual donation amounts are absent from the about view.
Missed
Passed
case-09 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.