ワンクリックで
paper-repo
找论文的代码仓库。 当用户问"代码在哪"、"有没有实现"、"帮我找 repo"、 "官方代码"、"复现"、"复现代码"、"开源实现"、 "开源代码"、"GitHub 地址"时触发。 验证仓库真实性后自动 clone。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
找论文的代码仓库。 当用户问"代码在哪"、"有没有实现"、"帮我找 repo"、 "官方代码"、"复现"、"复现代码"、"开源实现"、 "开源代码"、"GitHub 地址"时触发。 验证仓库真实性后自动 clone。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
一键导入论文:从标题/DOI/链接/模糊描述开始,自动走完 resolve → acquire → repo 管线。 当用户说"导入这篇论文"、"帮我把这篇论文弄下来"、"下载这篇论文"、 "把这篇论文弄到本地"、"帮我搞定这篇论文"时触发。 覆盖从搜索到下载到找代码的全流程。如果用户只需要搜索/确认论文身份, 不需要下载,应使用 paper-search skill。 三步默认全部执行:确定论文 → 获取 PDF+markdown → 找代码仓库。 用 --no-acquire 跳过下载,--no-repo 跳过代码搜索。
搜索论文并解析论文身份,生成结构化 metadata.yaml。 当用户要搜论文、找文献、确认论文身份(标题/DOI/arXiv ID/URL)、 查论文信息、做论文 metadata 时触发。 不负责下载 PDF 或转 markdown(那是 paper-acquire 的工作)。 覆盖 20+ 学术源(arXiv、PubMed、Semantic Scholar、Crossref、OpenAlex、DBLP、Unpaywall 等)。 如果用户想要"导入论文"(全流程),应使用 paper-import skill。 如果用户只要"下载论文"或"获取 PDF",应使用 paper-acquire skill。
获取论文原文:下载 PDF 并转成结构化 markdown。 当用户要求下载论文、获取 PDF、把论文转成 markdown 时触发。 也作为 paper-search 的下游自动步骤——确定了论文身份后自动获取原文。
PDF 转高质量 markdown,支持公式、表格、混合排版。 当用户要求 PDF 转 markdown、提取论文文本、OCR 提取时触发。 注意:paper-acquire 内部会调用它,不需要单独触发。
把一篇论文拆解成结构化研究卡片。 当用户说"做个卡片"、"写阅读笔记"、"总结这篇论文"、 "帮我读一下"、"结构化分析"、"拆解论文"时触发。 输出 card.md(快速概览)和 card-deep.md(深度分析)。
| name | paper-repo |
| description | 找论文的代码仓库。 当用户问"代码在哪"、"有没有实现"、"帮我找 repo"、 "官方代码"、"复现"、"复现代码"、"开源实现"、 "开源代码"、"GitHub 地址"时触发。 验证仓库真实性后自动 clone。 |
| argument-hint | <folder_slug> | <metadata_path> |
Discover implementation repository for a paper.
This skill owns:
metadata.yaml → repo_search sectionrepo/ → cloned repository (when confidence is high/medium)This skill does not:
identity or bibliography sectionsStep 1: Extract clues from paper content (scripts)
→ PDF metadata URLs
→ paper.md code links + context
→ Output: candidate URLs with evidence
Step 2: Search GitHub if needed (web-kit)
→ ask-search "{title} site:github.com" -e google -n 10
→ ask-search "{method_name} github" -e google -n 10
→ Add search results to candidates
Step 3: Verify candidates (web-kit)
→ crwlr crawl -o md "{repo_url}"
→ Judge: official vs reimplementation, author match, code-paper alignment
Step 4: Select best candidate and clone (if confidence >= medium)
→ git clone {repo_url} repo/
→ Update cloned_to in metadata.yaml
Step 5: Write repo_search to metadata.yaml
→ selected: best candidate with confidence
→ candidates: all found with sources
Read from:
$PAPERS_DIR/{folder_slug}/metadata.yaml
bibliography.authors — for author verificationbibliography.venue — for contextidentity.aliases.doi — for citation matching$PAPERS_DIR/{folder_slug}/paper/paper.pdf$PAPERS_DIR/{folder_slug}/paper/paper.mdWrite to metadata.yaml:
repo_search:
selected:
url: "https://github.com/owner/repo"
confidence: "high" # high / medium / low / none
source: "paper_md" # paper_pdf / paper_md / github_search
evidence:
- "README cites the paper DOI: 10.xxx"
- "Author names match: Hongbin Pei"
type: "official" # official / community / reimplementation
cloned_to: "repo/" # filled after git clone
candidates:
- url: "https://github.com/owner/repo"
source: "paper_md"
confidence: "high"
context: "Code availability section mentions this URL"
- url: "https://github.com/other/repo"
source: "github_search"
confidence: "low"
context: "Name similarity only"
Auto-clone when:
confidence is high or mediumDo not clone when:
confidence is low or none--no-clone flag# Clone command (use Bash tool, not PowerShell)
cd $PAPERS_DIR/{folder_slug}
git clone {repo_url} repo/
Windows / NTFS: Some repos contain paths with characters invalid on NTFS (e.g.
:in timestamps). Ifgit clonecheckout fails with path errors: download the repo as a zip archive instead, do not extract it. Record in metadata.yaml:cloned_to: "repo.zip" clone_note: "Archive only — contains NTFS-incompatible paths"
After cloning, update cloned_to field in metadata.yaml.
Extract URLs from PDF metadata and annotations.
uv run --script "${SKILL_DIR}/scripts/extract_urls_from_pdf.py" $PAPERS_DIR/{folder_slug}/paper/paper.pdf
Output: JSON list of URLs found in PDF with source annotation.
Extract code-related links from paper.md with surrounding context.
uv run --script "${SKILL_DIR}/scripts/extract_code_links_from_md.py" $PAPERS_DIR/{folder_slug}/paper/paper.md
Output: JSON list of code links with context lines.
| Criterion | How to check |
|---|---|
| DOI citation | README or repo description contains paper DOI |
| Author match | GitHub owner name matches one of bibliography.authors |
| Method name | Repo name contains the method name from title |
| Paper link | README links to arXiv/publisher URL from urls.canonical |
| Code alignment | Repo implements the core algorithm described in paper |
| Level | Criteria |
|---|---|
high | DOI citation + author match + official implementation stated |
medium | Repo matches method name + README mentions paper, but no author match |
low | Only name similarity, no explicit paper connection |
none | No candidate found or clearly unrelated |
Priority order:
paper.md → Code availability section, footnote linkspaper.pdf → PDF metadata URLs, annotation linksPaper often explicitly states: "Code is available at https://github.com/..."
When paper content has no explicit link:
# Search by paper title + github
ask-search "{paper_title} github" -e google -n 10
# Search by method name (if identifiable)
ask-search "{method_name} github" -e google -n 10
# Direct GitHub search via site:
ask-search "site:github.com {method_name}" -e google -n 10
If GitHub search yields no high-confidence result, try general search (code may be on author homepage, project page, or as ZIP download):
ask-search "{paper_title} code download" -e google -n 5
ask-search "{first_author} {method_name} code" -e google -n 5
For each candidate URL:
${SKILL_DIR}/../web-kit/scripts/crwlr crawl -o md "{repo_url}"
Look for:
This skill runs after paper-acquire.
Use paper-import for end-to-end workflow including repo discovery.
| File | When to read |
|---|---|
| repo-verification.md | Need detailed verification criteria |