validating-performance-budgets

Validate application performance against defined budgets to identify regressions early. Use when checking page load times, bundle sizes, or API response times against thresholds. Trigger with phrases like "validate performance budget", "check performance metrics", or "detect performance regression".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

62%Weight 40%Scale 1-3

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-organized with a clear overview and sequenced workflow, but it stays at an abstract level: it restates concepts Claude already knows and never connects to the bundled executable scripts. Adding concrete invocations and a validate-then-proceed checkpoint would lift the weakest dimensions.

Suggestions

Replace the abstract 'Instructions' list with concrete executable commands for the bundled scripts, e.g. `python scripts/validate_budget.py --budget performance-budgets.json --metrics metrics.json`.

Trim the 'Best Practices', 'Integration', and 'Overview' sections that restate the description; keep only guidance Claude would not already infer.

Add a validation checkpoint/feedback loop (e.g. run validation, review violations, remediate, re-validate until passing) and explicitly link to scripts/validate_budget.py, scripts/create_budget.py, and scripts/report_violation.py so the bundle is discoverable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient prose but pads with explanatory restatements Claude already infers ('It helps identify performance regressions and ensures your application maintains optimal performance characteristics') and generic 'Best Practices'/'Integration' sections that restate the description rather than add new, actionable information.	2 / 3
Actionability	It lists steps and names bundled scripts in the README, but the body itself gives no executable commands, no code examples, and no invocation syntax for the existing validate_budget.py/create_budget.py/report_violation.py scripts — guidance describes rather than instructs.	2 / 3
Workflow Clarity	The numbered 'Instructions' (load budget, collect metrics, compare, identify violations, generate report, remediate) sequence the process, but there are no validation checkpoints or feedback loops, and the rubric caps workflow clarity at 2 when validation/verification steps are missing in batch-style operations.	2 / 3
Progressive Disclosure	Bundle scripts exist (validate_budget.py, create_budget.py, report_violation.py) but the body never references or signals them, and the config path uses an unexplained ${CLAUDE_SKILL_DIR}/performance-budgets.json placeholder; structure is present but navigation to the bundled assets is not clearly signaled.	2 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong: it states concrete capabilities, gives an explicit 'Use when' clause, and lists natural trigger phrases with specific performance metrics. It is concise, third-person, and clearly scoped to performance budget validation with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and metrics — 'Validate application performance against defined budgets', 'checking page load times, bundle sizes, or API response times against thresholds' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers what it does and when to use it via a clear 'Use when...' clause plus enumerated trigger phrases, satisfying the 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ('validate performance budget', 'check performance metrics', 'detect performance regression') plus concrete metric keywords, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The narrow performance-budget niche with specific metric triggers (page load, bundle size, API response time) is clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/performance/performance-budget-validator/skills/validating-performance-budgets/SKILL.md
Commit: c4eafaf

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.