菜单
Use when evidence has to be turned into explicit scheduler policy levers, invariants, and measurement hypotheses before code generation or rollout. Keeps policy reasoning reusable across workloads and candidate implementations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use 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.
| name | sched-policy-mapping |
| description | Use when evidence has to be turned into explicit scheduler policy levers, invariants, and measurement hypotheses before code generation or rollout. Keeps policy reasoning reusable across workloads and candidate implementations. |
| aliases | ["policy-mapping","lever-mapping"] |
| tags | ["scheduler","policy","analysis"] |
references/lever-mapping.mdsched-workload-contract when the objective or guardrail is still vague.sched-perf-analysis or linux-scheduler-triage when the evidence still needs interpretation.sched-ext-codegen when the next step is source editing.sched-ext-run-evaluation or sched-ext-rollout-safety when the policy still needs a verification plan.scripts/scaffold_policy_mapping.sh is the default helper when you want a reusable mapping notereferences/lever-mapping.mdscripts/scaffold_policy_mapping.sh