k6-docs

Review k6 documentation changes across TypeScript types, docs, and release notes.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill k6-docs-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k6-docs
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/k6-docs
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill k6-docs-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents broken, outdated, or unverified k6 documentation by guiding updates across k6-DefinitelyTyped types, k6 user docs, and k6 release notes with consistent checks.

Core Features & Use Cases

  • Docs writing and reviewing workflows: Use the dedicated write and review procedures to update documentation with the correct scope across TypeScript types, user-facing pages, and release notes.
  • Visual verification support: Validate documentation rendering using agent-browser screenshots and accessibility snapshots, with curl as a fallback for HTTP status checks.
  • Link and example correctness: Enforce link validation against the locally served docs and require running k6 examples on k6@master to ensure snippets are truly runnable.

Quick Start

Ask the AI to review documentation changes for a specific k6 feature across the types repository, user docs site, and release notes, including link validation, visual checks, and running all runnable examples on k6@master.

Frequently Asked Questions about k6-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify k6 documentation changes across TypeScript types and release notes?

Verify k6 documentation changes by applying stepwise workflows that check TypeScript definitions, user-facing pages, and release notes. This ensures updates remain correct, runnable, and visually verified across all k6 documentation components.

What is the best way to validate links and run examples in k6 documentation?

Validate k6 documentation links against locally served docs and require running k6 examples on k6@master. This enforces link correctness and guarantees documentation code snippets are truly runnable.

Can I use agent-browser screenshots for visual verification of k6 docs?

Yes, use agent-browser screenshots and accessibility snapshots to validate k6 documentation rendering. Curl serves as a fallback for HTTP status checks when browser-based visual verification is unavailable.

How do I review new TypeScript definitions for k6 features?

Review new k6 TypeScript definitions using dedicated write and review procedures. These workflows ensure DefinitelyTyped types match user-facing documentation pages and release notes for specific k6 features.

Does k6 documentation testing require running examples on k6@master?

Yes, k6 documentation testing requires running all runnable examples on k6@master to ensure snippets are truly executable. Parallel example execution verifies correctness across documentation updates.