performance

Diagnose React runtime performance with React Doctor traces, live render outlines, Long Animation Frames, interaction timing, and component render evidence. Use when invoked as `/performance` for a slow interaction, unexpected re-renders, or a measured before-and-after comparison.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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 tight, well-sequenced workflow with executable commands, an evidence-based report structure, and explicit validation loops. It assumes Claude's competence and avoids padding; the only soft spot is a couple of high-level steps that lack executable specificity.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — it never explains React or tracing basics Claude already knows, and every section (interpretation rules, report template, validation steps) earns its tokens.	5 / 5
Actionability	Provides copy-paste-ready commands (npx react-doctor scan, CDP invocation) and a concrete report template, but a few steps like 'Search the repository' and 'Open the DevTools trace' remain high-level rather than executable.	4 / 5
Workflow Clarity	A clear six-phase sequence (define → record → read → connect → report → validate) with an explicit ordered checklist for reading the report and a feedback loop in the 'Validate a fix' section (rebuild, re-record, 3 before/3 after samples, compare medians).	5 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, and appropriately self-contained with no bundle files; minor gap is that the interpretation rules or report template could optionally live in a reference file to keep the overview shorter.	4 / 5
	Total	18 / 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 strong: it states concrete capabilities, provides explicit trigger guidance in third person, and occupies a distinct niche. The only minor gap is a few additional natural synonyms a user might say.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete mechanisms — React Doctor traces, live render outlines, Long Animation Frames, interaction timing, and component render evidence — giving comprehensive coverage of what the skill does rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' (diagnose React runtime performance with named signals) and 'when' (a concrete 'Use when invoked as /performance for...' clause with specific trigger scenarios).	5 / 5
Trigger Term Quality	Natural trigger phrases ('slow interaction', 'unexpected re-renders', 'measured before-and-after comparison', '/performance') match what users would say, though a few common synonyms like 'jank' or 'frame drops' are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (React runtime performance via React Doctor) with distinct triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: millionco/react-doctor
Path: skills/performance/SKILL.md
Commit: 83466a8

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.