CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/perf-budget-gate

Builds a unified release-readiness gate that aggregates verdicts from any combination of k6 / JMeter / Gatling / Locust load runners and Lighthouse CI Web Vitals, applies severity-aware pass/fail thresholds, and emits a single go / no-go decision with per-metric deltas vs the main-branch baseline. Posts the delta as a PR comment when the team has the integration set up. Use when authoring a CI step that gates a deployment on cross-runner perf compatibility.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, actionable, and uses progressive disclosure effectively with a real reference file. The main gap is missing validation checkpoints in the workflow for a batch aggregation, plus a worked example that diverges slightly from the stated decision rule.

Suggestions

Add an explicit validation checkpoint in the How-to-use workflow (e.g. 'verify each runner artifact exists and parsed before applying the gate; fail fast with a clear error if a required artifact or the main baseline is missing').

Reconcile the worked example with the decision rule: have run_perf_gate.py compute delta_pct against a fetched baseline and apply the regression/warn thresholds, rather than only blocking on status==fail.

Collapse the duplicated gate logic so the worked example imports or mirrors gate_decision rather than re-implementing a simpler variant.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no padding about what k6 or Lighthouse are), but the gate logic is implemented twice — conceptually in gate_decision and again in the worked example — which could be tightened.

4 / 5

Actionability

Provides executable code (run_perf_gate.py), a concrete metric-record schema, and a markdown artifact template, but the worked example omits delta_pct regression handling and baseline fetching that the stated decision rule requires, leaving a minor gap.

4 / 5

Workflow Clarity

The five-step How-to-use sequence is clearly ordered with an explicit non-zero exit on no-go, but the workflow lacks validation checkpoints (e.g. confirm each artifact exists/parsed, baseline present) for a batch aggregation across multiple runners, which caps this dimension.

3 / 5

Progressive Disclosure

The body is a well-signaled overview that defers deep material (per-runner source map, full CI wiring, per-metric budgets) to a real one-level-deep reference, references/ci-wiring-and-metric-sources.md, linked clearly and verified to exist.

5 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive, clearly stating both what the skill does and when to use it. The only mild weakness is a trigger phrase that leans technical rather than colloquial.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'aggregates verdicts', 'applies severity-aware pass/fail thresholds', 'emits a single go / no-go decision with per-metric deltas', 'Posts the delta as a PR comment' — with comprehensive coverage of the gate's behavior.

5 / 5

Completeness

Explicitly answers both what (builds/aggregate/apply/emit/post) and when ('Use when authoring a CI step that gates a deployment on cross-runner perf compatibility') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Strong keyword coverage including tool names (k6 / JMeter / Gatling / Locust), 'Lighthouse CI Web Vitals', 'perf', and 'go / no-go', but the trigger phrase 'authoring a CI step that gates a deployment on cross-runner perf compatibility' is more technical than the natural phrasing a user would say.

4 / 5

Distinctiveness Conflict Risk

Clear niche — a cross-runner perf compatibility release-readiness gate — with distinct triggers tied to specific load runners and Web Vitals, minimizing overlap with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents