Agent skill

Pioreactor Experiment Profiles

by Pioreactor in 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…

MITAuto-check passedBackend & APIs

Install Pioreactor Experiment Profiles

skills CLI
$ npx skills add Pioreactor/pioreactor --skill pioreactor-experiment-profiles -a claude-code

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

GitHub CLI
$ gh skill install Pioreactor/pioreactor pioreactor-experiment-profiles --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-experiment-profiles .claude/skills/pioreactor-experiment-profiles && 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/

Facts

Skill name
pioreactor-experiment-profiles
GitHub stars
149
Token cost
~1k tokens
SKILL.md length
34 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Backend & APIs work in your project
  • SKILL.md covers Goal and Experiment Profile Spec
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pioreactor Experiment Profiles is an agent skill from 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 wait-until blocks.

Its SKILL.md is about 1k 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 Backend & APIs. 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

  • Backend & APIs work in your project

Example prompts

  • “/pioreactor-experiment-profiles”

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

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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 Experiment Profiles loads about 1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 34 words of instructions outside code blocks.

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

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). 34 words, ~1,036 tokens.

Download SKILL.mdSave it as .claude/skills/pioreactor-experiment-profiles/SKILL.md (or your agent's skills folder).
name
pioreactor-experiment-profiles
description
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 wait-until blocks.

Pioreactor Experiment Profiles

Goal

Help Codex produce valid Pioreactor experiment profile YAML that matches the runtime schema and uses the supported action and expression syntax.

Experiment Profile Spec

# Main structure of the experiment profile
version: "1.0"  # Required and quoted; unquoted 1.0 is a YAML number and is rejected

experiment_profile_name: <string>  # Name of the experiment profile


# Metadata (optional)
metadata:
  author: <string>
  description: <string>

# Plugins (optional)
plugins:
  - name: <string>
    version: <string>  # version or constraint, e.g. "1.2.3" or ">=1.2.3"

# Inputs available to expressions (optional)
inputs:
  <input_name>: <value>


# Jobs common to all Pioreactors (optional)
common:
  jobs:
    <job_name>:
      description: <string>
      actions:
        - # see Action definitions below

# Jobs per Pioreactor (optional)
pioreactors:
  <pioreactor_unit_name>:
    label: <string>
    jobs:
      <job_name>:
        description: <string>
        actions:
          - # see Action definitions below


# Action definitions
# - type: log
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#   options:
#     message: <string>
#     level: DEBUG|debug|WARNING|warning|INFO|info|NOTICE|notice|ERROR|error (default: notice)
#
# - type: start
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#   options: {<option_name>: <value>}  # expressions allowed via ${{ }}
#   args: [<string>, ...]
#   config_overrides: {<config_name>: <value>}  # expressions allowed via ${{ }}
#
# - type: update
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#   options: {<option_name>: <value>}  # expressions allowed via ${{ }}
#
# - type: pause
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#
# - type: resume
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#
# - type: stop
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#
# - type: repeat
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#   every: <time_string_or_float>
#   while: <bool_or_expression>  # optional stop condition
#   max_time: <time_string_or_float>      # optional cap on total time loops run for
#   actions:
#     - # basic action only (log, start, pause, resume, stop, update)
#
# - type: when
#   t: <time_string_or_float>
#   if: <bool_or_expression>
#   wait_until: <bool_or_expression>
#   actions:
#     - # any action (including repeat/when)
#
#
# Profile expression syntax (used in ${{ ... }} in options/conditions)
#
# Literals
# - Numbers: integer or float (e.g., 1, -2.5)
# - Booleans: true, false (case-insensitive)
# - Names resolve to values provided in the expression environment (inputs, etc.); otherwise they remain strings.
#
# Operators
# - Arithmetic: +, -, *, / (raises on division by zero), ** (exponent)
# - Comparisons: <, <=, ==, >=, >
# - Logical: and, or, not
# - Parentheses for precedence
#
# Functions
# - random(): float in [0,1)
# - unit(): current unit name
# - hours_elapsed(): current action time
# - experiment(): current experiment name
# - job_name(): current job name
#
# MQTT lookups
# - <unit>:<job>:<setting>[.<nested_key>]*
# - ::<job>:<setting>[.<nested_key>]* (uses current unit)
#   Examples: unit():od_reading:od600, ::stirring:setting.target_rpm
#   Fails if worker is inactive or topic missing.
#
# Conversion rules
# - Numeric strings become floats; "true"/"false" become booleans; otherwise strings stay strings.

# Time strings
# Accepted formats are either a number (float/int) meaning hours, or a string that is a number immediately followed by a unit:
#    s, m, h, or d (case-insensitive). Examples: 0.5 (30min), "30s", "2m", "1.5h", "2d". Whitespace or extra text is rejected, and
#    negative values are disallowed
#
Examples

See more examples at https://github.com/Pioreactor/experiment_profile_examples

© Pioreactor, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

Open the folder on GitHubat commit 0ae14c0

Compare with similar skills

Pioreactor Experiment Profiles 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 Experiment Profiles compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pioreactor Experiment Profiles this skillPioreactor/pioreactor149—~1kAutomated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Nestjs Best Practicesrolling-scopes/rsschool-app10k6 repos~1.2kAutomated safety check: PassMIT
Sub2API AdminWei-Shaw/sub2api43k1 repos~717Automated safety check: PassLGPL-3.0
Firecrawl Build Onboardingfirecrawl/firecrawl190k1 repos~1.4kAutomated safety check: NotesISC
Obsidian BasesAtmosphere/atmosphere3.8k22 repos~3.2kAutomated safety check: PassApache-2.0

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed
  • Nestjs Best Practices

    rolling-scopes/rsschool-app

    NestJS best practices and architecture patterns for building production-ready applications.

    10k GitHub starsUsed in 6 repos~1.2k tokens
    Backend & APIsAuto-check passed
  • Sub2API Admin

    Wei-Shaw/sub2api

    Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.

    43k GitHub starsUsed in 1 repo~717 tokens
    Backend & APIsAuto-check passed
  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check: notes
  • Obsidian Bases

    Atmosphere/atmosphere

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.

    3.8k GitHub starsUsed in 22 repos~3.2k tokens
    Backend & APIsAuto-check passed
  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-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 yesterday
    Auto-check passed
  • Pioreactor CLI

    Pioreactor/pioreactor

    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…

    149 GitHub stars~1.2k tokensUpdated yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Categories

Questions about Pioreactor Experiment Profiles

What does Pioreactor Experiment Profiles do?

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…. Pioreactor Experiment Profiles is an agent skill from 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 wait-until blocks.

When should I use Pioreactor Experiment Profiles?

Pioreactor Experiment Profiles fits situations like: backend & APIs work in your project.

How do I install Pioreactor Experiment Profiles in Claude Code?

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

How do I install Pioreactor Experiment Profiles in Codex?

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

Can I use Pioreactor Experiment Profiles 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-experiment-profiles -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-experiment-profiles, .gemini/skills/pioreactor-experiment-profiles, .github/skills/pioreactor-experiment-profiles and .opencode/skills/pioreactor-experiment-profiles in your project.

What does Pioreactor Experiment Profiles need to run?

SKILL.md names no scripts, command-line tools or credentials: Pioreactor Experiment Profiles is instructions for the agent only.

Does Pioreactor Experiment Profiles access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Pioreactor Experiment Profiles 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 Experiment Profiles use?

Pioreactor Experiment Profiles 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 Experiment Profiles use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Experiment Profiles?

Skills that share tags, products or a category with Pioreactor Experiment Profiles: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 43k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pioreactor Experiment Profiles?

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