perf-onboarding

Bootstraps a gated k6 performance test suite from zero through seven enforced phases.

5|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/civitas-cerebrum/achilles --skill perf-onboarding-civitas-cerebrum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-onboarding
Source: https://github.com/civitas-cerebrum/achilles/tree/main/skills/perf-onboarding
Command: npx skills add https://github.com/civitas-cerebrum/achilles --skill perf-onboarding-civitas-cerebrum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires k6, and includes references (resource) components.

What problem does it solve? Setting up a performance testing pipeline from scratch involves scaffolding k6 helpers, discovering endpoints, authoring scenarios, running baselines and load passes, and gating results against SLOs — a process that is easy to leave half-finished. This Skill orchestrates that entire lifecycle autonomously, with reviewer-gated phase transitions and hard safety ceilings so no step is skipped. ## Core Features & Use Cases - Seven-phase pipeline: Scaffold, Readiness, Scenario-model, Baseline, Load-run, Threshold-gate, and Report, each with explicit deliverables, exit criteria, and reviewer approval before advancing. - Derive-or-bootstrap readiness probe: Reuses journey maps and HAR captures from prior functional onboarding when available, or falls back to crawler/OpenAPI endpoint discovery. - Enforced safety model: Hard ceilings of 1000 VUs and 3600 seconds per run, origin allowlisting, and explicit opt-in required before any production load testing. - Threshold enforcement proof: A mandatory deliberate-breach test proves k6 thresholds actually fail builds before SLO verdicts are trusted. - Use Case: Point the Skill at a staging origin and receive a maintained perf suite with scenario scripts, baselines, load/stress/spike/soak results, SLO verdicts, and a stakeholder-readable report. ## Quick Start Ask the agent to perf-onboard your project against your staging URL, for example by saying "perf-onboard https://staging.example.com". ## Quick Start Invoke the skill with a target origin such as "perf-onboard https://staging.example.com" and the pipeline runs all seven phases autonomously.

Frequently Asked Questions about perf-onboarding

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

FAQPage Schema
How do I set up k6 load testing for a web app from scratch?

Invoke the perf-onboarding skill with a target origin and it scaffolds k6 helper libraries, discovers or derives scenarios, writes scripts, runs baselines and load passes, and produces a report. The seven-phase pipeline runs autonomously with reviewer gates between phases.

How does the skill decide which endpoints to load test?

A readiness probe checks for a sentinel-bearing journey map and a HAR captures manifest. If both exist it derives scenarios from journey priority tiers; otherwise it bootstraps by crawling the origin, parsing an OpenAPI spec, or accepting a manual endpoint list.

Can I run load tests against production with k6?

Production load testing requires two deliberate manual steps: adding the production origin to the targets allowlist and setting production.allowed to true in the config. The safety gate denies production runs otherwise and never prompts for opt-in mid-run.

What safety limits does the load test pipeline enforce?

A Bash-boundary gate enforces a hard ceiling of 1000 virtual users and 3600 seconds per run, regardless of config values. It also restricts load tests to allowlisted origins and blocks all k6 runs until the scaffold phase completes.

How do I verify k6 thresholds actually fail the build?

Phase 6 runs a mandatory deliberate-breach proof: it temporarily mutates one threshold to an impossible value, confirms k6 exits non-zero, then reverts. The write gate rejects the threshold verdict file if this proof is missing.

How do I resume an interrupted performance onboarding run?

Read the status ledger at tests/perf/docs/perf-onboarding-status.json to find the last completed phase and current sub-stage. Each phase is independently runnable once its predecessor's deliverables exist on disk.