k6 documentation: write and review docs across the three k6 repos

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://github.com/grafana/skills/blob/main/skills/grafana-k6/k6-docs/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-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.