← Search

End-to-end k6 performance testing for websites, with Grafana backend investigation
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 1ccacf2
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: k6 ≥ 2.0, Node.js ≥ 20…

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

At a glance
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.

Version:

Quick answer

End-to-end k6 performance testing is a free Muse skill, the Grafana end-to-end workflow for performance-testing a website with k6: first, elicit user workflows from the user, since 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 tests that must be green before load testing.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 1ccacf2

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/grafana/skills/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-k6/k6-perf-test-website/SKILL.md Pinned version: install the code at commit 1ccacf29049fde66637fe01ab93a83a772da323b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 1ccacf2 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
1ccacf2 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.