Paper Reading Zh
MrGeDiao/paper-reading-zh
中文论文深读、总结/TL;DR、工程拆解、按论文实现/复现、比较与证据审计。用户给出论文 PDF、链接、标题、摘要、正文或图表,或明确要读论文时使用。只有论文锚点且无附言时澄清阅读目标;只有阅读意图时问哪篇。已有论文时,“看看这篇”直接深读。不用于仅翻译、解释单个术语、生成 BibTeX、找或下载论文。
Extract citations from a PDF and generate a validated .bib file.
$ npx skills add flonat/flonat-research --skill bib-parse -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flonat/flonat-research bib-parse --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bib-parse .claude/skills/bib-parse && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bib-parse" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/bib-parse into .claude/skills/bib-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bib-parse", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/bib-parseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add flonat/flonat-research --skill bib-parse -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flonat/flonat-research bib-parse --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/bib-parse .agents/skills/bib-parse && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bib-parse" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/bib-parse into .agents/skills/bib-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bib-parse", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flonat/flonat-research --skill bib-parse -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flonat/flonat-research bib-parse --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/bib-parse .cursor/skills/bib-parse && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bib-parse" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/bib-parse into .cursor/skills/bib-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bib-parse", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/bib-parse--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add flonat/flonat-research --skill bib-parse -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flonat/flonat-research bib-parse --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/bib-parse .gemini/skills/bib-parse && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bib-parse" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/bib-parse into .gemini/skills/bib-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bib-parse", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install flonat/flonat-research bib-parseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add flonat/flonat-research --skill bib-parse -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/bib-parse .github/skills/bib-parse && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bib-parse" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/bib-parse into .github/skills/bib-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bib-parse", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flonat/flonat-research --skill bib-parse -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install flonat/flonat-research bib-parse --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/bib-parse .opencode/skills/bib-parse && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bib-parse" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/bib-parse into .opencode/skills/bib-parse/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bib-parse", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
bib-parseExtract citations from a PDF and generate a validated .bib file.
Bib Parse is an agent skill from flonat/flonat-research. Extract citations from a PDF and generate a validated .bib file. Use when the user asks to extract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies referenced works, constructs BibTeX entries, and verifies metadata.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Citation management and PDF. It works with LaTeX. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWriteBash(mkdir*)Bash(ls*)Bash(uv*)WebFetchWebSearchSkill(split-pdf)…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
uvFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Bib Parse loads about 3.8k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 1,701 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 1,701 words, ~3,774 tokens.
.claude/skills/bib-parse/SKILL.md (or your agent's skills folder).LIBRARY-FIRST RULE: ALWAYS check Paperpile membership by DOI (paperpile lookup-by-doi) for each parsed reference BEFORE generating new BibTeX entries. Topic/title search-library is a lossy discovery aid, NOT a membership test — never tag a reference NEW off a title-search miss. Reuse existing library entries instead of constructing from scratch. Enforced in Phase 2.3 per shared/reference-resolution.md § Membership Check.
Goal: given a PDF file, extract all cited references and produce a clean, validated .bib file.
.bib file for its references.bib file\begin{thebibliography} or numbered references.bib file and just need to validate it — use the configured bibliography validatorpaperpile export-bib instead (faster, more accurate)A single PDF file path. The PDF should contain a bibliography, reference list, or works cited section.
A .bib file, located by context:
articles/, paper-*/, project root) — write to the same directory as the input PDF, named references.bib (per project convention). If references.bib already exists, ask before overwriting — offer to merge or use a different name (e.g., extracted-refs.bib).~/vault/parsed-bibs/<slug>.bib, where <slug> describes the source (e.g. kasberger-algorithmic-cooperation-geb-2026.bib). This is the standing location for one-off parses (established 2026-06-14). Create the folder if absent.Any staged Paperpile-import entry (Phase 4.1) is written into a .bib under .paperpile-import/ next to the output .bib.
Use split-pdf to read the PDF contents. This handles large PDFs by splitting into chunks. Focus on the bibliography / references section — typically the last few pages. Identify:
[1] Smith, J. (2020)...)\bibitem entries (if the PDF was generated from LaTeX)Before running any enrichment queries, render the parsed reference list as a numbered table and ask the user to confirm the split is correct. A misparsed reference list (one citation accidentally split across two rows, or two citations merged into one) makes Phase 2 spend 30+ API calls on the wrong entries — expensive in time and rate-limit budget.
Detected N references. Confirm the split before I enrich each one:
| # | parsed reference (verbatim) |
|---|----------------------------|
| 1 | Bebchuk, L. A., Cohen, A., & Hirst, S. (2017). The agency problems of institutional investors... |
| 2 | Smith, J. (2020). Title... |
| ... | ... |
Anything wrong with the split? (Reply "ok" to proceed, or list the row numbers that need merging/splitting.)Skip the confirmation step if any of these:
\bibitem boundaries are unambiguousWhen the user flags a bad split, fix it and re-render the skeleton before proceeding. Don't proceed to Phase 2 with unaddressed split issues — that's exactly the failure case this gate prevents.
For each reference found, extract:
| Field | Priority | Notes |
|---|---|---|
| Authors | Required | Full names, {Last, First and Last, First} BibTeX format |
| Title | Required | Exact title from the reference |
| Year | Required | Publication year |
| Journal / Booktitle | Required (articles/proceedings) | Full journal name, not abbreviation |
| Volume / Number / Pages | If available | Standard bibliographic fields |
| Publisher | If available | For books and proceedings |
| DOI | Best effort | Extract if printed in the reference |
Large reference lists (50+ entries): process in batches of ~20. Verify each batch before moving to the next. Report progress: "Processed 20/87 references...". This caps the rate-limit blast radius if a batch fails.
For each extracted reference, verify and enrich using available tools:
web search to confirm the reference exists and pull missing metadata (DOI, volume, pages).scholarly CLI for multi-source enrichment:scholarly scholarly-search "<title>" --json — search by title across OpenAlex + S2 + Scopus + WoSscholarly scholarly-paper-detail <paper_id> --json — get full metadata including pre-formatted BibTeX (citationStyles), TLDR summary, and open access PDF link. When BibTeX is available, use it as the primary template instead of manually constructing entries — reduces formatting errors.scholarly openalex-lookup-doi <doi> --json — get full metadata if DOI was found.Important: do NOT silently replace the extracted metadata with search results. If there's a conflict (e.g., different year, different spelling of author name), flag it as a note field in the .bib entry and keep the original from the PDF.
For each parsed reference, check if it already exists in Paperpile using the resolution order from shared/reference-resolution.md:
paperpile lookup-by-doi --doi <DOI> for each parsed reference (verify the DOI itself first if unsure). This is the membership test. Batch ≥6 references via one Bash sub-agent returning a merged {doi: citekey-or-null} map.paperpile search-library with first-author surname + title keywords (limit ≥10) — a discovery aid, not a membership test.NEW — never tag NEW off a search-library miss alone. Foundational classics (Simon, March, Levinthal, Cyert & March, …) are the most common false NEW; check them by DOI too.Status summary:
| Paperpile | Status | Phase 4.1 action |
|---|---|---|
| Yes | ALREADY IN PAPERPILE | Skip (reuse key) |
| No | NEW | Stage as BibTeX for Paperpile import |
Graceful degradation: if the paperpile CLI is unavailable, skip with a warning and treat all references as NEW.
Better BibTeX conventions:
{Author}{Year}-{xx} — e.g., Smith2020-xy.bib, match the key format already in useexport-bib is @misc/thin). Add note = {key reconciled to Paperpile <key>}. Full rule + first-author-match guard: shared/reference-resolution.md § Key Reconciliation.| Source type | BibTeX type | Key fields |
|---|---|---|
| Journal article | @article | author, title, journal, year, volume, number, pages |
| Conference paper | @inproceedings | author, title, booktitle, year, pages |
| Book | @book | author/editor, title, publisher, year |
| Book chapter | @incollection | author, title, booktitle, publisher, year, pages |
| Working paper / preprint | @techreport or @unpublished | author, title, institution/note, year |
| Thesis | @phdthesis or @mastersthesis | author, title, school, year |
| Website / online | @misc | author, title, howpublished, year, note |
Write entries to the output .bib file with:
note field for any metadata conflicts or uncertainties flagged in 2.2Example entry:
@article{smith2020optimal,
author = {Smith, John and Doe, Jane},
title = {Optimal Decision Making Under Uncertainty},
journal = {Management Science},
year = {2020},
volume = {66},
number = {3},
pages = {1234--1256},
doi = {10.1287/mnsc.2019.3456}
}Two cases that cross sub-steps:
Poor OCR / unreadable references (PDFs with poor text extraction, scanned documents, unusual formatting):
@misc entries with note = {MANUAL CHECK NEEDED: ...}.Incomplete references (missing key fields like year or journal):
note = {metadata enriched from web search}.note = {INCOMPLETE: missing [field]}.Follow the filing sequence from shared/reference-resolution.md. For references marked NEW in Phase 2.3:
Present a summary table before staging:
| # | Key | Title | Authors | Year | Status |
|---|---|---|---|---|---|
| 1 | Smith2020-xy | Title... | Smith, J. | 2020 | NEW — staging for import |
| 2 | Doe2019-ab | Title... | Doe, J. | 2019 | ALREADY IN PAPERPILE (skipped) |
Stage under .paperpile-import/ — write each new entry's BibTeX into a .bib under .paperpile-import/ (Paperpile CLI is read-only; write-bib --citekeys only exports entries already in the library). Mark any draft cite \CiteTodo{...} until imported.
Remind user — "Import the staged .bib under .paperpile-import/ into Paperpile to complete the sync."
Graceful degradation: if the paperpile CLI is unavailable, skip this sub-step. The .bib file from Phase 3.3 is still the primary output.
Run the configured bibliography validator when installed. Otherwise perform these checks directly:
Surface the validation report inline in the final summary (see Report section below). Do not proceed to 4.3 when citation keys are unresolved, required fields are missing, or metadata cannot be verified—fix and re-validate first.
Before any auto-commit, emit an outputs manifest and run the shared verifier per _shared/verify-outputs.md:
Write manifest to <project>/.claude/state/outputs-manifest-<UTC-timestamp>.json listing every file this skill claims to have written, paths relative to the project root.
Run:
uv run python "<skills-root>/_shared/verify_outputs.py" \
--manifest "$MANIFEST" \
--project-root "$PROJECT_ROOT"If the verifier exits non-zero, do not commit. Surface the missing-files list and stop. The verifier logs an error entry to ~/.local/state/ai-workflows/skill-outcomes.jsonl.
Closes the "hallucinated outputs" failure class (commit b2cff75, 2026-04-18).
After completion, provide a summary:
## bib-parse Summary
**Input:** [filename.pdf]
**Output:** [output.bib]
| Metric | Count |
|--------|-------|
| References found in PDF | X |
| Successfully parsed | Y |
| DOIs found/verified | Z |
| Already in Paperpile | A |
| Staged for Paperpile import | B |
| Flagged for manual review | W |
### Bibliography validation report
[paste the configured validator's verdict, or the direct checks performed, plus any critical issues]
### Entries needing attention
- `key1` — missing journal name
- `key2` — year mismatch between PDF (2019) and DOI lookup (2020).bib file when available in Phase 4.2bib-coverage — compare project .bib vs Paperpile project/topic folder — find uncited papers and unfiled referencessplit-pdf — reads the input PDF (called in Phase 1.1)shared/reference-resolution.md — canonical lookup + filing sequence used by Phase 2.3 and Phase 4.1<!-- paperpile-citation-contract -->
\cite{key}, verify with paperpile get-item key and paperpile export-bib key.refpile semantic search → Paperpile verify.\CiteTodo{slug}{title/author/year/DOI hint} — never a guessed key..bib; only the orchestrator regenerates it from Paperpile exports..paperpile-import/ for manual Paperpile import; don't cite until Paperpile mints the key.scripts/bib/citation_lint.py before commit; zero placeholders, zero non-Paperpile keys, zero hand-authored metadata.See rules/paperpile-citations.md for the full workflow.
© flonat, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/bib-parse of flonat/flonat-research.
Open the folder on GitHubat commit da27600
Bib Parse next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bib Parse this skillflonat/flonat-research | 145 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Paper Reading ZhMrGeDiao/paper-reading-zh | 103 | — | ~1.3k | Automated safety check: Pass | MIT | |
| 01 Paper Reviewagentscope-ai/OpenJudge | 868 | 1 repos | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Colt Camera Readybrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Check Review Alignmentmajiayu000/claude-skill-registry | 666 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Paper Auditbahayonghang/academic-writing-skills | 497 | — | ~5.1k | Automated safety check: Pass | None |
MrGeDiao/paper-reading-zh
中文论文深读、总结/TL;DR、工程拆解、按论文实现/复现、比较与证据审计。用户给出论文 PDF、链接、标题、摘要、正文或图表,或明确要读论文时使用。只有论文锚点且无附言时澄清阅读目标;只有阅读意图时问哪篇。已有论文时,“看看这篇”直接深读。不用于仅翻译、解释单个术语、生成 BibTeX、找或下载论文。
agentscope-ai/OpenJudge
Review academic papers for correctness, quality, and novelty using OpenJudge's multi-stage pipeline.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when converting an accepted COLT (Conference on Learning Theory) paper into its PMLR proceedings version, covering de-anonymization, acknowledgements and funding restoration…
majiayu000/claude-skill-registry
当用户明确要求"核查/优化综述 {主题}review.tex 的正文引用"或"运行 check-review-alignment"时使用。通过宿主 AI 的语义理解逐条核查引用是否与文献内容吻合,只在发现致命性引用错误时对"包含引用的句子"做最小化改写,并复用 systematic-literature-review 的渲染脚本输出…
bahayonghang/academic-writing-skills
Reviewer-style audit and submission gate for academic papers in .tex, .typ, or .pdf.
Lucaswangzcx/literature-downloader-skill
中文文献检索、筛选、批量采集和合法全文获取助手。用于用户需要查找论文、下载可合法获取的 PDF/HTML/XML 全文、生成关键词和检索式、查询 DOI/PMID、筛选高影响因子或高分区期刊、检查开放获取、做引用链扩展、批量文献候选表、下载日志、去重清单、Zotero/BibTeX 整理,或解决文献难下载问题;禁止绕过付费墙、盗版下载、共享账号或规避版权限制。
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
Works with
Categories
Extract citations from a PDF and generate a validated .bib file. Bib Parse is an agent skill from flonat/flonat-research.bib file.
Bib Parse fits situations like: the user asks to extract citations from a PDF and generate a validated .bib file; tasks that involve Citation management; tasks that involve PDF.
Run `npx skills add flonat/flonat-research --skill bib-parse -a claude-code`. Or copy the skill folder (skills/bib-parse in flonat/flonat-research) into .claude/skills/bib-parse in your project. Claude Code loads it when a task matches its description.
Run `npx skills add flonat/flonat-research --skill bib-parse -a codex`. Or copy the skill folder (skills/bib-parse in flonat/flonat-research) into .agents/skills/bib-parse in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill bib-parse -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bib-parse, .gemini/skills/bib-parse, .github/skills/bib-parse and .opencode/skills/bib-parse in your project.
Going by SKILL.md and its folder, Bib Parse needs the command-line tools its instructions call (uv). Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Bash(mkdir*), Bash(ls*), Bash(uv*), WebFetch, WebSearch, Skill(split-pdf), Bash(paperpile*).
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Bib Parse is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Bib Parse: Paper Reading Zh (MrGeDiao/paper-reading-zh, 103 stars), 01 Paper Review (agentscope-ai/OpenJudge, 868 stars), Colt Camera Ready (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Check Review Alignment (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.
Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.