Agent Skills › dartsim/dart › dart-benchmark-packet

dart-benchmark-packet

GitHub

用于构建基准测试并生成或刷新证明数据包。通过识别所属计划、执行基准测试、写入证据包及运行校验器，确保测量数据的准确性和合规性，适用于需要标准化性能证据的场景。

.codex/skills/dart-benchmark-packet/SKILL.md dartsim/dart

Trigger Scenarios

用户请求生成或更新DART基准测试证据包用户提及dart-benchmark-packet命令或相关计划验证需求

Install

npx skills add dartsim/dart --skill dart-benchmark-packet -g -y

More Options

Non-standard path

npx skills add https://github.com/dartsim/dart/tree/main/.codex/skills/dart-benchmark-packet -g -y

Use without installing

npx skills use dartsim/dart@dart-benchmark-packet

指定 Agent (Claude Code)

npx skills add dartsim/dart --skill dart-benchmark-packet -a claude-code -g -y

安装 repo 全部 skill

npx skills add dartsim/dart --all -g -y

预览 repo 内 skill

npx skills add dartsim/dart --list

SKILL.md

Frontmatter

{
    "name": "dart-benchmark-packet",
    "description": "DART Benchmark Packet: author or refresh a benchmark evidence packet for an owning plan"
}

dart-benchmark-packet

Use this skill in Codex to run the DART dart-benchmark-packet workflow. The editable workflow source currently lives in .claude/commands/, and this generated Codex skill is a first-class Codex entrypoint.

Invocation

Claude Code/OpenCode: /dart-benchmark-packet <arguments>
Codex: $dart-benchmark-packet <arguments>

Treat the text after the skill name as $ARGUMENTS. When the workflow references $1, $2, etc., map those to the positional values supplied by the user.

Command Body

Author or refresh a benchmark evidence packet: $ARGUMENTS

Required Reading

@AGENTS.md @docs/onboarding/profiling.md

Also read the owning plan file named by the packet (for example docs/plans/<NNN>-<slug>.md) and its packet convention.

Workflow

Identify the owning plan and its packet convention: the packet checker (for example pixi run check-avbd-packets) and the packet generator (for example scripts/write_*_packet.py) that the plan names.
Build the benchmark target and run the benchmark that feeds the packet, following docs/onboarding/profiling.md for a stable measurement setup.
Run the packet writer to record the machine-generated evidence packet with its provenance and resolved configuration.
Validate the packet with the plan's packet checker; treat a failing checker as incomplete evidence and fix the packet, not the checker.
Prepare the owning plan's row or link update that task-specific gates require, but leave editing the plan file to the plan's own workflow — this command prepares and validates the packet. This is a local task; do not push or open PRs without explicit maintainer/user approval.