Individual skill
k6-manage
Interact with Grafana Cloud k6 (GCk6) — manage load tests, test runs, scripts, projects, schedules, env vars, fetch metrics or logs, and run scripts locally — using the `gcx` CLI (or direct curl when gcx is unavailable). Use this skill whenever the user mentions a k6 cloud test or run, asks to list/edit/create/start/abort k6 load tests, wants to fetch logs or metrics for a test run, manage k6 project limits or schedules, run a k6 script locally or via `k6 cloud run`, or needs to call any `/cloud/v6/`, `/cloud/v5/`, or k6-app Loki endpoint against a Grafana Cloud stack. Trigger even when the user doesn't explicitly say "gcx" or "API" — phrases like "why did my k6 test fail", "show me logs for run X", "bump VUh limit on project Y", or "update my k6 script" all qualify.
skills/grafana-k6/k6-manage/SKILL.md
Source commit 8fb72a527961f05e708f53d2a0500709e12d7970
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 307
- Repository last updated
- Nov 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesSKILL.mdcore · 47,408 bytesreferences/metrics.mddoc · 14,093 bytes
Read excerpt
# Grafana Cloud k6 — interaction reference
The default path is the `gcx` CLI. When gcx isn't installed, every
endpoint here is still reachable via direct curl against k6's public
hosts — see §1.2 for the auth-header and host-translation rules. Two
principles shape the rest:
- **gcx owns Grafana-side auth (when present).** It injects the right
headers on every call, so you should not set auth headers yourself.
The only header you ever set by hand is `X-K6TestRun-Id`, on Loki
log queries (§4), browser screenshot/file fetches (§6), and Tempo
trace queries (§7) — anything else gets overwritten or causes
conflicts. In curl mode the auth headers are manual; see §1.2.
- **Reach for `gcx k6 ...` subcommands first.** They wrap the common