benchmark

Execute nucleo's benchmark suite measuring token cost, speed, and format compatibility across builds.

2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mateonunez/nucleo --skill benchmark-mateonunez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/mateonunez/nucleo/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/mateonunez/nucleo --skill benchmark-mateonunez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Benchmarking nucleo's performance by running a standardized benchmark suite to quantify token consumption and execution speed for release builds.

Core Features & Use Cases

  • Quick smoke tests to verify baseline performance after changes.
  • Full benchmark runs to compare token usage, latency, and format handling across builds.
  • Use case: validate performance regressions before releases and provide data for optimization.

Quick Start

Build nucleo in release mode and run the quick benchmark to capture baseline results.

Frequently Asked Questions about benchmark

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

FAQPage Schema
How do I measure token cost and execution speed for nucleo builds?

Measuring token cost and execution speed requires running the standardized benchmark suite to quantify token consumption and latency for release builds. Results are stored in the benchmarks/results directory.

What's the best way to run a quick smoke test for nucleo performance?

Quick smoke tests verify baseline performance after changes by executing a fast benchmark run. Build nucleo in release mode and run the quick benchmark to capture baseline results.

Do I need a release binary to benchmark nucleo performance?

Yes, a built release binary is required to benchmark nucleo performance. Additionally, the benchmark scripts located under the benchmarks directory are needed to execute the assessment.

What metrics does the nucleo benchmark suite evaluate?

The benchmark suite evaluates token cost measurement, execution speed, and format-compatibility across builds. It provides data for optimization and validates performance regressions before releases.

Where are nucleo benchmark results stored after a full run?

Benchmark results are stored in the benchmarks/results directory. Full benchmark runs compare token usage, latency, and format handling across builds.

Can I compare format-compatibility across different nucleo builds?

Yes, full benchmark runs compare format-compatibility across builds. The suite targets format handling scenarios, enabling quick smoke tests or full assessments to validate compatibility.