Trigger.dev Configuration
papermark/papermark
Configures Trigger.dev projects through trigger.config.ts, with build extensions for Prisma, Playwright, Puppeteer, FFmpeg, Python and system packages.
Create, update, debug, or review Pioreactor plugin background jobs, including file-based plugin modules, BackgroundJobContrib or LongRunningBackgroundJobContrib classes, pio run command…
Install Pioreactor Plugin Jobs
$ npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Pioreactor/pioreactor pioreactor-plugin-jobs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pioreactor-plugin-jobs .claude/skills/pioreactor-plugin-jobs && rm -rf skills-srcUse ~/.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/
Install the "pioreactor-plugin-jobs" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-plugin-jobs into .claude/skills/pioreactor-plugin-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-plugin-jobs", 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 install https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-plugin-jobsType 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.
$ npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Pioreactor/pioreactor pioreactor-plugin-jobs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pioreactor-plugin-jobs .agents/skills/pioreactor-plugin-jobs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pioreactor-plugin-jobs" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-plugin-jobs into .agents/skills/pioreactor-plugin-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-plugin-jobs", 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.
$ npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Pioreactor/pioreactor pioreactor-plugin-jobs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pioreactor-plugin-jobs .cursor/skills/pioreactor-plugin-jobs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pioreactor-plugin-jobs" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-plugin-jobs into .cursor/skills/pioreactor-plugin-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-plugin-jobs", 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 https://github.com/Pioreactor/pioreactor.git --path .agents/skills/pioreactor-plugin-jobs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Pioreactor/pioreactor pioreactor-plugin-jobs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pioreactor-plugin-jobs .gemini/skills/pioreactor-plugin-jobs && rm -rf skills-srcUse ~/.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/
Install the "pioreactor-plugin-jobs" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-plugin-jobs into .gemini/skills/pioreactor-plugin-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-plugin-jobs", 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.
$ gh skill install Pioreactor/pioreactor pioreactor-plugin-jobsInstalls 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).
$ npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pioreactor-plugin-jobs .github/skills/pioreactor-plugin-jobs && rm -rf skills-srcUse ~/.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/
Install the "pioreactor-plugin-jobs" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-plugin-jobs into .github/skills/pioreactor-plugin-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-plugin-jobs", 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.
$ npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Pioreactor/pioreactor pioreactor-plugin-jobs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Pioreactor/pioreactor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pioreactor-plugin-jobs .opencode/skills/pioreactor-plugin-jobs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pioreactor-plugin-jobs" agent skill from https://github.com/Pioreactor/pioreactor/tree/master/.agents/skills/pioreactor-plugin-jobs into .opencode/skills/pioreactor-plugin-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pioreactor-plugin-jobs", 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-plugin-jobs- GitHub stars
- 149
- Token cost
- ~799 tokens
- SKILL.md length
- 336 words
- Files
- 5 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create, update, debug, or review Pioreactor plugin background jobs, including file-based plugin modules, BackgroundJobContrib or LongRunningBackgroundJobContrib classes, pio run command…
- Works in 8 steps: First decide whether the request is a… → Inspect the current repo before editing:… → Identify the development environment… → …
- Custom jobs that should run from pio
- SKILL.md covers Overview, Workflow, References and Rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pioreactor Plugin Jobs is an agent skill from Pioreactor/pioreactor. Create, update, debug, or review Pioreactor plugin background jobs, including file-based plugin modules, BackgroundJobContrib or LongRunningBackgroundJobContrib classes, pio run command registration, published settings, MQTT listeners, cleanup hooks, OD-dodging jobs, local discovery through PLUGINSDEV, and UI job descriptors under plugins/ui/jobs. Use for custom jobs that should run from pio or appear in the Pioreactor UI. For dosing, LED, or temperature automations, use the pioreactor-automations skill instead.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/development-environments.md`, `references/plugin-job-patterns.md` and `references/ui-job-descriptors.md`).
It sits in Backend & APIs, covering Background jobs. 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
- Custom jobs that should run from pio
- Appear in the Pioreactor UI
Example prompts
- “/pioreactor-plugin-jobs”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- First decide whether the request is a background job or an automation. If it is a dosing, LED, or temperature automation, use…
- Inspect the current repo before editing: core/pioreactor/background_jobs/base.py, core/pioreactor/cli/run.py, the target plugin file if…
- Identify the development environment before choosing tests: repo-local development has pytest and no real hardware; on-device development…
- Confirm the environment root when it matters: local dev uses TESTING=1 plus PLUGINS_DEV; devices use /home/pioreactor/.pioreactor/plugins…
- Implement the job using the narrowest contrib base class
- Register a Click function named click_ so pio run can discover it.
- If the job should appear in the UI, add a YAML descriptor under $DOT_PIOREACTOR/plugins/ui/jobs/.
- Validate discovery first, then runtime behavior.
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
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 Plugin Jobs loads about 799 tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 135 tokens; SKILL.md has 336 words of instructions outside code blocks.
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). 336 words, ~799 tokens.
Download SKILL.mdSave it as
.claude/skills/pioreactor-plugin-jobs/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- pioreactor-plugin-jobs
- description
- Create, update, debug, or review Pioreactor plugin background jobs, including file-based plugin modules, BackgroundJobContrib or LongRunningBackgroundJobContrib classes, pio run command registration, published settings, MQTT listeners, cleanup hooks, OD-dodging jobs, local discovery through PLUGINS_DEV, and UI job descriptors under plugins/ui/jobs. Use for custom jobs that should run from pio or appear in the Pioreactor UI. For dosing, LED, or temperature automations, use the pioreactor-automations skill instead.
Pioreactor Plugin Jobs
Overview
Build custom Pioreactor background jobs as plugin modules that can be discovered by pio plugins list, launched with pio run <job_name>, and optionally displayed in the Pioreactor UI.
Workflow
- First decide whether the request is a background job or an automation. If it is a dosing, LED, or temperature automation, use
$pioreactor-automations. - Inspect the current repo before editing:
core/pioreactor/background_jobs/base.py,core/pioreactor/cli/run.py, the target plugin file if one exists, and similar examples inplugins_dev/. - Identify the development environment before choosing tests: repo-local development has pytest and no real hardware; on-device development has hardware and usually no repo test harness.
- Confirm the environment root when it matters: local dev uses
TESTING=1plusPLUGINS_DEV; devices use/home/pioreactor/.pioreactor/plugins; UI descriptors are rooted underDOT_PIOREACTOR. - Implement the job using the narrowest contrib base class:
- Use
BackgroundJobContribfor normal experiment-scoped plugin jobs. - Use
LongRunningBackgroundJobContribfor jobs that run across experiments, usually withUNIVERSAL_EXPERIMENT. - Use
BackgroundJobWithDodgingContribonly when the job must change behavior around OD readings.
- Use
- Register a Click function named
click_<job_name>sopio run <job_name>can discover it. - If the job should appear in the UI, add a YAML descriptor under
$DOT_PIOREACTOR/plugins/ui/jobs/. - Validate discovery first, then runtime behavior.
References
- Read
references/plugin-job-patterns.mdbefore creating or changing plugin job Python. - Read
references/development-environments.mdbefore choosing where to create files or what validation to run. - Read
references/ui-job-descriptors.mdbefore adding a job to the Pioreactor UI. - Read
references/validation.mdbefore reporting the work complete.
Rules
- Keep module-level work cheap and safe; plugin modules are imported during discovery.
- Avoid filenames that shadow standard library modules because the plugin directory is injected into
sys.path. - Keep
job_name, Click command name, MQTT topics, config section names, and UI descriptor names aligned. - Use
published_settingsfor runtime-observable settings andset_<setting>methods when a settable value needs validation or side effects. - Put cleanup in
on_disconnected; cancel timers, close hardware handles, and leave hardware in a safe state. - Prefer small targeted tests and smoke checks. Do not run the whole pytest suite for job work.
© 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
SKILL.md and 4 other files (references) in .agents/skills/pioreactor-plugin-jobs of Pioreactor/pioreactor.
- SKILL.md
- references/development-environments.md
- references/plugin-job-patterns.md
- references/ui-job-descriptors.md
- references/validation.md
Open the folder on GitHubat commit 0ae14c0
Compare with similar skills
Pioreactor Plugin Jobs 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pioreactor Plugin Jobs this skillPioreactor/pioreactor | 149 | — | ~799 | Automated safety check: Pass | MIT | |
| Trigger.dev Configurationpapermark/papermark | 9.2k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Laravel SpecialistJeffallan/claude-skills | 12k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Trigger.dev Realtimepapermark/papermark | 9.2k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| NubaseOtterMind/Nubase | 623 | — | ~2.2k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Foundatio
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
Laravel Specialist
Jeffallan/claude-skills
Builds Laravel 10+ applications with Eloquent models, Sanctum authentication, Horizon queues, API resources and Livewire components, tested with Pest or PHPUnit.
Trigger.dev Realtime
papermark/papermark
Shows how to subscribe to Trigger.dev task runs from the backend and from React for progress indicators, live dashboards, AI response streams and approval waits.
Nubase
OtterMind/Nubase
A skill your agent uses when the user mentions Nubase broadly, wants a backend for an AI-generated app, or needs to deploy/publish generated code online — across Database, Auth, Storage, Assets…
AI Model Nodejs
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses for Node.js backend AI via @cloudbase/node-sdk (=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration.
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…
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…
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…
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…
Related
Categories
Questions about Pioreactor Plugin Jobs
What does Pioreactor Plugin Jobs do?
Create, update, debug, or review Pioreactor plugin background jobs, including file-based plugin modules, BackgroundJobContrib or LongRunningBackgroundJobContrib classes, pio run command…. Pioreactor Plugin Jobs is an agent skill from Pioreactor/pioreactor. Create, update, debug, or review Pioreactor plugin background jobs, including file-based plugin modules, BackgroundJobContrib or LongRunningBackgroundJobContrib classes, pio run command registration, published settings, MQTT listeners, cleanup hooks, OD-dodging jobs, local discovery through PLUGINSDEV, and UI job descriptors under plugins/ui/jobs.
When should I use Pioreactor Plugin Jobs?
Pioreactor Plugin Jobs fits situations like: custom jobs that should run from pio; appear in the Pioreactor UI.
How do I install Pioreactor Plugin Jobs in Claude Code?
Run `npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a claude-code`. Or copy the skill folder (.agents/skills/pioreactor-plugin-jobs in Pioreactor/pioreactor) into .claude/skills/pioreactor-plugin-jobs in your project. Claude Code loads it when a task matches its description.
How do I install Pioreactor Plugin Jobs in Codex?
Run `npx skills add Pioreactor/pioreactor --skill pioreactor-plugin-jobs -a codex`. Or copy the skill folder (.agents/skills/pioreactor-plugin-jobs in Pioreactor/pioreactor) into .agents/skills/pioreactor-plugin-jobs in your project. Codex loads it when a task matches its description.
Can I use Pioreactor Plugin Jobs 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-plugin-jobs -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-plugin-jobs, .gemini/skills/pioreactor-plugin-jobs, .github/skills/pioreactor-plugin-jobs and .opencode/skills/pioreactor-plugin-jobs in your project.
What does Pioreactor Plugin Jobs need to run?
SKILL.md names no scripts, command-line tools or credentials: Pioreactor Plugin Jobs is instructions for the agent only.
Does Pioreactor Plugin Jobs 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 Plugin Jobs 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 Plugin Jobs use?
Pioreactor Plugin Jobs 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 Plugin Jobs use?
About 799 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Pioreactor Plugin Jobs?
Skills that share tags, products or a category with Pioreactor Plugin Jobs: Trigger.dev Configuration (papermark/papermark, 9.2k stars), Foundatio (FoundatioFx/Foundatio, 2.1k stars), Laravel Specialist (Jeffallan/claude-skills, 12k stars) and Trigger.dev Realtime (papermark/papermark, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pioreactor Plugin Jobs?
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.