Physicalai Train Benchmarking A Policy
open-edge-platform/physical-ai-studio
Benchmarks a trained Physical AI Studio policy in a simulation gym and reports success metrics.
Instantiate or update a workspace UNITS.csv from a selected pipeline and units template (deps/checkpoints/acceptance).
Install Unit Planner
$ npx skills add WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills unit-planner --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/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/unit-planner .claude/skills/unit-planner && 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 "unit-planner" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-planner into .claude/skills/unit-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-planner", 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/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-plannerType 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 WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills unit-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/unit-planner .agents/skills/unit-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "unit-planner" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-planner into .agents/skills/unit-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-planner", 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 WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills unit-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/unit-planner .cursor/skills/unit-planner && 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 "unit-planner" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-planner into .cursor/skills/unit-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-planner", 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/WILLOSCAR/research-units-pipeline-skills.git --path .codex/skills/unit-planner--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 WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills unit-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/unit-planner .gemini/skills/unit-planner && 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 "unit-planner" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-planner into .gemini/skills/unit-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-planner", 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 WILLOSCAR/research-units-pipeline-skills unit-plannerInstalls 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 WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/unit-planner .github/skills/unit-planner && 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 "unit-planner" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-planner into .github/skills/unit-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-planner", 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 WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WILLOSCAR/research-units-pipeline-skills unit-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WILLOSCAR/research-units-pipeline-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/unit-planner .opencode/skills/unit-planner && 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 "unit-planner" agent skill from https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/unit-planner into .opencode/skills/unit-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-planner", 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
unit-planner- GitHub stars
- 513
- Token cost
- ~578 tokens
- SKILL.md length
- 242 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- None found
At a glance
Instantiate or update a workspace UNITS.csv from a selected pipeline and units template (deps/checkpoints/acceptance).
- Works in 5 steps: Read PIPELINE.lock.md (or ask to create… → Copy the pipeline’s units_template into… → If UNITS.csv exists, only edit it to… → …
- Tasks that involve CSV and tabular files
- SKILL.md covers Triggers & routing, Goal, Inputs and Outputs, plus 4 more sections
- Calls uv
What it does
Unit Planner is an agent skill from WILLOSCAR/research-units-pipeline-skills. Instantiate or update a workspace UNITS.csv from a selected pipeline and units template (deps/checkpoints/acceptance).
Its SKILL.md is about 580 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 Documents & Office, covering CSV and tabular files. The repository describes itself as: Research pipelines as semantic execution units: each skill declares inputs/outputs, acceptance criteria, and guardrails. Evidence-first methodology prevents hollow writing…
When your agent uses it
- Tasks that involve CSV and tabular files
Example prompts
- “/unit-planner”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read PIPELINE.lock.md (or ask to create it via pipeline-router).
- Copy the pipeline’s units_template into the workspace as UNITS.csv if missing.
- If UNITS.csv exists, only edit it to reflect
- Ensure every unit has: unit_id, skill, outputs, acceptance, checkpoint, status, owner.
- Keep checkpoints consistent with CHECKPOINTS.md; add missing checkpoints if the pipeline uses custom checkpoints.
What it can do on your machine
Read from SKILL.md and the folder at commit c92912a. 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:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
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
Unit Planner loads about 578 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 242 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 242 words (~578 tokens).
- name
- unit-planner
- binding
- library
Files
Just SKILL.md in .codex/skills/unit-planner of WILLOSCAR/research-units-pipeline-skills.
Open the folder on GitHubat commit c92912a
Compare with similar skills
Unit Planner 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 |
|---|---|---|---|---|---|---|
| Unit Planner this skillWILLOSCAR/research-units-pipeline-skills | 513 | — | ~578 | Automated safety check: Pass | None | |
| Physicalai Train Benchmarking A Policyopen-edge-platform/physical-ai-studio | 129 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Sector Analysttradermonty/claude-trading-skills | 3k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Data Cleanupsgharlow/claude-code-recipes | 389 | — | ~566 | Automated safety check: Pass | Custom licence | |
| Sn Da Image CaptionMichaelYang-lyx/AIDABench | 111 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Data Extractorhanzili/hanzi-browse | 177 | — | ~2.2k | Automated safety check: Pass | Custom licence |
Similar skills
Sector Analyst
tradermonty/claude-trading-skills
This skill should be used when analyzing sector rotation patterns and market cycle positioning.
Data Cleanup
sgharlow/claude-code-recipes
Clean and standardize messy tabular data (CSV, spreadsheet paste, system exports) into an analysis-ready dataset — consistent dates and names, typed columns, duplicates identified, missing values…
Sn Da Image Caption
MichaelYang-lyx/AIDABench
图片理解与数据提取 skill。当图片文件（.png/.jpg/.jpeg/.gif/.webp/.bmp）是主要输入且用户需要理解、提取数据或分析图片内容时使用。提供预配置的 caption 脚本（scripts/caption.py），通过 vision 模型将图片转为文本描述，无需额外配置 API Key。覆盖：(1) 通过 scripts/caption.py…
Data Extractor
hanzili/hanzi-browse
Extract structured data from websites into CSV or JSON. An agent skill from hanzili/hanzi-browse.
Wjs X Increasing Follower
jianshuo/claude-skills
A skill your agent uses when 王建硕 wants to systematically grow his X (Twitter) followers by running numbered, A/B-testable growth experiments and tracking which ones actually work.
More from WILLOSCAR/research-units-pipeline-skills
All 107 skills in this repoAppendix Table Writer
WILLOSCAR/research-units-pipeline-skills
Curate reader-facing survey tables for the Appendix (clean layout + high information density), using only in-scope evidence and existing citation keys.
Artifact Contract Auditor
WILLOSCAR/research-units-pipeline-skills
Audit one research Workspace for declared Unit outputs and Pipeline target Artifacts, writing output/CONTRACTREPORT.md; use for mid-Run coverage snapshots or final delivery completeness, not deep…
Arxiv Search
WILLOSCAR/research-units-pipeline-skills
Retrieve arXiv paper metadata with keyword queries or import an offline arXiv export, and save results as JSONL (papers/papersraw.jsonl).
Chapter Lead Writer
WILLOSCAR/research-units-pipeline-skills
Write H2 chapter lead blocks (sections/S<secidlead.md) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.
Chapter Skeleton
WILLOSCAR/research-units-pipeline-skills
Build a retrieval-informed chapter skeleton (outline/chapterskeleton.yml) from taxonomy/core scope before stable H3 decomposition.
Dedupe Rank
WILLOSCAR/research-units-pipeline-skills
A skill your agent uses when a broad paper candidate pool needs deterministic deduplication and a stable core set.
Related
Questions about Unit Planner
What does Unit Planner do?
Instantiate or update a workspace UNITS.csv from a selected pipeline and units template (deps/checkpoints/acceptance). Unit Planner is an agent skill from WILLOSCAR/research-units-pipeline-skills.csv from a selected pipeline and units template (deps/checkpoints/acceptance).
When should I use Unit Planner?
Unit Planner fits situations like: tasks that involve CSV and tabular files.
How do I install Unit Planner in Claude Code?
Run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a claude-code`. Or copy the skill folder (.codex/skills/unit-planner in WILLOSCAR/research-units-pipeline-skills) into .claude/skills/unit-planner in your project. Claude Code loads it when a task matches its description.
How do I install Unit Planner in Codex?
Run `npx skills add WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a codex`. Or copy the skill folder (.codex/skills/unit-planner in WILLOSCAR/research-units-pipeline-skills) into .agents/skills/unit-planner in your project. Codex loads it when a task matches its description.
Can I use Unit Planner 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 WILLOSCAR/research-units-pipeline-skills --skill unit-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unit-planner, .gemini/skills/unit-planner, .github/skills/unit-planner and .opencode/skills/unit-planner in your project.
What does Unit Planner need to run?
Going by SKILL.md and its folder, Unit Planner needs the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Unit Planner access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Unit Planner 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 Unit Planner use?
No licence was found for Unit Planner or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Unit Planner use?
About 578 tokens (SKILL.md is roughly 2.3k 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 Unit Planner?
Skills that share tags, products or a category with Unit Planner: Physicalai Train Benchmarking A Policy (open-edge-platform/physical-ai-studio, 129 stars), Sector Analyst (tradermonty/claude-trading-skills, 3k stars), Data Cleanup (sgharlow/claude-code-recipes, 389 stars) and Sn Da Image Caption (MichaelYang-lyx/AIDABench, 111 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Unit Planner?
WILLOSCAR (a GitHub user) maintains it in WILLOSCAR/research-units-pipeline-skills, which has 513 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on October 5, 2026.
Source: WILLOSCAR/research-units-pipeline-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.