agentleFS
Sign inStart free
kvantatechkvantatech/RedLine/.github/skills/k6-profile-benchmark/SKILL.md

k6-profile-benchmark

Skill1 starsChanged 3 months agoMITView on GitHub

Type: skill (deterministic) · Used by: perf-run-one, perf-sweep, run-k6-action gate · Status: STUB (P0 scaffold — not yet implemented)

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No model call: pure config emission for the deterministic deploy gate.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

k6-profile-benchmark

1-VU benchmark/smoke profile — the daily per-deploy signal.

Type: skill (deterministic) · Used by: perf-run-one, perf-sweep, run-k6-action gate · Status: STUB (P0 scaffold — not yet implemented)

Prompt

Emit the k6 execution config for a 1-VU benchmark/smoke run. Inputs: team, profile (always benchmark). Output: {executor, load_shape, cadence, exec_mode, baseline_path}.

  • cadence: daily
  • exec_mode: local
  • Standard shape: 1 VU, 10 iterations, per-vu-iterations executor — 10 samples is the minimum for a statistically meaningful p95. Never 1 iteration.
  • This is the ONLY profile permitted on PROD — and only with a one-time approval token and vus <= 1 (DEC-prod-scripts Option B). No model call: pure config emission for the deterministic deploy gate.

Tools

none — deterministic (plain code)

Data

  • Reads: baselines/<team>.benchmark.json
  • Writes: none (config object passed downstream to run-k6-script)

Notes

  • Activation: P0 (config + grammar) / P2 (full profile authoring). Benchmark FIRST per DEC-5testtypes.
  • The baselines/<team>.<profile>.json grammar is LOCKED at P0.
  • p95 everywhere. The run-k6-action deploy gate has ZERO model calls.
  • PROD rule: permitted only with one-time approval token AND vus <= 1.

Frozen skill registry: AGENTS.md in this repo

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free