9527CODE 技术博客
← 返回博客列表

paper-context-resolver

由 lllllllama 提供的 paper-context-resolver Skill,包含安装方法、功能说明、完整指令和 GitHub 原文入口。


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.


功能说明

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.

快速安装

npx skills add https://github.com/lllllllama/rigorpilot-skills --skill paper-context-resolver

交给 AI 助手使用

以下是页面提示词的中文转述,命令保持原样。

运行 npx skills use "https://github.com/lllllllama/rigorpilot-skills" --skill "paper-context-resolver",完整阅读输出并按 Skill 说明操作。必要时先将输出保存到临时文件;相对路径以输出提供的支持文件目录为准。

补充说明

Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical...


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.

来源与许可

lllllllama/RigorPilot-Skills 提供此 Skill,适用 MIT。本版本追加了安装和访问入口,并将相对文档链接解析为 GitHub 地址;原始文件可从下方原文入口获取。

MIT License

Copyright (c) 2026 Chengkun Rao

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

在 GitHub 查看原文

查看更多详情

原文作者:lllllllama

来源网站:GitHub