learn-via-k6-docs
Skill1 starsChanged 3 months agoMITView on GitHub
Type: skill (grounded model narration) · Used by: perf-author · Status: STUB (P0 scaffold — not yet implemented) - Input: an API/feature question from the script-author step (e.g. how to set thresholds, use scenarios, configure outputs). - Output: the verified k6 v2 API shape and usage, pulled from the docs. Never invent or recall APIs from memory — every API used must trace back to a docs lookup. This is the anti-hallucination spine.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- k6-browser-testSkill
- k6-load-testSkill
- k6-playwright-converterSkill
- k6-smoke-testSkill
- k6-test-plannerSkill
- apply-ws2-conventionsSkill
- author-resilient-playwrightSkill
- build-status-viewsSkill
- choose-k6-execution-modeSkill
- compare-coreSkill
- compare-to-baselineSkill
- corroborate-2-sourcesSkill
- curate-baselinesSkill
- doc-consistency-checkSkill
- emit-otlp-and-prometheusSkill
- estimate-token-costSkill
- explore-product-structureSkill
- file-perf-regression-jiraSkill
- func-verdictSkill
- heal-playwright-suiteSkill
- k6-profile-benchmarkSkill
- k6-profile-loadSkill
- k6-profile-soakSkill
- k6-profile-spikeSkill
- k6-profile-stressSkill
- link-grafana-panelSkill
- notify-responsible-teamSkill
- open-draft-prSkill
- parse-k6-json-summarySkill
- parse-playwright-summarySkill
- perf-run-logSkill
- run-k6-scriptSkill
- run-ledgerSkill
- run-playwright-suiteSkill
- scope-reviewSkill
- scrub-har-secretsSkill
- triage-func-verdictSkill
- triage-perf-verdictSkill
- verify-k6-scriptSkill
- verify-playwright-suiteSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Never invent or recall APIs from memory — every API used must trace back to a docs lookup.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
learn-via-k6-docs
Look up correct k6 v2 APIs — the anti-hallucination spine for script authoring.
Type: skill (grounded model narration) · Used by: perf-author · Status: STUB (P0 scaffold — not yet implemented)
Prompt
Ground all script authoring in real k6 v2 APIs by querying k6 x docs.
- Input: an API/feature question from the script-author step (e.g. how to set thresholds, use scenarios, configure outputs).
- Output: the verified k6 v2 API shape and usage, pulled from the docs.
Never invent or recall APIs from memory — every API used must trace back to a docs lookup. This is the anti-hallucination spine.
Tools
k6 x docs MCP
Data
none
Notes
Activation: P4. Grounded model helper. Hard rule: no API may be used in an
authored script unless it was confirmed via k6 x docs here — recall is not a
source of truth.
Frozen skill registry: AGENTS.md in this repo
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.