One-click install
npx skills add https://github.com/zjunlp/Mechanist --skill auto-verify-zjunlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-verify
Source: https://github.com/zjunlp/Mechanist/tree/main/skills/auto-verify
Command: npx skills add https://github.com/zjunlp/Mechanist --skill auto-verify-zjunlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Main-experiment results can be fragile artifacts of a specific method, dataset, or model choice. This Skill stress-tests each research claim by running controlled swap variants and computing a robustness score, so you know whether a finding survives independent replication or collapses under a different setup. ## Core Features & Use Cases - Three-Stage Verification Pipeline: Audits the main experiment's evaluation and mechanism rigor, runs swap variants on top-priority claims, then judges each variant against the frozen claim with binary pass/fail verdicts. - Dual Integrity Gates: Cross-model audits (experiment methodology plus mechanism-intervention rigor) gate both the main experiment and every variant, excluding untrusted runs from the robustness calculation. - Robustness Scoring with Five Terminal States: Computes robustness = passing variants / eligible variants and assigns PASS, FAIL, INCONCLUSIVE, ZERO_ELIGIBLE_VARIANTS, or INTEGRITY_ONLY per claim. - Use Case: After running experiments that appear to support a claim about LLM internal mechanisms, invoke verification to swap the model or dataset and confirm the conclusion holds before writing it into a research report. ## Quick Start Ask the agent to verify claim C1 with a robustness threshold of 0.67 and dimensions set to method and dataset.

Frequently Asked Questions about auto-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a research claim with swap variants?

Invoke the skill with a claim id such as C1, or leave the argument empty to target all claims. It audits the main experiment, runs one swap variant per selected dimension (method, dataset, model), then computes a robustness score to assign PASS or FAIL.

What does the robustness score mean in claim verification?

Robustness equals the number of passing variants divided by eligible variants that survived the integrity audit. A claim passes when robustness meets the threshold, default 0.5, meaning at least half of eligible variants must agree with the main experiment verdict.

Can I run only the integrity audit without swap variants?

Yes, set swap-variants to false for audit-only mode. The main-experiment audit still runs per claim and writes an INTEGRITY_ONLY or INCONCLUSIVE result, skipping all variant execution and GPU usage.

What is the difference between INCONCLUSIVE and ZERO_ELIGIBLE_VARIANTS?

INCONCLUSIVE means the main experiment failed its integrity audit, so variants never ran and iteration must fix the main experiment. ZERO_ELIGIBLE_VARIANTS means variants ran but all failed their own integrity audit, so only the variant evaluation needs fixing.

How do I resume an interrupted verification run?

Re-invoke with resume set to true. Each phase checks whether its primary artifact already exists on disk and skips completed work, including per-claim audits, variant runs, and verdict files, without deleting prior outputs.

How many claims and variants does one verification pass cover?

By default one claim per pass (MAX_VERIFY_CLAIMS=1) with one variant per listed dimension, so the default model-only dimension yields one variant run. Raise the cap or broaden dimensions to expand coverage.