providing-performance-optimization-advice

Produce a prioritized performance-optimization roadmap across frontend, backend, and infrastructure. Use as an explicit/manual helper after bottlenecks are known or suspected, not as the owner of regression detection, profiling capture, or test execution.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/providing-performance-optimization-advice/SKILL.md

Quality

Content

65%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 body is concise and well-structured with clear boundaries and related-skill pointers, but it lacks an executable procedure or sequenced workflow and fails to connect to the bundled reference, script, and asset files that would make the guidance actionable.

Suggestions

Add a short numbered workflow (identify bottlenecks -> rank by impact/effort -> propose validation) with an explicit validation checkpoint to raise workflow clarity.

Link the bundled scripts (e.g., performance_profiler.py, impact_estimator.py) and reference docs from the body so progressive disclosure is one level deep and clearly signaled.

Provide at least one concrete example of an output artifact (e.g., a sample ranked backlog row) to move actionability toward executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned with no padding or explanation of concepts Claude already knows; every section (Positioning, When to Use, Boundaries, Outputs, Related) earns its place, matching the level-3 anchor.	3 / 3
Actionability	It names output shapes ('ranked optimization backlog by impact and effort', 'concrete hotspots by layer') and layers, but gives no concrete procedure, commands, or method for producing the roadmap, falling into the level-2 anchor of some concrete guidance but incomplete.	2 / 3
Workflow Clarity	There is no sequenced multi-step workflow or validation checkpoint; 'Typical Outputs' lists artifacts but not a sequence, matching the level-2 anchor of steps/outputs listed but checkpoints missing or implicit rather than the level-3 explicit validate-fix-retry loop.	2 / 3
Progressive Disclosure	The body is well-organized into sections, but a substantial bundle (5 reference docs, 3 scripts, 3 assets) exists and the body references none of it, matching the level-2 anchor of structure present but references not clearly signaled.	2 / 3
	Total	9 / 12 Passed

Description

75%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 clearly states what the skill does and when to use it, with strong boundary-setting that distinguishes it from related performance skills. It is slightly weakened by a single-action specificity and somewhat technical trigger terms rather than natural user phrasings.

Suggestions

Add concrete verbs for multiple actions (e.g., 'rank bottlenecks, estimate effort, propose validation steps') to lift specificity toward level 3.

Include natural user phrasings such as 'speed up', 'slow load times', or 'optimize performance' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('frontend, backend, and infrastructure') and a concrete action ('Produce a prioritized performance-optimization roadmap'), but offers only a single primary action rather than the multiple specific concrete actions the level-3 anchor requires.	2 / 3
Completeness	It answers both 'what' ('Produce a prioritized performance-optimization roadmap...') and 'when' via an explicit 'Use as an explicit/manual helper after bottlenecks are known or suspected' clause, satisfying the level-3 anchor for explicit trigger guidance.	3 / 3
Trigger Term Quality	Relevant terms like 'performance-optimization roadmap' and 'bottlenecks' appear, but common natural phrasings users would actually say (e.g., 'speed up', 'slow', 'optimize') are missing, matching the level-2 anchor of some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	The negative boundary 'not as the owner of regression detection, profiling capture, or test execution' carves out a clear niche against neighboring skills, matching the level-3 anchor of a distinct niche unlikely to conflict.	3 / 3
	Total	10 / 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: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/providing-performance-optimization-advice/SKILL.md
Commit: f627ab5

Reviewed: 8 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.