benchmark-docs

Maintains dual-platform benchmark documentation across ARM and x86_64 architectures.

51|3|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/rust-works/succinctly --skill benchmark-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark-docs
Source: https://github.com/rust-works/succinctly/tree/main/.claude/skills/benchmark-docs
Command: npx skills add https://github.com/rust-works/succinctly --skill benchmark-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains consistent benchmark documentation across multiple platforms (ARM/Apple Silicon and x86_64/Intel/AMD) to prevent data drift and miscommunication. It ensures that results, inventories, and update guidelines stay synchronized.

Core Features & Use Cases

  • Cross-platform parity rules: preserves dual-platform benchmarks and updates simultaneously.
  • Directory and file inventory: tracks where benchmarks and results live (data/bench/generated, data/bench/results, docs/benchmarks/*.md, README.md).
  • Update workflow: follows the documented process to add new results and reflect them in documentation.

Quick Start

Follow the benchmarking workflow documented in docs/guides/benchmarking.md to add new results and keep platform data in sync.

Frequently Asked Questions about benchmark-docs

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

FAQPage Schema
How do I keep cross-platform benchmark documentation consistent across ARM and x86_64?

To keep cross-platform benchmark documentation consistent, you enforce dual-platform parity rules that update ARM/Apple Silicon and x86_64/Intel/AMD results simultaneously to prevent data drift. This ensures benchmark inventories and docs stay synchronized across architectures.

What is the standard workflow to update benchmark results and prevent discrepancies?

The standard workflow to update benchmark results involves following the documented process in benchmarking guides to add new data and reflect it in documentation. This prevents discrepancies by enforcing simultaneous updates across dual-platform benchmarks and directory inventories.

Where should generated benchmark results and inventory files be placed in my repository?

Generated benchmark results and inventory files should be placed under specific directories: data/bench/generated, data/bench/results, and docs/benchmarks/*.md. This standardized placement ensures benchmarks are tracked and synchronized correctly across platforms.

Can I use this to document jq comparison benchmarks across different processor architectures?

Yes, you can use this to document jq comparison benchmarks across different processor architectures. It specifically manages dual-platform benchmarks for ARM/Apple Silicon and x86_64/Intel/AMD, enforcing cross-platform parity and updating results simultaneously.

How do I track and inventory cross-platform benchmark data to avoid miscommunication?

To track cross-platform benchmark data and avoid miscommunication, maintain a directory and file inventory that monitors where benchmarks live, including data/bench/generated and docs/benchmarks/*.md. This prevents data drift by keeping results and guidelines synchronized.