k6 documentation: write and review docs across the three k6 repos
Write or review k6 docs (user docs, TypeScript types, release notes) with style conventions and mandatory example validation
- What
- Write or review k6 docs (user docs, TypeScript types, release notes) with style conventions and mandatory example validation
- Cost
- Free
- Needs
- nothing to install — the skill is a documentation workflow your agent follows; local clones of the k6, k6-docs and k6-DefinitelyTyped repos plus a working k6 build from master are needed for the full example-validation workflow
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @grafana's skill for writing and reviewing k6 documentation across three repositories: k6-DefinitelyTyped (TypeScript types), k6-docs (user documentation) and k6 (release notes/changelog). Pick the write or review workflow, lean on the quick-reference guides (repo structure, TypeScript patterns, parallel-subagent testing workflow, agent-browser reference, troubleshooting), and follow strict critical rules: never push without asking, never chain commands with `&&` or `;`, only document user-facing features, `1.` for every numbered list item, every code example executed cleanly against k6@master before committing, and no AI attribution in commits. Honest caveats: k6-specific — only useful if you contribute to the k6 ecosystem; the full workflow expects local clones of all three repos and a working k6 build from master, which is heavyweight for a casual contributor. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
k6 documentation is a free Muse skill, the Grafana skill for writing and reviewing k6 documentation across three repositories: k6-DefinitelyTyped for TypeScript types, k6-docs for user documentation, and k6 for release notes and changelog. Pick the write or review workflow, lean on the guides for repo structure, TypeScript patterns, and troubleshooting, and follow critical rules, including never pushing without asking.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 1ccacf2Step 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: nothing to install — the skill is a documentation workflow your agent follows; local clones of the k6, k6-docs and k6-DefinitelyTyped repos plus a working k6 build from master are needed for the full example-validation workflow Install "k6 documentation: write and review docs across the three k6 repos" for me. It gives my agent @grafana's k6 docs workflow: pick the write or review path, apply k6 doc style conventions, draft TypeScript type definitions and release notes, and validate every code example by running it against k6@master before committing — with strict critical rules (never push without asking, run each command separately, user-facing features only, no AI attribution in commits). Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/grafana/skills/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-k6/k6-docs/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-docs". 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. clone the three k6 repos and build k6 from master myself for example validation). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
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.