Paper Context Resolver Skill Security Audit
What the author says it does (original text)
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper s
No obvious risks found in this check
- Files checked
- 3
- Risks found
- 0
Inside this skill
This Skill is an optional helper used only when the README and repository leave a specific reproduction-critical gap. Its scope is limited to datasets, preprocessing, evaluation, checkpoint mapping, and runtime assumptions; it is not intended for general paper summaries or command execution.
View source
- README and repo files leave a reproduction-critical gap.- The gap concerns dataset version, split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions.- The main skill needs a narrow evidence supplement instead of a full paper summary.- There is already a concrete reproduction question to answer.- This skill is optional.- This skill is helper-tier and should usually be orchestrator-invoked.- It supplements README-first reproduction.- It does not replace the main orchestration flow.- It does not summarize the whole paper by default.Sources are prioritized from README-provided links through official pages and arXiv/OpenReview; Google Scholar is used only to locate a primary source. The supplied files contain no scripts, installation steps, or instructions to execute downloaded content.
View source
## Source order1. paper link explicitly provided by the README2. official project page or official paper page3. arXiv or OpenReview primary paper record4. Google Scholar only to help locate the primary sourceIf the paper and README disagree, the Skill requires both positions to be recorded and forbids silently replacing the README, reducing the risk of concealed changes to reproduction parameters or user decisions.
View source
## Conflict ruleIf README and paper disagree:- do not silently replace README- record the conflict- explain which source says what- preserve the README-first policy in the final reportFile reference map
References: 1Files and check records3 files
Coverage and gaps
Content covered in each file
These are the source ranges included in this check, not a guarantee that every issue has been resolved.
SKILL.mdFull text includedreferences/paper-assisted-reproduction.mdFull text includedagents/openai.yamlFull text included
This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.
SKILL.mdInstructionsagents/openai.yamlSupporting filereferences/paper-assisted-reproduction.mdSupporting file
Operations mentioned in code and instructions
Read files
- README and repo files leave a reproduction-critical gap.- The gap concerns dataset version, split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumptions.- Lines read
- 105
- File checksum (to compare versions)
- 13d5a4a97ee0be5151c23aefaba03cacb43b1a3b716c6cf605422610d545320a