← Back to list

compare-friction-outputs
by davidjiyangcai
⭐ 0🍴 0📅 Jan 20, 2026
SKILL.md
name: compare-friction-outputs description: Compare friction pipeline outputs across different runs, thinking levels, or seeds. Use when comparing visa research results, checking variance across thinking levels (minimal/low/medium), analyzing fee discrepancies, or reviewing route selection consistency. allowed-tools: Read, Glob, Grep, Bash
Compare Friction Pipeline Outputs
Compare outputs from the orig_dest_occ_friction pipeline across different runs to analyze variance and consistency.
When to Use
- Comparing results across thinking levels (minimal, low, medium)
- Checking if route selections are consistent
- Investigating field value variance (fees, salaries, processing days)
- Verifying synthesis decisions
Key File Locations
src/orig_dest_occ_friction/
├── artifacts_v8_minimal/
│ └── [triple]/
│ ├── output.json # FINAL extracted values (use this!)
│ ├── panel.csv # Yearly panel expansion
│ └── workspace/
│ ├── research.md # Full research with worker synthesis
│ ├── todos.json # Field completion status
│ └── year_routes.json # Route selection
├── artifacts_v8_low/
└── artifacts_v8_medium/
Comparison Workflow
1. Find artifact directories
ls -d src/orig_dest_occ_friction/artifacts_*
2. Find common triples
ls src/orig_dest_occ_friction/artifacts_v8_minimal/
3. Compare route selections
For each triple, extract first route from output.json → year_routes.
4. Compare field values
Key fields to compare:
application_fee_applicant- Total mandatory feessalary_min- Minimum salary thresholdrepresentative_days- Processing timepr_years_required- Years to permanent residencyjob_loss_grace_period_days- Grace period after job loss
5. Use the comparison script
uv run python scripts/compare_friction_outputs.py artifacts_v8_minimal artifacts_v8_low artifacts_v8_medium
Understanding research.md Structure
The workspace/research.md file has multiple sections:
- Worker Reports (top) - 3 parallel workers with potentially different findings
- Step 1: Decisions - Synthesis rationale explaining which worker was chosen
- Step 2: Search Queries/Results - Verification searches
- Step 3: Final Synthesis - THE ACTUAL OUTPUT VALUES (matches output.json)
IMPORTANT: Always compare using output.json or "Step 3: Final Synthesis", NOT the individual worker reports at the top of research.md.
Investigating Variance
When values differ across runs:
- Read the full
research.mdfor each run - Check "Step 1: Decisions" for the rationale
- Look for which worker was selected and why
- Check if the variance is due to:
- Different fee components included
- Historical data interpretation differences
- Source availability differences
Output Format
=== ROUTE SELECTIONS ===
Triple minimal low medium
australia_china_2211 Subclass 457 Subclass 457 Subclass 457
=== FIELD COMPARISON ===
australia_china_2211:
⚠️ application_fee_applicant: (⚠️ = values differ)
minimal: 765
low: 265
medium: 615
salary_min: (no marker = consistent)
minimal: 47480
low: 47480
medium: 47480
Score
Total Score
50/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon