メニュー
Publishes benchmark result JSONs into README/docs safely. Use when updating README tables, using MacBook RGB results, preserving Pillow results for the website, running tools/update_docs.sh, or preventing pyperf raw JSON from polluting documentation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Validates whether benchmark artifacts cover the paper's required RGB micro and RGB DataLoader sections. Use when checking missing RGB runs, deciding what to run next, validating gcp_runs/output folders, or preparing paper tables.
Automates running image/video augmentation benchmarks for single or multiple libraries, validates outputs, generates comparison reports, and updates documentation. Use when running benchmarks, comparing library performance, or when the user mentions benchmark, benchmark.cli, pyperf, GCP benchmark runs, or performance testing.
Updates benchmark documentation with latest results including README tables, speedup plots, and library metadata. Use when updating documentation, generating comparison tables, or when the user mentions update_docs.sh or documentation generation.
Triage detached GCP benchmark runs, DONE/FAILED sentinels, VM cleanup, vm.log, gcp_last_run.json, and partial result downloads. Use when GCP benchmark logs mention DONE, FAILED, exit_code.txt, VM disappeared, STOPPING, gcloud machine type errors, or missing artifacts.
Guides adding support for new image/video augmentation libraries to the benchmark suite. Use when integrating a new library, adding library support, or when the user mentions adding a new augmentation library to test.
Executes the paper benchmark plan for RGB, multichannel, DataLoader, and video benchmarks. Use when the user mentions the paper benchmark, deadline plan, machine matrix, RGB micro, multichannel, DataLoader, video GPU, c4/c4d/g2 machines, or what to run next.
| name | benchmark-results-publisher |
| description | Publishes benchmark result JSONs into README/docs safely. Use when updating README tables, using MacBook RGB results, preserving Pillow results for the website, running tools/update_docs.sh, or preventing pyperf raw JSON from polluting documentation. |
Use this when turning completed benchmark artifacts into documentation.
While the full paper matrix is still running, tools/update_docs.sh defaults to MacBook M4 RGB micro results:
./tools/update_docs.sh
Equivalent explicit path:
./tools/update_docs.sh \
--image-results output/rgb_micro_macos_m4max/image-rgb/micro
Pass --video-results only when intentionally updating video README sections.
*_results.json, including scenario names like albumentationsx_micro_results.json.*.pyperf.json; never load them as README columns.gcp_runs/, output/, or output_*/ artifacts.Run after docs changes:
python -m pytest tests/test_compare.py tests/test_update_readme.py
pre-commit run --all-files