360 Secure SkillHub
360 安全技能中心

paper-context-resolver

README 优先复现流程中的可选 helper:当 README 与仓库文件留下复现关键缺口(数据集划分、预处理、评测协议、检查点映射或运行时假设)时,从一手论文来源补充窄范围证据,标注 README 与论文冲突,并区分直接证据与推断;不替代主流程。

lllllllama
热度 0.00
最近更新 2026-10-18 15:53:53
分类:知识依赖:纯提示词应用场景:研究

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add lllllllama/rigorpilot-skills/paper-context-resolver
Metadata
name
paper-context-resolver
description
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 summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.

paper-context-resolver

Use this as the Rigor Paper Context helper. The installed slug remains paper-context-resolver for compatibility.

When to apply

  • 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.

When not to apply

  • The README already gives enough reproduction detail.
  • The user wants a general paper explanation rather than reproduction support.
  • The goal is to override README instructions without documenting the conflict.
  • The only available input is a paper title and there is no concrete reproduction gap yet.

Clear boundaries

  • 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.

Input expectations

  • target repo metadata
  • reproduction-critical question
  • existing README or repo evidence
  • any already known paper links

Output expectations

  • narrowed source list
  • reproduction-relevant answer only
  • explicit README-paper conflict note when applicable
  • clear distinction between direct evidence and inference

Notes

Use references/paper-assisted-reproduction.md.