514-perf-optimize

Profiles a Moose deployment to identify slow queries and bottlenecks across seven stages.

3|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/514-labs/agent-skills --skill 514-perf-optimize
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: 514-perf-optimize
Source: https://github.com/514-labs/agent-skills/tree/main/skills/514/perf-optimize
Command: npx skills add https://github.com/514-labs/agent-skills --skill 514-perf-optimize

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve?

Profile a Moose deployment to identify slow queries, bottlenecks, and optimization opportunities.

Core Features & Use Cases

  • Seven-stage end-to-end workflow: SETUP, PROFILE, PROPOSE, BASELINE, EXPERIMENT, COMPARE, SHIP.
  • Maps findings to code and proposes candidate optimizations, benchmarks them, and ships a PR.
  • Supports referencing detailed procedures in the references/ docs and is designed for MooseStack + ClickHouse environments.

Quick Start

Start the seven-stage workflow on your 514/Moose deployment to begin profiling and optimization.

Frequently Asked Questions about 514-perf-optimize

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

FAQPage Schema
How do I identify slow ClickHouse queries in a MooseStack deployment?ā–¼

ClickHouse query profiling in a MooseStack deployment identifies slow queries and bottlenecks by analyzing production metadata and query logs. It maps findings to code and uses benchmarking to propose and validate candidate optimizations.

What is the best way to benchmark ClickHouse query optimizations?ā–¼

Benchmarking ClickHouse query optimizations requires establishing baseline metrics before running experiments. The workflow captures BASELINE_METRICS and BENCHMARK_QUERIES, then compares experimental results against the baseline to validate performance improvements.

Do I need access to production query logs to profile a Moose deployment?ā–¼

Profiling a Moose deployment requires access to production metadata, query logs, and the Moose workspace to accurately identify bottlenecks. These inputs allow the optimization workflow to map performance findings directly to code.

Can I ship a PR directly after benchmarking ClickHouse changes?ā–¼

Shipping a PR directly after benchmarking ClickHouse changes is supported by the workflow. It outputs a PR-ready summary after completing the COMPARE stage, which validates experimental benchmark results against established baseline metrics.

How does the ClickHouse optimization workflow map findings to code?ā–¼

The ClickHouse optimization workflow maps findings to code during the PROPOSE stage after profiling bottlenecks. It proposes candidate optimizations based on identified slow queries, then benchmarks these code changes before generating a PR-ready summary.