choose-k6-execution-mode
Skill1 starsChanged 3 months agoMITView on GitHub
Type: skill (deterministic) · Used by: perf-run-one, perf-sweep, perf-author · Status: STUB (P0 scaffold — not yet implemented)
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- k6-browser-testSkill
- k6-load-testSkill
- k6-playwright-converterSkill
- k6-smoke-testSkill
- k6-test-plannerSkill
- apply-ws2-conventionsSkill
- author-resilient-playwrightSkill
- build-status-viewsSkill
- compare-coreSkill
- compare-to-baselineSkill
- corroborate-2-sourcesSkill
- curate-baselinesSkill
- doc-consistency-checkSkill
- emit-otlp-and-prometheusSkill
- estimate-token-costSkill
- explore-product-structureSkill
- file-perf-regression-jiraSkill
- func-verdictSkill
- heal-playwright-suiteSkill
- k6-profile-benchmarkSkill
- k6-profile-loadSkill
- k6-profile-soakSkill
- k6-profile-spikeSkill
- k6-profile-stressSkill
- learn-via-k6-docsSkill
- link-grafana-panelSkill
- notify-responsible-teamSkill
- open-draft-prSkill
- parse-k6-json-summarySkill
- parse-playwright-summarySkill
- perf-run-logSkill
- run-k6-scriptSkill
- run-ledgerSkill
- run-playwright-suiteSkill
- scope-reviewSkill
- scrub-har-secretsSkill
- triage-func-verdictSkill
- triage-perf-verdictSkill
- verify-k6-scriptSkill
- verify-playwright-suiteSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
When implemented, select the k6 execution mode for a given profile: local (single runner) for the benchmark profile and the per-deploy gate …
≈ “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.
Files
choose-k6-execution-mode
Pick local vs k6-operator execution mode for a run — the SCALE pillar.
Type: skill (deterministic) · Used by: perf-run-one, perf-sweep, perf-author · Status: STUB (P0 scaffold — not yet implemented)
Prompt
When implemented, select the k6 execution mode for a given profile: local (single runner) for the benchmark profile and the per-deploy gate — fast and cheap; k6-operator v1.0 (Kubernetes) for heavy profiles (load / stress / soak / spike) that need VU concurrency beyond one runner.
Inputs: profile (+ requested VU/duration) -> Output: chosen mode and its launch parameters.
This is a lookup, not an always-on dependency — it returns a mode, nothing more.
Tools
none — deterministic (plain code)
Data
none
Notes
Activation: P1/P2. The SCALE pillar. Hard rule: benchmark and the deploy gate always run local (latency-sensitive, low cost); only the four heavy profiles route to k6-operator on K8s. Five profiles total: benchmark, load, stress, soak, spike.
Frozen skill registry: AGENTS.md in this repo
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
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.