Syncs TripIt travel itineraries to Reclaim.ai timezone segments and Google Calendar OOO blocks.
93
97%
Does it follow best practices?
Impact
85%
1.49xAverage score across 4 eval scenarios
Advisory
Suggest reviewing before use
Reads from input path
75%
12%
Writes to correct env file path
0%
40%
File permissions set to 600
0%
50%
Telegram vars excluded
0%
60%
SNS var excluded
0%
60%
Mandatory vars included
0%
60%
Trip filtering var included
0%
62%
Incomplete Google OAuth detected
28%
71%
Dry-run attempted
0%
10%
Dry-run failure handled
0%
10%
Run 1 identified as no-change
100%
100%
Run 2 identified as no-change
100%
100%
Decision is silence
100%
100%
Does not report existing segments as changes
100%
100%
Does not fabricate diff between runs
100%
100%
Does not report null OOO as a problem
100%
100%
Reasoning is provided
100%
100%
Does not run the sync
100%
100%
Both runs processed
100%
100%
Concise output
100%
100%
Existence check before install
0%
100%
Correct download URL
0%
100%
User-space install path
0%
100%
npm ci with --omit=dev
0%
100%
Post-install verification
0%
100%
Install failure aborts
0%
100%
Correct sync command
0%
100%
JSON output captured to file
60%
100%
Exit code propagation
100%
100%
Non-zero exit on sync failure
100%
100%
Report is not empty
100%
100%
Created timezones reported with context
100%
100%
Deleted timezone reported separately
100%
100%
OOO block counts reported
100%
100%
Conflict warning with both trip names
100%
100%
Conflict date included
100%
100%
Error reported
100%
100%
Error contextualized
80%
50%
Uses trip labels from segments
100%
100%
No fabricated data
80%
100%