Agent skill

Pioreactor CLI

A skill your agent uses when running, debugging, documenting, or changing Pioreactor command-line workflows with pio or pios, including local job control, logs, MQTT, config, plugins, calibrations…

MITAuto-check passedDevelopment

Install Pioreactor CLI

skills CLI

$ npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Pioreactor/pioreactor pioreactor-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pioreactor-cli .claude/skills/pioreactor-cli && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "pioreactor-cli" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-cli into .claude/skills/pioreactor-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-cli", 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

$skill-installer install https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-cli

Type 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.

skills CLI

$ npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Pioreactor/pioreactor pioreactor-cli --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pioreactor-cli .agents/skills/pioreactor-cli && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pioreactor-cli" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-cli into .agents/skills/pioreactor-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-cli", 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.

skills CLI

$ npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Pioreactor/pioreactor pioreactor-cli --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pioreactor-cli .cursor/skills/pioreactor-cli && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pioreactor-cli" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-cli into .cursor/skills/pioreactor-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-cli", 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

$ gemini skills install https://github.com/Pioreactor/pioreactor.git --path .agents/skills/pioreactor-cli

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Pioreactor/pioreactor pioreactor-cli --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pioreactor-cli .gemini/skills/pioreactor-cli && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "pioreactor-cli" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-cli into .gemini/skills/pioreactor-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-cli", 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.

GitHub CLI

$ gh skill install Pioreactor/pioreactor pioreactor-cli

Installs 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).

skills CLI

$ npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pioreactor-cli .github/skills/pioreactor-cli && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "pioreactor-cli" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-cli into .github/skills/pioreactor-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-cli", 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.

skills CLI

$ npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Pioreactor/pioreactor pioreactor-cli --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pioreactor-cli .opencode/skills/pioreactor-cli && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pioreactor-cli" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-cli into .opencode/skills/pioreactor-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-cli", 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.

Facts

Skill name: pioreactor-cli
GitHub stars: 149
Token cost: ~1.2k tokens
SKILL.md length: 527 words
Files: 1
Skills in repo: 5
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when running, debugging, documenting, or changing Pioreactor command-line workflows with pio or pios, including local job control, logs, MQTT, config, plugins, calibrations…

Works in 4 steps: Confirm the environment root when… → In this repo, prefer .venv/bin/pio and… → For web-backed or Huey-backed commands,… → …
Changing Pioreactor command-line workflows with pio
SKILL.md covers Purpose, First Checks, Choosing pio vs pios and Safe Execution Rules, plus 2 more sections
Calls make

What it does

Pioreactor CLI is an agent skill from Pioreactor/pioreactor. Use when running, debugging, documenting, or changing Pioreactor command-line workflows with pio or pios, including local job control, logs, MQTT, config, plugins, calibrations, worker targeting, config sync, cluster orchestration, and safe production command execution.

Its SKILL.md is about 1.2k 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 Development, covering Performance reviews. The repository describes itself as: Hardware and software for accessible, extensible, and scalable bioreactors. Built on Raspberry Pi. The licence is MIT.

When your agent uses it

Changing Pioreactor command-line workflows with pio
Including local job control
Worker targeting
Cluster orchestration

Example prompts

“/pioreactor-cli”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Confirm the environment root when behavior depends on files, config, plugins, profiles, calibrations, databases, or logs
In this repo, prefer .venv/bin/pio and .venv/bin/pios over bare pio and pios unless the task is explicitly on-device.
For web-backed or Huey-backed commands, run make dev-status before starting services. Start only the services listed as missing.
Byte-cap unknown command output, for example

What it can do on your machine

Read from SKILL.md and the folder at commit 0ae14c0. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pioreactor CLI loads about 1.2k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 527 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~72
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from Pioreactor/pioreactor at commit 0ae14c0, republished under its MIT licence (© Pioreactor). 527 words, ~1,200 tokens.

Download SKILL.mdSave it as .claude/skills/pioreactor-cli/SKILL.md (or your agent's skills folder).

name: pioreactor-cli
description: Use when running, debugging, documenting, or changing Pioreactor command-line workflows with `pio` or `pios`, including local job control, logs, MQTT, config, plugins, calibrations, worker targeting, config sync, cluster orchestration, and safe production command execution.

Pioreactor CLI

Purpose

Use this skill for Pioreactor CLI work involving:

pio: local node commands for a leader, worker, or standalone Pioreactor.
pios: leader-only commands that dispatch work to worker Pioreactors.

Prefer the command's current --help output and the implementation in core/pioreactor/cli/ over remembered syntax.

First Checks

Confirm the environment root when behavior depends on files, config, plugins, profiles, calibrations, databases, or logs:
- DOT_PIOREACTOR
- GLOBAL_CONFIG
- TESTING
- PLUGINS_DEV
- PIO_EXECUTABLE
- PIOS_EXECUTABLE
In this repo, prefer .venv/bin/pio and .venv/bin/pios over bare pio and pios unless the task is explicitly on-device.
For web-backed or Huey-backed commands, run make dev-status before starting services. Start only the services listed as missing.
Byte-cap unknown command output, for example:

bash

.venv/bin/pio jobs running 2>&1 | head -c 4000

Choosing `pio` vs `pios`

Use pio for local unit work: start or stop one job, inspect logs, subscribe to MQTT, edit local config, manage local plugins, run calibrations, inspect jobs, or query the local database.
Use pios from the leader for cluster work: run or kill jobs on multiple workers, update worker settings, sync configs, copy/remove files on workers, install/uninstall plugins, reboot/shutdown workers, or update app versions across units.
Test a job or command locally with pio before scaling it through pios when that is practical.
Remember that pios adds target selectors such as --units and --experiments; avoid relying on the default target set unless the user explicitly asked for all eligible workers.

Safe Execution Rules

Do not run broad production-affecting commands unless the user explicitly asked for that scope. Examples: pios kill --all-jobs -y, pios shutdown, pios reboot, pios update app, pios rm, and cluster-wide plugin changes.
Prefer narrow targeting with --units <unit> or --experiments <experiment> for pios commands.
For destructive or state-changing operations, first show or inspect the resolved target set when the CLI supports it, or use a safer read command such as pio workers status, pio jobs running, or the relevant --help.
For commands that can block, stream indefinitely, or run jobs, use the harness background/session support when needed and make sure the process is stopped before finalizing.
Never paper over failures by disabling tests or weakening command behavior. Diagnose whether the issue is code, environment, service state, or target reachability.

Show full SKILL.md (167 more words)Show less

Common Workflows

Inspect Current CLI Syntax

bash

pio --help
pio <command> --help
pios --help
pios <command> --help

Local Job Work

bash

pio jobs running
pio run <job_name> [job options]
pio update-settings <job_name> [setting options]
pio kill --job-name <job_name>

Check core/pioreactor/background_jobs/base.py and the job implementation when lifecycle, published settings, MQTT topics, or cleanup behavior matter.

Cluster Job Work

bash

pios run <job_name> --units <unit> [job options]
pios update-settings <job_name> --units <unit> [setting options]
pios kill --job-name <job_name> --units <unit>

For worker-targeted failures, distinguish leader dispatch failures from worker-local failures. Inspect the pios implementation, leader API route, Huey task, and worker /unit_api route as appropriate.

Config and Plugin Work

Local config edits or reads usually belong under pio config or direct config-file logic rooted at DOT_PIOREACTOR.
Cluster config propagation belongs under pios sync-configs.
Local plugin inspection belongs under pio plugins.
Cluster plugin installs or removals belong under pios plugins, and should usually be targeted.

Logs and MQTT

bash

pio logs -n 50
pio mqtt -t "pioreactor/<unit>/<experiment>/<job_name>/#"

Use narrow MQTT topics when possible. Stop subscriptions before finalizing.

Validation

For CLI implementation changes, run the smallest relevant pytest target, usually a specific file or test under core/tests/.
For command-syntax or discovery work, smoke check the current command:

bash

pio <command> --help
pios <command> --help

For live cluster behavior, report exactly what was run, which unit or experiment was targeted, and any services or environment variables that mattered.

Files

Just SKILL.md in .agents/skills/pioreactor-cli of Pioreactor/pioreactor.

Open the folder on GitHubat commit 0ae14c0

Compare with similar skills

Pioreactor CLI 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.

Pioreactor CLI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pioreactor CLI this skillPioreactor/pioreactor	149	—	~1.2k	Automated safety check: Pass	MIT	today
Sanity Radar Investigatesanity-io/sanity	6.4k	—	~1.5k	Automated safety check: Pass	MIT	today
Code Review Skillawesome-skills/code-review-skill	2.1k	—	~2.8k	Automated safety check: Notes	MIT	29 days ago
Jev Lint Repomizchi/jev-lint	117	—	~942	Automated safety check: Pass	MIT	5 days ago
Multi Reviewer Patternswshobson/agents	40k	—	~1.3k	Automated safety check: Pass	MIT	2 days ago
Deep Analysisnicepkg/auto-company	192	2 repos	~2.7k	Automated safety check: Notes	None	7 mo ago

Similar skills

Sanity Radar Investigate
sanity-io/sanity
Official
Investigate a suspected Studio performance regression surfaced by Studio Radar or the bench suite — confirm the signal against host calibration, narrow the commit range, confirm with an A/B…
6.4k GitHub stars~1.5k tokensUpdated today
DevelopmentAuto-check passed
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
2.1k GitHub stars~2.8k tokensUpdated 29 days ago
DevelopmentAuto-check: notes
Jev Lint Repo
mizchi/jev-lint
A skill your agent uses when changing jev-lint ITSELF — editing src/, shipped rule suites under rules/<language/<id/, or recorded runs in docs/data/.
117 GitHub stars~942 tokensUpdated 5 days ago
DevelopmentAuto-check passed
Multi Reviewer Patterns
wshobson/agents
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting.
40k GitHub stars~1.3k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Deep Analysis
nicepkg/auto-company
Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews.
192 GitHub starsUsed in 2 repos~2.7k tokens
Business, Finance & HRAuto-check: notes
Sap Sac Planning
secondsky/sap-skills
SAP Analytics Cloud (SAC) planning guidance for planning models, planning-enabled stories, data actions, multi actions, version management, data locking, calendar/input workflows, allocations, value…
460 GitHub stars~10k tokensUpdated 2 days ago
Business, Finance & HRAuto-check passed

More from Pioreactor/pioreactor

Pioreactor Calibration Dev
Pioreactor/pioreactor
Create, update, debug, or review Pioreactor calibration routines and session flows in core/pioreactor/calibrations, including calibration data types, CLI and UI behavior, step registries, protocol…
149 GitHub stars~2.9k tokensUpdated today
Auto-check passed
Pioreactor Plugin Jobs
Pioreactor/pioreactor
Create, update, debug, or review Pioreactor plugin background jobs, including file-based plugin modules, BackgroundJobContrib or LongRunningBackgroundJobContrib classes, pio run command…
149 GitHub stars~799 tokensUpdated today
Auto-check passed
Pioreactor Automations
Pioreactor/pioreactor
Create, update, debug, or review Pioreactor dosing, temperature, and LED automations, including automation families, config sections, UI descriptors, runtime execution strategies, published…
149 GitHub stars~1.3k tokensUpdated today
Auto-check passed
Pioreactor Experiment Profiles
Pioreactor/pioreactor
Write, edit, review, or debug Pioreactor experiment profile YAML, including profile structure, inputs, common jobs, per-Pioreactor jobs, action timing, expressions, MQTT lookups, and repeat or…
149 GitHub stars~1k tokensUpdated today
Auto-check passed

Questions about Pioreactor CLI

What does Pioreactor CLI do?

A skill your agent uses when running, debugging, documenting, or changing Pioreactor command-line workflows with pio or pios, including local job control, logs, MQTT, config, plugins, calibrations…. Pioreactor CLI is an agent skill from Pioreactor/pioreactor. Use when running, debugging, documenting, or changing Pioreactor command-line workflows with pio or pios, including local job control, logs, MQTT, config, plugins, calibrations, worker targeting, config sync, cluster orchestration, and safe production command execution.

When should I use Pioreactor CLI?

Pioreactor CLI fits situations like: changing Pioreactor command-line workflows with pio; including local job control; worker targeting; cluster orchestration.

How do I install Pioreactor CLI in Claude Code?

Run `npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a claude-code`. Or copy the skill folder (.agents/skills/pioreactor-cli in Pioreactor/pioreactor) into .claude/skills/pioreactor-cli in your project. Claude Code loads it when a task matches its description.

How do I install Pioreactor CLI in Codex?

Run `npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a codex`. Or copy the skill folder (.agents/skills/pioreactor-cli in Pioreactor/pioreactor) into .agents/skills/pioreactor-cli in your project. Codex loads it when a task matches its description.

Can I use Pioreactor CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Pioreactor/pioreactor --skill pioreactor-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pioreactor-cli, .gemini/skills/pioreactor-cli, .github/skills/pioreactor-cli and .opencode/skills/pioreactor-cli in your project.

What does Pioreactor CLI need to run?

Going by SKILL.md and its folder, Pioreactor CLI needs the command-line tools its instructions call (make).

Does Pioreactor CLI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pioreactor CLI safe to install?

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.

What licence does Pioreactor CLI use?

Pioreactor CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pioreactor CLI use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pioreactor CLI?

Skills that share tags, products or a category with Pioreactor CLI: Sanity Radar Investigate (sanity-io/sanity, 6.4k stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Jev Lint Repo (mizchi/jev-lint, 117 stars) and Multi Reviewer Patterns (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pioreactor CLI?

Pioreactor (a GitHub organization) maintains it in Pioreactor/pioreactor, which has 149 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.

Source: Pioreactor/pioreactor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Pioreactor CLI

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Pioreactor CLI

Purpose

First Checks

Choosing pio vs pios

Safe Execution Rules

Common Workflows

Inspect Current CLI Syntax

Local Job Work

Cluster Job Work

Config and Plugin Work

Logs and MQTT

Validation

Files

Compare with similar skills

Similar skills

More from Pioreactor/pioreactor

Related

Questions about Pioreactor CLI

Choosing `pio` vs `pios`