Menú
Use when demonstrating or tuning a compile-heavy LLVM/clang build workload with sched-claw. Covers the demo launcher, direct build metrics, and the fallback path to IPC/CPI proxies.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | llvm-clang-build-tuning |
| description | Use when demonstrating or tuning a compile-heavy LLVM/clang build workload with sched-claw. Covers the demo launcher, direct build metrics, and the fallback path to IPC/CPI proxies. |
| aliases | ["llvm-build-demo","clang-build-tuning"] |
| tags | ["sched-claw","llvm","clang","build","scheduler"] |
This is a workload profile, not a foundational workflow skill. It should supply workload-specific selectors, direct metrics, and likely scheduler levers, then compose the generic skills that do the actual contract, collection, analysis, policy mapping, codegen, and rollout work.
sched-workload-contractsched-perf-collectionsched-perf-analysissched-policy-mappingsched-ext-codegensched-ext-run-evaluationsched-ext-rollout-safetybuild_seconds:minimizeconfigure_seconds:minimizeipc:maximize, cpi:minimizeapps/sched-claw/scripts/demos/llvm-clang-autotune.shapps/sched-claw/scripts/workloads/run-llvm-clang-build.shbuild.log, configure.log, and metrics.env.references/demo-contract.mdUse when sched-ext source has to be edited, then compiled, verifier-checked, and persisted with concrete artifacts. Covers build command hygiene, libbpf or verifier triage, and script-friendly artifact capture.
Use when baseline and candidate runs need to be executed and compared with reproducible artifacts instead of free-form notes. Covers repeated runs, metrics import, noise handling, and script-driven comparison instead of host-owned scoring.
Use when a tuning request needs to be turned into a durable workload contract before any sched-ext code is changed. Covers selectors, direct metrics, proxy metrics, guardrails, and saved contract hygiene.
Use when a sched-ext candidate is about to be activated through the privileged daemon. Covers rollout gates, daemon usage limits, rollback triggers, and how to keep deployment evidence attributable.
Use when collected scheduler evidence needs to be turned into explicit facts, inferences, unknowns, and candidate design implications. Covers repo helper scripts for uv-managed analysis environments, pandas or polars summaries, and matplotlib plots.
Use when scheduler-related performance evidence has to be collected reproducibly for a workload, target selector, or experiment phase. Covers low-overhead counters first, escalation to traces, and repo scripts that keep capture deterministic without baking a workflow into the host.