Overview
While most people use AI by pasting text into a chat window, you can run an agent that works with your files directly from the folder. With the Open Science Skills added, a short command can verify your reference list against your bibliography, or check whether your sources actually contain the claims you make.
Everything is done in your terminal, which is where you type commands. You will only need the commands listed on this page. It doesn't matter if you're on a laptop or a server at your university, or if you're using Claude Code or Codex. You can also use Claude Code inside VS Code or JetBrains editors, or in the Claude desktop and web apps, but the rest of this site assumes you're using a terminal.
Get an account and open a terminal
To use Claude Code, you need a paid plan (Pro, Max, Team or Enterprise) or an Anthropic Console account. It is not available with the free plan.
Open a terminal window on your computer. If you're using a Mac, you can open the Terminal app by searching for it in Spotlight. If you're using Windows, you can open PowerShell from the Start menu. On Linux, open your terminal as you normally would.
Install Claude Code
To run skills, you'll need Claude Code, the AI agent that runs them. To install it, paste the line for your system into your terminal and hit Enter.
# macOS, Linux, or WSL
curl -fsSL https://claude.ai/install.sh | bash
# Windows (PowerShell)
irm https://claude.ai/install.ps1 | iex
You can verify it installed by running claude --version, which will print the version. If you get an error that the command is not found, try opening a new terminal.
Other ways to install are in the Claude Code setup guide.
Sign in
claude
Type claude and press Enter. The first time, you will be prompted to log in with your Claude account in a browser window. You will not need to log in again after that. To exit Claude Code, type /exit.
Add the Open Science Skills
The checks come from the Open Science Skills, a free plugin for Claude Code. Run both of the commands below in your terminal, not in Claude Code. The first command points Claude Code to the plugin and the second installs it.
claude plugin marketplace add scdenney/open-science-skills
claude plugin install oss@open-science-skills
Once you have done that, start Claude Code again by running claude in your terminal. You can tell that you are set up if you type / and see commands like /oss:citation-check in the list. If Claude Code is already open, run /reload-plugins instead.
Open a project and call a skill
Your project is just a folder on your computer that has all your files in it. You can navigate to it in the terminal with the cd command (cd stands for "change directory"), then start Claude Code there. You can usually do this by typing cd followed by a space and then dragging the folder into the terminal.
cd path/to/your/project
claude
Then run the command for the skill in Claude Code.
/oss:citation-check manuscript.md references.bib
You can also prompt in natural language instead, something like "check the references in manuscript.md against references.bib." Claude Code has access to all files in the folder, so make sure to use the actual names of the files.
Using Codex instead alternative
Codex is OpenAI's version of Claude Code. A Codex version of the Open Science Skills is also available, with 43 of the 44 skills (all but presubmit). Since Codex does not have a plugin marketplace, setting it up is slightly different.
Install Codex and sign in first, following OpenAI's instructions. Then download and install the skills, which requires git and Python 3. The dry-run line previews the install, and the last line actually installs the skills.
git clone https://github.com/scdenney/open-science-skills
cd open-science-skills
python3 plugin/scripts/install-codex.py --all --dry-run
python3 plugin/scripts/install-codex.py --all
In Codex, use $ instead of /oss: to invoke a skill.
$citation-check manuscript.md references.bib
A few skill names and options are different in Codex – see the full list in the Codex README.
Build a knowledge base optional
This is only required if you want the source-claim check, which reads your sources and checks whether they support the claims made in a manuscript. The reference check does not need it.
The research-repo skill creates the folders for you. Your original PDFs go in sources/og/ and markdown versions in sources/md/. The markdown versions are plain-text versions of your PDFs, and the doc-to-markdown skill converts them. See the knowledge-base demo for the full process.
/oss:research-repo . # set up the sources/ folders
/oss:doc-to-markdown paper.pdf # convert one PDF to Markdown
Next: check a draft against its sources →
Step through a recorded run in which an agent builds a small knowledge base from archival sources and checks a draft against it.