SKILLEMALL.ai

AD fine-tuning-serving-openpi

Fine-tune and serve Physical Intelligence OpenPI models (pi0, pi0-fast, pi0.5) using JAX or PyTorch backends for robot policy inference across ALOHA, DROID, and LIBERO environments. Use when adapting pi0 models to custom datasets, converting JAX checkpoints to PyTorch, running policy inference servers, or debugging norm stats and GPU memory issues.

Orchestra-Research/AI-Research-SKILLs Agent Skills author: Orchestra-Research MIT 6 files body ≈ 3 395 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Fine-tune and serve Physical Intelligence OpenPI models (pi0, pi0-fast, pi0.5) using JAX or PyTorch backends for robot policy inference across ALOHA, DROID…

As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGitHubAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
D
39/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "dependencies"

    Process rating: all ten parameters 39/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 40Consistency. Frontmatter name (fine-tuning-serving-openpi) differs from the folder (openpi)
    • 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
    • 100Steps. 16 steps
    • 100Execution cost. Instruction body is 3395 tokens
    • low 12 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (4 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 350: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 16 items
    • +4Has examples (36 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.