stage-evid-curator

Import, register, and audit read-only research evidence files against a manifest.

2|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/wanghao9610/STAGE --skill stage-evid-curator-wanghao9610
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stage-evid-curator
Source: https://github.com/wanghao9610/STAGE/tree/main/.qwen/skills/stage-evid-curator
Command: npx skills add https://github.com/wanghao9610/STAGE --skill stage-evid-curator-wanghao9610

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Academic manuscripts lose credibility when numbers in the draft cannot be traced to their source files, or when evidence files are silently edited after claims are written. This Skill maintains a fingerprinted, read-only evidence store (mates/) with a manifest that records each file's provenance, checksum, and upstream commit, so every number in the paper traces to a verifiable source. ## Core Features & Use Cases - Import from a paired STAR repo: Runs execs/scpts/import.sh to pull or refresh result files, pinning each file's upstream commit in mates/MANIFEST.md as source-type: star entries, with confirmation before any rewrite of registered entries. - Register hand-dropped evidence: Adopts files under mates/manual/ as source-type: manual entries after reading them in full, asking for provenance, computing sha256, and stamping the real date. - Reconciliation check: Grades every file ok, unregistered, missing, tampered, or stale by comparing disk against the manifest, and reports the exact command that fixes each non-ok row. - Use Case: After a STAR experiment run produces updated results, run the import mode to refresh the evidence, then route to the table builder and claims auditor so tables and claims citing moved numbers get re-checked. ## Quick Start Ask the assistant to run stage-evid-curator in check mode to reconcile the mates/ evidence store against its manifest and report any unregistered, missing, tampered, or stale files.

Frequently Asked Questions about stage-evid-curator

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

FAQPage Schema
How do I import experiment results from a STAR repository into my paper project?

Run the skill in import mode, which executes execs/scpts/import.sh to pull results from the repo pointed to by STAR_HOME in .env. The script pins each file's upstream commit in mates/MANIFEST.md, and any rewrite of already-registered entries is confirmed with you before running.

How do I register a result file that was added manually?

Use register mode with the file path; the file is read in full, copied under mates/manual/ if needed, and you are asked for its source and coverage. The skill then computes its sha256 and writes a source-type: manual manifest entry with the current date.

Can I fix a wrong number by editing an evidence file directly?

No. Evidence files are read-only by design; a wrong number must be fixed at its source, such as the STAR repo or original document, then re-imported or re-registered. In-place edits are detected as tampered during integrity checks.

What does the evidence check report when files and manifest disagree?

The check grades each file ok, unregistered, missing, tampered, or stale. Unregistered means no manifest entry exists, missing means the file is gone, tampered means the sha256 no longer matches, and stale means the upstream STAR commit moved past the pinned stamp.

Does evidence import work without a paired STAR repository?

Yes, partially. If STAR_HOME is unset in .env, star imports and staleness checks are unavailable and this is stated up front, but manual evidence registration and integrity checks via sha256 work fully offline.