菜单
Audit this Linux PC for the Skillful RAN software-only OCUDU campaign. Use when you need a non-destructive checkpoint before building images, cloning sources, or running the local and ZMQ lanes. Do not use it to build code, start containers, or promote files into tracked skills.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build the repo-owned Docker images used by the Skillful RAN OCUDU campaign. Use when the workspace is ready and the next step is to prepare the pinned build and runtime containers. Do not use it to clone source code, run Open5GS, or promote skill drafts.
Run the software-only local OCUDU lane on one host using split CU DU binaries, no-core, and test-mode overlays. Use when the user wants a 60 second local runtime checkpoint after the RAN build is complete. Do not use it for Open5GS, srsUE, or skill promotion work.
Control the vendored Open5GS compose stack used by the Skillful RAN proof-of-concept lane. Use when the user wants the core brought up, checked, or torn down through repo-owned assets. Do not use it for the local no-core lane, the srsUE build, or tracked skill QA.
Build the pinned OCUDU-aligned RAN side from srsRAN Project release_25_10 in the local workspace. Use when the user wants the concrete project source cloned and compiled inside the repo-owned Docker build environment. Do not use it for host readiness checks, Open5GS core control, or srsUE builds.
Run the proof-of-concept OCUDU lane with `srsRAN_Project` gNB, vendored Open5GS, `srsUE`, and ZeroMQ. Use when the user wants the software-only attach plus ping path on this PC. Do not use it for the local no-core lane, source builds, or skill promotion.
Review scratch OCUDU or srsRAN artifacts and scaffold compact tracked skills for Skillful RAN. Use when reusable scripts, notes, or examples should move out of `.local/ocudu/` and into `skills/`. Do not use it to build software, run runtime stages, or skip the skill QA gate.
| name | ocudu-pc-readiness |
| description | Audit this Linux PC for the Skillful RAN software-only OCUDU campaign. Use when you need a non-destructive checkpoint before building images, cloning sources, or running the local and ZMQ lanes. Do not use it to build code, start containers, or promote files into tracked skills. |
workspace: root lab path, defaulting to .local/ocudu/profile: ubuntu-24.04-gaming-pc or portable-linuxcheck_docker: include Docker and Compose reachability checkscheck_storage: include disk and RAM headroom checkscheck_usb: inspect attached USB devices for SDR-like hardwaredry_run: still writes evidence, but never changes the hoststrict: fail if any blocker is presenttool.json for the contract.scripts/run_pc_readiness.py to write summary.json under .local/ocudu/stages/ocudu-pc-readiness/<timestamp>/.references/readiness-baseline.md and the current PC notes.ocudu-docker-build-env only after the blocker list is understood.passed, summary, warnings, artifacts, next_stepsblockers: commands, packages, or permissions blocking the campaignchecks: per-check status recordsstage_dir: evidence path for this checkpointhardware: compact OS, CPU, PCIe, and USB profiledocker or docker compose is unavailable to the current user, stop and fix that before build work.lspci or lsusb are missing, return a partial report and say what could not be inspected.