Open Science Skills
Agentic skills for Claude Code and Codex, built from published social-science methods sources. Covers experimental design, computational text analysis, manuscript QA, and…
Install
claude plugin install oss@open-science-skillsInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Open Science Skills
Open Science Skills is a library of 42 agentic skills for Claude Code, with a parallel 41-skill library for OpenAI Codex, written for computational social scientists and digital humanists. Each skill is meant to work the way the field expects. Identify the data-generating process before proposing an estimator, and design experiments and instruments to a standard. Drafts are held to established reporting norms.
The library follows the research lifecycle. It covers survey design, list experiments, topic modeling, LLM text classification, VLM-based OCR pipelines, manuscript QA, multi-model orchestration, and transparent reporting under APSA, JARS, DA-RT, TOP, and FAIR expectations. Every skill is grounded in published methods sources and based on best practices for writing skills. See SOURCES.md for the bibliography of 150+ works consulted.
This is the toolkit I use in my own research, and it grows as I add sources and skills. The authoring is mine, with editing help from Opus 5, Fable 5.1, and ChatGPT 5.5/6.
| Platform | Skills | Invoke |
|---|---|---|
| Claude Code | 42, as the oss plugin |
/oss:skill-name |
| OpenAI Codex | 41, as the codex/ library |
$skill-name |
The two libraries differ only in invocation and tooling. The Codex side omits presubmit; its orchestrate is the Codex-native version led by the active GPT-6 Astra or GPT-6.1 Sol session, with mode-aware routing between them. See codex/README.md.
Model selection and reusable migration practices are documented in MODEL-POLICY.md.
Quick start · Skills · Recommended · How skills trigger · Installation · Sources · Contributing · License
Quick start
Install the plugin from the marketplace, user-wide across all projects, or add --scope project for one project only:
# Step 1: Register the marketplace (one-time)
claude plugin marketplace add scdenney/open-science-skills
# Step 2: Install the plugin
claude plugin install oss@open-science-skills
# Project-only install
claude plugin install oss@open-science-skills --scope project
Then invoke a skill by name, for example /oss:conjoint-design. Every skill is on demand, so nothing loads into a session until you ask for it (see Skills).
On Codex there is no plugin. Install the skills library instead (see Codex).
How skills trigger
No skill loads on its own. Name one, with /oss:skill-name in Claude Code or $skill-name in Codex, and it reads into context and runs. Nothing is suggested unprompted, so the library costs an idle session nothing.
The orchestration and delegated-review skills (orchestrate, advisor, model-committee and its chair variants, diverge --codex, and paper-review-lite --codex) start subagents or an external model. Every skill is on demand (see Skills), but for these the rule is load-bearing rather than economical.
Installation
Claude Code
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.