القائمة
Validate your DEC Bench setup and run your first scenario. Use when a user says "get started", "first run", "test my setup", or "run a quick benchmark".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | dec-bench-quickstart |
| description | Validate your DEC Bench setup and run your first scenario. Use when a user says "get started", "first run", "test my setup", or "run a quick benchmark". |
Validate the user's setup and run their first benchmark scenario.
Check that everything is in place before running:
docker info — if it fails, tell the user to start Docker Desktopdec-bench list — if it fails, tell the user to install with curl -fsSL https://decbench.ai/install.sh | shscenarios/foo-bar-csv-ingest/scenario.json exists — if not, the user isn't in the repo rootANTHROPIC_API_KEY is set (or OPENAI_API_KEY / CURSOR_API_KEY depending on which agent they want to use) — if not, ask them to export itIf anything is missing, tell the user exactly what to fix and stop. Don't proceed with a broken setup.
Once setup is validated, run the first scenario:
dec-bench build --scenario foo-bar-csv-ingest
dec-bench run --scenario foo-bar-csv-ingest
dec-bench results --latest --scenario foo-bar-csv-ingest
Explain the output: which gate the agent reached, the normalized score, and where the artifacts are.
The user has a working setup and their first result. Point them to:
dec-bench list to see all available scenariosdec-bench-run skill to run more scenariosdec-bench-create-scenario skill to create their ownBuild and run DEC Bench scenarios, inspect results, and open the audit UI. Use when a user says "run scenario", "run eval", "benchmark", "run foo-bar-*", "run matrix", "compare agents", or asks about specific scenario results.
Capture a DEC Bench (AXP) comparison run set as a Linear snapshot — required GCS trace upload, parent index issue (with eval-validity / cheating / decbench-DX / Moose-feedback findings), Document, and labeled follow-up sub-issues. Halts if `gcloud` is not authenticated and asks the user to log in. Use when a user says "snapshot the results", "publish this comparison to Linear", "create a snapshot from these runs", "document the latest matrix", or after running a multi-cell harness comparison and asking "now what".
Create a new DEC Bench evaluation scenario from scratch. Use when a user says "create scenario", "new scenario", "add eval", "write a benchmark for", "create a performance test", or describes a data engineering task they want to benchmark.
Substitute a locally-built artifact — a binary (moose-cli, moose-lib, clickhouse, 514 CLI), a directory (Claude skills, template-packages), or a JSON fragment (MCP servers) — into a DEC Bench scenario image so changes can be tested end-to-end without cutting a release. Use when a developer says "test my local moose build", "try my patched moose-lib", "iterate on a skill inside dec-bench", "test a clickhouse patch against scenarios", "run moose-user scenarios against a patched binary", or "override <X> in a scenario".
Build and run DEC Bench scenarios locally using the Cargo-built CLI and Docker. Use when testing scenario changes, assertion fixes, entrypoint modifications, or harness configurations before pushing to CI.
Apply Eugene Schwartz's "Breakthrough Advertising" framework to write high-converting digital copy. Use for landing pages, Facebook/Google ads, email sequences, sales pages, and conversion funnels. Use when writing persuasive copy, conversion copywriting, sales copy, ad copy, landing page copy, or when optimizing copy for specific audience awareness levels.