CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

profile-optimizer

Analyzes React Profiler exports, Chrome Performance traces, and heap snapshots to find the highest-impact CPU and memory bottlenecks and propose fixes ranked by measured impact. Invoke with /profile-optimizer for "why is this slow", "memory leak", or "analyze profile".

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 body is a well-written orchestrator with an exemplary gated workflow, concrete thresholds, and lean tables. Its fatal flaw is that the bundle does not back it: all rule files and the report template referenced by every phase are missing, so the skill's detailed methodology is unreachable as shipped.

Suggestions

Add the eight missing bundle files (rules/input-detection.md, rules/measurement-methodology.md, rules/react-profile-analysis.md, rules/chrome-trace-analysis.md, rules/heap-snapshot-analysis.md, rules/optimization-playbook.md, rules/confidence-loop.md, templates/analysis-report.md) or inline their essential content — the Workflow, Required-reading, and Memory-quickstart sections currently point at files that don't exist.

Merge the Workflow table and the "Required reading by phase" table into one table with columns for rule file and gate; the same phase-to-file mapping is currently listed three times (also in the confidence section).

For the CPU path, add one inline fallback command (like the heap-summary/heap-diff commands) so profile analysis is not entirely blocked by the missing rule files — e.g., a jq or node one-liner for top self-time functions from a trace.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basic-concept explanations, tables for input formats and phases, concrete anti-pattern one-liners. Not a 5 because the phase-to-rule-file mapping is repeated across three sections (Workflow table, Required-reading table, Confidence-gated iteration), which could be consolidated.

4 / 5

Actionability

Gives concrete executable commands for the memory path ("node --max-old-space-size=4096 <skill_dir>/scripts/heap-summary.mjs <snapshot.heapsnapshot>"), a concrete skill invocation (Skill(skill="confidence", args="analysis")), and actionable detection signals ("Top-level traceEvents array"). Not a 5 because the CPU-path analysis steps are delegated to rule files that don't exist in the bundle, so the guidance stops at pointers there.

4 / 5

Workflow Clarity

Six clearly sequenced phases each with an explicit gate ("Do not skip a gate"), a validation feedback loop with concrete thresholds ("≥ 90%" proceed, "70–89%" one deeper pass, "< 70%" surface to user, max two deep-dives), and a Definition of Done checklist. This matches the anchor-5 example of sequence + explicit validation + feedback loops + checklist.

5 / 5

Progressive Disclosure

Signaling is excellent — every phase maps to named rule files with "Load on demand — do not preload" — but scoring against the actual bundle, 8 of the 10 referenced files (all of rules/*.md and templates/analysis-report.md, which carry phases 0–5) do not exist. The thin-orchestrator structure is not actually realized: navigation leads to dead ends for the core content, which is neither inline nor in the bundle.

2 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description that clearly states what the skill does and gives explicit, natural trigger phrases for when to invoke it. Minor gaps: missing file-extension/synonym triggers and a slightly generic "why is this slow" trigger that overlaps with general performance skills.

DimensionReasoningScore

Specificity

Lists several specific actions across a clearly named domain — "Analyzes React Profiler exports, Chrome Performance traces, and heap snapshots", "find the highest-impact CPU and memory bottlenecks and propose fixes ranked by measured impact". Not a 5 because it omits parts of the skill's stated scope (multi-format correlation, snapshot diffing for leak detection, report generation), leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both questions: the "what" ("Analyzes... to find the highest-impact CPU and memory bottlenecks and propose fixes ranked by measured impact") and the "when" with concrete trigger phrases ("Invoke with /profile-optimizer for 'why is this slow', 'memory leak', or 'analyze profile'"). This matches the anchor-5 example structure of what + explicit 'Use when' guidance with trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases — "why is this slow", "memory leak", "analyze profile" — plus concrete domain terms (React Profiler, Chrome Performance traces, heap snapshots). Not a 5 because it lacks file-extension triggers (.cpuprofile, .heapsnapshot) and common synonyms (flamegraph, long task, INP) that the frontmatter tags show the skill targets.

4 / 5

Distinctiveness Conflict Risk

Clear niche — profile-file-driven React/Chrome performance analysis — with distinct triggers like "memory leak" and "analyze profile". Not a 5 because "why is this slow" is a generic performance complaint that would also match general performance-tuning skills, leaving minor overlap risk with closely related skills.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 22 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/analysis/profile-optimizer/SKILL.md

Reviewed

Table of Contents

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.