End-to-end k6 performance testing for websites, with Grafana backend investigation
Elicit workflows, record with Playwright, build hybrid (protocol + browser) k6 suites with SLO thresholds, run smoke/average/stress/spike/soak/breakpoint, investigate the backend in Grafana, ship a structured report
- What
- Elicit workflows, record with Playwright, build hybrid (protocol + browser) k6 suites with SLO thresholds, run smoke/average/stress/spike/soak/breakpoint, investigate the backend in Grafana, ship a structured report
- Cost
- Free
- Needs
- k6 ≥ 2.0, Node.js ≥ 20, Playwright with Chromium installed, har-to-k6; a website you own or have explicit permission to load-test; optional Grafana Cloud account for cloud-scale runs (billed — browser VU-hours cost 10× protocol VU-hours)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @grafana's official end-to-end workflow for performance-testing a website with k6: Step 1 (the most important), elicit real user workflows from the user — the skill stops rather than guessing. Then scaffold the project, record each workflow with Playwright into a HAR, convert to k6 protocol scripts, and build functional tests that must be green before any load testing. Next, design SLO-backed thresholds (global, per-endpoint tagged, per-iteration, Web Vitals LCP/INP/CLS), and build hybrid load tests — a protocol scenario driving load plus one browser VU measuring Web Vitals under load — for smoke, average, stress, spike, soak and breakpoint. A load-generator monitor sidecar guards against "the laptop is the bottleneck" false readings; cloud runs dispatch to Grafana Cloud k6; the backend is investigated via Grafana (RED metrics, logs, traces, Pyroscope) only when the user owns it; everything lands in a structured Markdown report. Hard opinions: always monitor the load generator, local for validation / cloud for scale, no shared test libs. Honest caveats: toolchain prerequisites — k6 ≥ 2.0, Node.js 20+, Playwright with Chromium, har-to-k6; Grafana Cloud k6 runs are billed (browser VU-hours cost 10× protocol VU-hours — check limits before soak/breakpoint); only ever load-test sites you own or have explicit permission to test. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: k6 ≥ 2.0, Node.js ≥ 20, Playwright with Chromium installed, har-to-k6; a website you own or have explicit permission to load-test; optional Grafana Cloud account for cloud-scale runs (billed — browser VU-hours cost 10× protocol VU-hours) Install "End-to-end k6 performance testing for websites, with Grafana backend investigation" for me. It teaches my agent @grafana's k6 workflow: elicit real user workflows first (never guess), scaffold the project, record workflows with Playwright and convert the HAR to k6 scripts, build functional tests that must pass before load testing, design SLO-backed thresholds with Web Vitals, build hybrid protocol+browser load tests (smoke/average/stress/spike/soak/breakpoint), run locally with the load-generator monitor sidecar, push to Grafana Cloud k6 for cloud-scale types, investigate the backend in Grafana if owned, and deliver a structured report. Apache-2.0 licensed. Repository: https://github.com/grafana/skills/blob/main/skills/grafana-k6/k6-perf-test-website/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "k6-perf-test-website". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. verify k6 ≥ 2.0, Node 20 and Playwright/Chromium are installed; log in to Grafana Cloud k6 if I want cloud runs; confirm which workflows to test and which site — load-test only what I own or have permission to test). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.