claude-scholar

<div align="center"> <img src="LOGO.png" alt="Claude Scholar Logo" width="100%"/> <p> <a href="https://github.com/Galaxy-Dawn/claude-scholar/stargazers"><img src="https://img.shields.io/github/stars/Galaxy-Dawn/claude-scholar?style=flat-square&color=yellow" alt="Stars"/></a> <a href="https://gitcode.com/Dawngammad/claude-scholar"><img src="https://gitcode.com/Dawngammad/claude-scholar/star/badge.svg" alt="GitCode Stars"/></a> <a href="https://github.com/Galaxy-Dawn/claude-scholar/network/members"><img src="https://img.shields.io/github/forks/Galaxy-Dawn/claude-scholar?style=flat-square" alt="Forks"/></a> <img src="https://img.shields.io/github/last-commit/Galaxy-Dawn/claude-scholar/main?style=flat-square" alt="Last Commit"/> <img src="https://img.shields.io/badge/License-MIT-green?style=flat-square" alt="License"/> </p> <p> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/kimi-open-source-friends-dark.svg"> <img alt="Kimi Open Source Friends" src="assets/kimi-open-source-friends-light.svg"> </picture> </p> <p> _{Official Kimi links: <a href="https://www.kimi.com/code?aff=claude-scholar">Kimi Code</a> · <a href="https://platform.kimi.com?aff=claude-scholar">Platform CN</a> · <a href="https://platform.kimi.ai?aff=claude-scholar">Platform Global</a>} </p>

<strong>Language</strong>: <a href="README.md">English</a> | <a href="README.zh-CN.md">中文</a> | <a href="README.ja-JP.md">日本語</a>

<p><strong>Supported Platforms</strong>: <a href="https://github.com/Galaxy-Dawn/claude-scholar/tree/main">Claude Code</a> | <a href="https://github.com/Galaxy-Dawn/claude-scholar/tree/codex">Codex CLI</a> | <a href="https://github.com/Galaxy-Dawn/claude-scholar/tree/kimi">Kimi Code CLI</a> | <a href="https://github.com/Galaxy-Dawn/claude-scholar/tree/opencode">OpenCode</a></p> </div>

Semi-automated research assistant for academic research and software development, especially for computer science and AI researchers. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across literature review, coding, experiments, reporting, writing, and project knowledge management.

<p><em>Branch note</em>: the <code>main</code> branch is the Claude Code workflow. If you use Codex CLI, please see the <a href="https://github.com/Galaxy-Dawn/claude-scholar/tree/codex"><code>codex</code> branch</a>. If you use Kimi Code CLI, please see the <a href="https://github.com/Galaxy-Dawn/claude-scholar/tree/kimi"><code>kimi</code> branch</a>. If you use OpenCode, please see the <a href="https://github.com/Galaxy-Dawn/claude-scholar/tree/opencode"><code>opencode</code> branch</a>.</p>

Recent News

• 2026-06-03: Kimi Code CLI branch added with strong support from Kimi — added the kimi branch as the Kimi Code CLI edition of Claude Scholar and thank the Kimi team for their strong support of this project.
• 2026-05-14: expression-skill made the communication core, planning-with-files restored as the default persistence layer, and the Nature writing stack expanded — made expression-skill the explicit conclusion-first discipline for reporting, planning, file operations, and multi-step technical work; reintroduced planning-with-files as the default on-disk planning and progress-tracking workflow for complex tasks; introduced nature-writing for section drafting and argument construction; refreshed nature-polishing to the latest upstream article-pattern release; and kept nature-response plus nature-data in the journal-writing stack.
• 2026-05-13: Evidence-gated research workflow and Sources/Papers routing tightened — added a shared research-contract.md for Evidence Records, claim strength, and Claim Promotion Gates; connected research ideation, Zotero ingestion, literature synthesis, results reporting, writing, and rebuttal workflows to that contract; and clarified that project paper notes live under Sources/Papers before promoted claims move into Knowledge or Writing.
• 2026-04-24: Project-scoped Obsidian KB workflow consolidated — rebuilt Obsidian project knowledge management into a vault-first workflow, consolidated the older overlapping memory skills into four focused skills, kept repo-local project binding metadata as a runtime layer, and made project navigation human-first instead of a machine registry dump.
• 2026-04-22: Lean core, pruned default agents, safer install lifecycle, and cleaner paper discovery — replaced large always-on CLAUDE.md / AGENTS.md files with compact core instructions, pruned the default agent set to the retained core agents, added safe install-state based uninstall support, generalized daily-paper-generator to broader topics with arXiv / bioRxiv support and a fixed Top 10 -> Top 3 -> Top 1 selection flow.
• 2026-04-15: pubfig and pubtab introduced — introduced pubfig, a Python package for publication-grade scientific figures, and pubtab, a Python package for publication-ready tables and Excel↔LaTeX workflows. Together they provide a cleaner production stack for paper figures, benchmark tables, export control, and final artifact QA.

<details> <summary>View older changelog</summary>

• 2026-04-15: publication-chart-skill integrated into Claude Scholar — wrapped pubfig + pubtab into publication-chart-skill, added the skill to the repository, and connected it to Claude Scholar's analysis and writing boundaries so publication-grade figure/table work now has an explicit handoff route instead of being mixed into general analysis or prose skills.

• 2026-03-31: Zotero smart-import workflow docs aligned — updated Claude Scholar's research-facing docs around the latest zotero-mcp public surface: zotero_add_items_by_identifier is now the default paper-import path, zotero_reconcile_collection_duplicates is the standard post-import cleanup step, source-aware PDF cascade behavior is documented more accurately, and public vs internal diagnostics are now clearly separated.

• 2026-03-31: README onboarding refreshed — clarified that Claude Scholar is especially well-suited to computer science and AI researchers, added practical getting-started scenarios after installation, improved prerequisite and branch guidance, and made the “existing local md files must be manually merged” expectation much more explicit.

• 2026-03-31: Installer and hook behavior tightened — the installer now preserves existing local CLAUDE.md while installing the repo-managed version as CLAUDE.scholar.md, and the default hook summaries were trimmed to reduce noisy temp-file / uncommitted-file output while keeping safer write-guard behavior.

• 2026-03-31: Japanese documentation added — added Japanese docs for the main README plus AGENTS, MCP_SETUP, and OBSIDIAN_SETUP, so the OpenCode branch now has a more complete multilingual documentation surface.

• 2026-02-25: Codex CLI support — added codex branch supporting OpenAI Codex CLI with config.toml, 40 skills, 14 agents, and sandbox security

• 2026-02-23: Added setup.sh installer — backup-aware incremental updates for existing ~/.opencode, auto-backup opencode.jsonc, additive agent/mcp/permission/plugin merge

• 2026-02-21: OpenCode support — Claude Scholar now supports OpenCode as an alternative CLI; switch to the opencode branch for OpenCode-compatible configuration

• 2026-02-20: Bilingual docs — maintained English and Chinese entry documents for broader readability

• 2026-02-15: Zotero MCP integration — added /zotero-review and /zotero-notes commands, updated research-ideation skill with Zotero integration guide, enhanced literature-reviewer agent with Zotero MCP support for automated paper import, collection management, full-text reading, and citation export

• 2026-02-14: Hooks optimization — restructured security-guard to two-tier system (Block + Confirm), skill-forced-eval now groups skills into 6 categories with silent scan mode, session-start limits display to top 5, session-summary adds 30-day log auto-cleanup, stop-summary shows separate added/modified/deleted counts; removed deprecated shell scripts (lib/common.sh, lib/platform.sh)

• 2026-02-11: Major update — added 10 new skills (research-ideation, results-analysis, citation-verification, review-response, paper-self-review, post-acceptance, daily-coding, frontend-design, ui-ux-pro-max, web-design-reviewer), 7 new agents, 8 research workflow commands, 2 new rules (security, experiment-reproducibility); restructured the main configuration docs; 89 files changed

• 2026-01-26: Rewrote all Hooks to cross-platform Node.js; completely rewrote README; expanded ML paper writing knowledge base; merged PR #1 (cross-platform support)

• 2026-01-25: Project open-sourced, v1.0.0 released with 25 skills (architecture-design, bug-detective, git-workflow, kaggle-learner, scientific-writing, etc.), 2 agents (paper-miner, kaggle-miner), 30+ commands (including SuperClaude suite), 5 Shell Hooks, and 2 rules (coding-style, agents)

</details>

Quick Navigation

| Section | What it helps with | |---|---| | Why Claude Scholar | Understand the project positioning and target use cases. | | Core Workflow | See the end-to-end research pipeline from ideation to publication. | | Quick Start | Install Claude Scholar in full, minimal, or selective mode. | | Getting Started Scenarios | See a few realistic first-use scenarios after installation. | | Integrations | Learn how Zotero and Obsidian fit into the workflow. | | Primary Workflows | Browse the main research and development workflows. | | Supporting Workflows | See the background systems that strengthen the main workflow. | | Documentation | Jump to setup docs, configuration, and templates. | | Citation | Cite Claude Scholar in papers, reports, or project docs. |

Why Claude Scholar

Claude Scholar is not an end-to-end autonomous research system that tries to replace the researcher.

Its core idea is simple:

human decision-making stays at the center; the assistant accelerates the workflow around it.

That means Claude Scholar is designed to help with the heavy, repetitive, and structure-sensitive parts of research — literature organization, note-taking, experiment analysis, reporting, and writing support — while still keeping the key judgments in human hands:

• which problem is worth pursuing,
• which papers actually matter,
• which hypotheses are worth testing,
• which results are convincing,
• and what should be written, submitted, or abandoned.

In other words, Claude Scholar is a semi-automated research assistant, not a “fully automated scientist.”

Who This Is For

Claude Scholar is especially well-suited to:

• computer science researchers who move between literature review, coding, experiments, and paper writing,
• AI / ML researchers who need one assistant workflow spanning ideation, implementation, analysis, reporting, and