skills.rest
514-labs
514-labsOFFICIAL
Explore all skills by this author →
Website𝕏@514hqGitHub

dec-bench-local-test

Compile the DEC Bench CLI from source and run scenario tests in Docker containers.

1|2|Updated Feb 22, 2026
Search Tags:#cli#docker#rust#scenarios#local-testing#testing-infra#dec-bench
One-click install
npx skills add https://github.com/514-labs/agent-evals --skill dec-bench-local-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dec-bench-local-test
Source: https://github.com/514-labs/agent-evals/tree/main/.agents/skills/dec-bench-local-test
Command: npx skills add https://github.com/514-labs/agent-evals --skill dec-bench-local-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and validate DEC Bench scenarios locally by compiling the CLI from source and running tests in containers, reducing feedback cycles before CI.

Core Features & Use Cases

  • Build the DEC Bench CLI from source and run scenarios against lightweight containers locally.
  • Debug, tweak entrypoints, and verify harness configurations before pushing changes to CI.

Quick Start

Run a local build and execution of a DEC Bench scenario using cargo and Docker to validate changes before pushing to CI.

Frequently Asked Questions about dec-bench-local-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test DEC Bench scenarios locally before pushing to CI?▼

Test DEC Bench scenarios locally by compiling the CLI from source with cargo and running tests in Docker containers. This validates scenario changes, assertion fixes, and harness configurations before pushing to CI.

Do I need Docker to build and run DEC Bench CLI scenarios?▼

Yes, Docker is required to run DEC Bench scenarios locally. The Skill operates via cargo and Docker, using lightweight containers to validate scenario changes, entrypoint modifications, and harness configurations.

What's the best way to debug entrypoints and harness configurations for Rust CLI tests?▼

Debug Rust CLI entrypoints and harness configurations by compiling from source with cargo and running the scenarios in local Docker containers. This reduces feedback cycles before pushing changes to CI.

Why run local container tests instead of relying on CI for scenario validation?▼

Run local container tests to reduce feedback cycles before CI. Compiling the CLI from source and validating scenario changes locally prevents broken entrypoints and assertion fixes from failing in remote pipelines.

Related Skills

Explore More Software Engineering Skills→
RediSearchRediSearch
6.2k

run-rust-benchmarks

Run Rust benchmarks and compare performance against the C implementation.

Official
Advanced
louloulinlouloulin
19

deployment-automation

Automates build, test, and deploy pipelines for GitHub Actions and GitLab CI.

Community
Advanced
ZESCODEZESCODE

docker-patterns

Standardize Docker and Docker Compose configurations for development and production.

Community
Intermediate
JustineDevsJustineDevs
2

ask-gemini

Execute Gemini CLI prompts and archive outputs as markdown artifacts.

Community
Intermediate