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.

75

Quality

94%

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

87%

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

A well-structured, highly actionable skill body with executable code, a concrete record schema, and clean one-level-deep progressive disclosure. The main gap is workflow clarity: the numbered steps lack explicit validation checkpoints and error-recovery feedback for batch failure modes like missing artifacts or baselines.

Suggestions

Add explicit validation checkpoints to 'How to use' — e.g., fail fast with a clear message if a required runner artifact or the last-green main-branch baseline is missing before flattening records.

Make the worked example reuse gate_decision() (or at least apply the regression/warn triggers and delta computation) so the runnable script matches the full decision rule rather than only checking budget breaches.

Add a short feedback loop for the no-go path — e.g., on a no-go verdict, surface the offending records and the baseline diff so the CI failure is triageable without re-running the gate.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains what k6/Lighthouse/Web Vitals/CI are — and every section (overview, when-to-use, how-to-use, record schema, decision rule, artifact format, worked example, anti-patterns, references) earns its place without concept-explaining padding.

3 / 3

Actionability

Provides fully executable code — a complete gate_decision() function and a runnable run_perf_gate.py parsing real k6/Lighthouse artifacts — plus a concrete JSON record shape, field source table, and a markdown summary template, all copy-paste ready.

3 / 3

Workflow Clarity

The 'How to use' section gives a clear 5-step sequence, but validation checkpoints are only implicit (the final gate verdict) and there is no error-recovery/feedback loop for batch failure modes such as a missing runner artifact or absent main-branch baseline, which the rubric flags for batch operations.

2 / 3

Progressive Disclosure

SKILL.md is a well-organized overview with a real, one-level-deep bundle file (references/ci-wiring-and-metric-sources.md) signaled clearly in multiple places and a closing References section; deep CI wiring is appropriately split out rather than inlined.

3 / 3

Total

11

/

12

Passed

Description

100%

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

A strong, third-person description that states concrete capabilities, names the relevant tools, and gives an explicit 'Use when' trigger with a clear niche distinct from sibling gates. No vague fluff or over-claims; nothing materially weak to flag.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'aggregates verdicts from any combination of k6 / JMeter / Gatling / Locust... and Lighthouse CI', 'applies severity-aware pass/fail thresholds', 'emits a single go / no-go decision with per-metric deltas', 'Posts the delta as a PR comment' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (builds the gate, aggregates verdicts, applies thresholds, emits decision, posts PR comment) and 'when' via an explicit 'Use when...' clause, matching the top anchor.

3 / 3

Trigger Term Quality

The trigger 'Use when authoring a CI step that gates a deployment on cross-runner perf compatibility' plus named tools (k6, JMeter, Gatling, Locust, Lighthouse) and natural terms ('perf', 'CI step', 'gates a deployment', 'go / no-go') give good coverage of phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear niche — a multi-runner perf budget gate — with distinct triggers and an explicit contrast to sibling gates (data-quality-gate, visual-baseline-gate, contract-compatibility-gate), making wrong-skill conflicts unlikely.

3 / 3

Total

12

/

12

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