reproducibility-third-party-verification
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
(Proposal, unverified) Attempt to verify a paper's reported results by actually executing its released code/scripts against its own reported configuration — the only SOP in this package whose action type is code execution rather than text reading/judgment. Use this after unit-classification has extracted the paper's reported configuration/hyperparameters as classified units; "not_attempted" is a correct, common output when the paper's own reporting is too incomplete to run, not a failure of this SOP.
In this repository34 other files it gives its agents.
- acu-nugget-recallSkill
- argumentative-zoningSkill
- atomic-unit-matchingSkill
- atomic-unit-recall-aggregateSkill
- atomic-unit-writingSkill
- claim-label-predictionSkill
- claim-writingSkill
- domain-level-judgmentSkill
- dual-column-self-checkSkill
- engineering-config-gradingSkill
- first-pass-skimSkill
- keshav-three-passSkill
- multi-stage-cascade-extractionSkill
- paper-fetchSkill
- qalmriSkill
- qalmri-worksheetSkill
- qasper-evidence-qaSkill
- quality-appraisal-checklistSkill
- question-framingSkill
- rationale-selectionSkill
- reforms-gradingSkill
- reporting-standard-checklistSkill
- research-question-appraisalSkill
- rhetorical-structure-qualitySkill
- second-pass-graspSkill
- signalling-question-answeringSkill
- star-awardingSkill
- study-design-tool-gateSkill
- sum-threshold-scoringSkill
- template-slot-fillingSkill
- third-pass-deep-readSkill
- unit-classificationSkill
- unit-segmentationSkill
- worst-case-lookupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
No primary-source precedent, no inter-rater-reliability baseline.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reproducibility Third-Party Verification (Proposal)
Actually runs code to check reported results against the paper's own extracted configuration — unique action type (execution) in this package. Fills the evidence-verification × engineering-metadata gap in the evaluative-stance × content-layer matrix.
Execution
Subagent — spawned via spawn-agent skill.
Dependency: unit-classification, not raw full_text (graph correction L20)
This SOP needs the paper's reported configuration already pulled out in structured form before attempting to verify it — hence its input is classified_units, not full_text directly. An earlier graph draft had this SOP depending on nothing upstream, which meant it had no defined way to get the structured claims it needs to check.
Proposal Status — Read Before Modifying
No primary-source precedent, no inter-rater-reliability baseline. Keep "(Proposal, unverified)" in the description until real usage validates the method. Given the code-execution action type, treat any scope expansion here with more caution than the other 3 proposal SOPs.
<!-- BEGIN available-tables (generated) -->Available SOPs
| SOP | When to use |
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. |
<!-- END available-tables (generated) -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.