Skip to main content
skillspec port-one-shot bundles the safe single-skill porting ladder after source-shape recon confirms exactly one atomic prose package. It runs grammar/schema/checklist artifacts, source map, doctor, typed mechanical import, schema-derived shape crib, validate, imports check, deps check, scenario tests, compile, compact report, and optional direct-run estimated progress stats — all in one command. The command rejects parent folders with multiple SKILL.md files. Use the workspace flow for multi-skill or plugin-shaped roots, and the revision flow for existing reviewed skill.spec.yml files.
port-one-shot produces a reviewed scaffold, not a finished semantic spec. Missing scenario tests or unresolved dependency gaps are reported as review_required, not treated as passing proof. Do not install without completing the review obligations in the generated spec’s review_required: section.

Synopsis

Options

What the porting ladder bundles

port-one-shot runs the following steps in sequence and collects evidence for each:

Examples

Basic port to a Codex skill loader:
Port with proof enforcement — exits non-zero if any required QA gate fails:
Port and overwrite an existing draft:
Port with token metrics captured in a run directory:

--prove behavior

When --prove is set:
  • Each required QA gate (validate, imports check, deps check) must pass.
  • Scenario test failures or missing tests are reported as review_required (not fake proof).
  • If any required gate fails, the command exits non-zero regardless of other results.
  • Dependency gaps are reported as review_required, not suppressed.
Without --prove, gate failures are reported in the output but the command exits 0.

Git checkout and PR guidance

When the source is inside a local Git checkout, a successful run summary includes PR guidance. The recommended next steps are:
  1. Complete the review obligations in the generated spec’s review_required: section.
  2. Run skillspec validate, skillspec imports check, skillspec test, and skillspec deps check.
  3. Run skillspec install skill --target <target> --dry-run and review the planned writes.
  4. Install, restart the harness, and interact with the SkillSpec-backed skill through the agent.
  5. Open a PR with the generated contracts and proof artifacts against the source skill repo.
  • skillspec doctor <path> — Run a standalone follow-through risk assessment before porting.
  • skillspec import-skill <path> --out <path> — Run just the mechanical import step.
  • skillspec compile <path> --target <target> — Compile a reviewed spec independently.
  • skillspec workspace map <source-root> — Use for multi-skill or plugin-shaped roots.