performance

MUST be used whenever fixing performance issues in a Flows app. This skill finds AND fixes performance problems — re-renders, inefficient queries, missing pagination, unbounded fetches, large bundles, and memory leaks. It does not just report them. Always measure before and after. Triggers: performance, slow, laggy, optimize, re-render, bundle size, load time, CDF query, large list, memory leak, debounce, virtualize, lazy load, code split.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A highly actionable, well-sequenced performance workflow with concrete code and a measure-before/after validation loop. Its weaknesses are length/repetition across steps and a lack of progressive disclosure — the monolithic body keeps detail inline rather than splitting it into reference files.

Suggestions

Move the larger BAD/FIX reference tables and code patterns (e.g. DMS query rewriting, bundle-size fixes) into separate reference files and link to them from the main steps to reduce inline length.

De-duplicate repeated guidance (staleTime 30_000, 'Add limit: 100', shared-hook extraction) into a single canonical mention referenced from each step.

Either create the referenced 'semantic-knowledge/' directory or remove the conditional 'if available' pointer so navigation signals point to real, clearly-signaled references.

Dimension	Reasoning	Score
Conciseness	The ~500-line body avoids explaining basic concepts but repeats similar guidance across steps (staleTime 30_000, 'Add limit', BAD/FIX patterns), so it is mostly efficient yet could be tightened; not 3 due to length and redundancy, not 1 since it does not pad with known concepts.	2 / 3
Actionability	Provides concrete grep commands and copy-paste-ready executable code (useMemo/useCallback, useInfiniteQuery, useVirtualizer, AbortController, lodash-es), matching the fully-executable anchor.	3 / 3
Workflow Clarity	Clear 11-step sequence with an explicit validation feedback loop (Step 1 baseline measurement, Step 11 'Re-run...report the delta' and 'Do not fabricate numbers'), so the destructive/batch cap at 2 does not apply.	3 / 3
Progressive Disclosure	No bundle files exist and the 500-line body is monolithic with all detail inline; the single reference to a non-existent 'semantic-knowledge/' directory is conditional and weak, so it has structure but content that should be separate is inline. Not 3 (the under-50-line exception does not apply), not 1 because the step sections are well organized.	2 / 3
	Total	10 / 12 Passed

Description

92%

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, specific description that concretely states capabilities and provides explicit trigger guidance for both what and when. Its main weakness is a broad, partly-generic trigger list that could cause overlap with general performance skills despite the Flows/CDF scoping.

Suggestions

Tie more trigger terms to the Flows/CDF domain (e.g. 'CDF re-render', 'Flows slow table') to reduce overlap with generic React/web performance skills.

Lead with the Flows/CDF scope in the trigger clause so the generic terms (slow, laggy, optimize) are read as domain-scoped rather than universal.

Consider trimming near-synonym triggers (e.g. 'slow' vs 'laggy') to sharpen distinctiveness without losing natural coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('re-renders, inefficient queries, missing pagination, unbounded fetches, large bundles, and memory leaks') plus 'Always measure before and after', matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Clearly answers both what ('finds AND fixes performance problems...') and when ('MUST be used whenever fixing performance issues in a Flows app' plus an explicit Triggers list), so the missing-trigger cap at 2 does not apply.	3 / 3
Trigger Term Quality	The explicit 'Triggers:' list covers natural terms users say ('slow', 'laggy', 'optimize', 're-render', 'bundle size', 'load time', 'memory leak', 'lazy load', 'code split'), giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The 'Flows app'/'CDF query' framing gives a niche, but most trigger terms (slow, laggy, optimize, re-render, bundle size) are generic and would overlap with a general performance skill; not 1 because of the domain scoping, not 3 because of the broad generic triggers.	2 / 3
	Total	11 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (526 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	13 / 16 Passed

Repository: cognitedata/builder-skills
Commit: ab7b5f8

Reviewed: 1 day 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.