Osd Agents
Use for anything about the workbench's own sessions, Screens, terminals and settings — opening a Screen, splitting it into several sessions or terminals, closing one; reading another conversation or the Claude Code / Codex in a terminal and messaging it; or acting on an "[OSD session]", "[OSD terminal]" or "[OSD screen]" reference the user pasted; or a setting the task needs changed (terminals, remote access, approval mode, proxy). All of it goes through the `osd` command.
Install
npx skills add ai4s-research/open-science --skill osd-agentsgit clone --depth 1 https://github.com/ai4s-research/open-science.git /tmp/open-science
mkdir -p ~/.claude/skills
cp -r /tmp/open-science/runtime/skills/core/osd-agents ~/.claude/skills/osd-agentsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# The workbench: sessions, Screens, terminals `osd` is on your PATH and already connected to this workbench. Three things are reachable through it: - **Sessions**: conversations, each with its own folder. - **Screens**: the tabs at the top of the app. Each one is split into panes, and each pane shows a session or a terminal. - **Terminals**: shells, some running Claude Code or Codex. `osd screen ls` shows all of it at once, with the ids every other command takes. `osd session find <words>` finds a conversation by what was said in it. ## Screens ``` osd screen new --sessions 6 --name "Six" # a new Screen, split evenly among 6 new conversations osd screen new ses_a ses_b --terminals 1 # existing conversations and a terminal, side by side osd screen new --terminals 3 --run claude # three terminals, each starting Claude Code osd screen add g12 --new # one more pane: a new conversation (or a SESSION_ID, or --terminal) osd screen add --here --new # a new conversation right of you, on the Screen you are on osd screen show g12 # bring it up in the user's window osd screen close g12 # close it; the conversations are kept ``` New conversations and terminals start in your folder unless you pass `--directory DIR` or `--project NAME`. A new Screen appears in the user's tab bar right away, and the user stays on the Screen they were looking at.
Details
- Skill name
osd-agents- Repository
- ai4s-research/open-science
- Path
runtime/skills/core/osd-agents/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Osd Agents skill do?
Use for anything about the workbench's own sessions, Screens, terminals and settings — opening a Screen, splitting it into several sessions or terminals, closing one; reading another conversation or the Claude Code / Codex in a terminal and messaging it; or acting on an "[OSD session]", "[OSD terminal]" or "[OSD screen]" reference the user pasted; or a setting the task needs changed (terminals, remote access, approval mode, proxy). All of it goes through the `osd` command.
How do I install the Osd Agents skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ai4s-research/open-science --skill osd-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Osd Agents popular?
It lives in ai4s-research/open-science, which has 2,105 GitHub stars and 231 forks.
Related skills
Computer Use
2.1kai4s-research/open-science
Use when a task needs an app on the user's own screen — a native desktop application (instrument control software, Origin, GraphPad, ImageJ, a reference manager, a spreadsheet), or a desktop browser window that needs window-level control. Read before the first `computer` call. Covers the observe-act-observe loop, why element indexes go stale, which action to prefer for which control, what "unverified" means and why it must never be reported as success, and the recovery for each error code. Not for page-level web automation (use the browser connector) and not for anything that can be done from
Domain Check
2.1kai4s-research/open-science
Use ONLY when the user asks to check, validate, review or audit analysis code for scientific correctness, or when you are the reviewer agent running its checks. Never run it unprompted as part of ordinary analysis work. Covers physics, earth/geo, biology, chemistry, social science and bioprocess/fermentation. Runs a deterministic domain-correctness gate that catches code which runs but is scientifically wrong (unit/dimension mismatch, Euclidean distance on lat/lon without a CRS, 0-based/1-based coordinate and strand errors, impossible SMILES valence, uncorrected multiple comparisons, averaging
Large File
2.1kai4s-research/open-science
Use BEFORE reading any data file that could be large (CSV/TSV, Parquet, HDF5, FITS, NetCDF, NDJSON, genomics FASTQ/FASTA/VCF/BAM, GRIB, ROOT, or big text/simulation logs like VASP OUTCAR). Returns a compact memory pointer — header/schema/shape/sample/key numbers — by introspection and sampling in bounded memory, so you never load a file bigger than the context window into the model. Reference data via the pointer; read specific ranges deterministically.
Comet Build
3.3krpamis/comet
Comet Phase 3: Plan and Build. Invoke with /comet-build. Create plans and select execution method (subagent or direct) for implementation.
Skill Digester
2.2klessweb/deepcode-cli
Reviews and improves another DeepCode skill's SKILL.md description field, and guides Agent Skill installation into user or project .agents/skills roots. Use when the user asks to digest a skill, install an Agent Skill, install a skill to user/project scope, or says "消化技能" or "安装 agent skill".
Agents Md
1.2kgetsentry/skills
Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.