菜单
Build or publish nemo-switchyard Python distributions through the repository's GitHub Actions workflow. Use when asked to build a development wheel, cut a Python release, publish to PyPI, create a release tag, or debug .github/workflows/publish.yml.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/NVIDIA-NeMo/Switchyard --skill publish-python-release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Deep dive on Harbor trial results for tasks that use SWE-Bench-style F2P (FAIL_TO_PASS) and P2P (PASS_TO_PASS) reference tests. Diagnoses why an agent failed and audits whether a failing task is genuinely hard or unfair (instruction-vs-verifier mismatch). Use when the user asks to analyze, debug, investigate, or deep dive on a Harbor run, trial, or job directory; when the user says "harbor deep dive", "f2p deep dive", or "p2p deep dive"; when a trial scores lower than expected; or when the user wants to assess task fairness, instruction quality, verifier correctness, or whether an F2P or P2P test is reasonable for the instruction given. Works with any Harbor task whose verifier reports F2P/P2P-style results, and with any supported agent (claude-code, opencode, codex). Produces a per-failure root-cause verdict (capability gap / verifier issue / instruction issue) by triangulating verifier output, the agent's implementation, the reference tests, and the instruction.
Review CRAFT Search gold answer quality for a specific task. Use when the user asks to review, check, investigate, or look closely at a craft-* task ID. Evaluates gold files, functions, assertions, and explanation against actual source code and agent tier results. Produces actionable recommendations (keep/remove/demote/promote/edit) with evidence.
Review Switchyard Rust changes for correctness and maintainability. Use for pull requests or diffs touching crates, PyO3 bindings, async runtime behavior, streaming, protocol types, translation, algorithms, or LLM clients.
基于 SOC 职业分类
正在显示 SKILL.md
| name | publish-python-release |
| description | Build or publish nemo-switchyard Python distributions through the repository's GitHub Actions workflow. Use when asked to build a development wheel, cut a Python release, publish to PyPI, create a release tag, or debug .github/workflows/publish.yml. |
Use .github/workflows/publish.yml as the source of truth. The supporting runbook is
docs/internal/release_workflow.md.
| Intent | Trigger | Result |
|---|---|---|
| One temporary wheel | Manual dispatch with build_dev_artifact=true | Linux x86_64 GitHub artifact, retained for one day |
| Full matrix test | Manual dispatch with build_dev_matrix=true | sdist and wheel artifacts; no publish |
| Official release | Push vMAJOR.MINOR.PATCH matching pyproject.toml | Full matrix, PyPI publish, GitHub Release |
Manual builds are artifact-only. Official releases use PyPI Trusted Publishing through the
GitHub environment named pypi; do not add a long-lived PyPI token.
pyproject.toml; do not rely on remembered inputs or versions.Example development dispatch:
gh workflow run publish.yml \
-f build_dev_artifact=true \
-f build_dev_matrix=false \
-f dev_version=0.0.1.dev0
pyproject.toml, and package metadata.Cargo.toml,
dependency publication order, and crates.io ownership before running cargo publish.uv run ruff check scripts/release/set_dev_wheel_version.py tests/test_dev_wheel_versioning.py
uv run pytest tests/test_dev_wheel_versioning.py -v
python scripts/release/set_dev_wheel_version.py 0.0.1.dev0 --print-version
git diff --check