CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

1k-performance

Performance optimization for React/React Native — re-renders, memoization, FlashList, memory leaks, and bundle size.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-performance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A strongly actionable, well-structured skill body: every command, knob, and code sample is executable and the bundle reference is real, clearly signaled, and one level deep. The main cost is token efficiency — the render-baseline section inlines methodology detail that the skill itself defers to file header comments, and the topic list duplicates the reference's own structure.

Suggestions

Trim the Account Selector Render Baseline section to the commands, the gate thresholds, the failure-vs-warning distinction, and a pointer to the e2e files' header comments, moving the ABBA/MAD/IQR and harness-hashing methodology detail out of SKILL.md.

Cut the 9-bullet 'Topics covered' list (or reduce it to 2-3 headline topics) since the reference file's own headers already serve as its table of contents.

Consider replacing the full executeBatched implementation with the one-line rule plus a 3-4 line minimal example, keeping the 'limit to 3-5' guidance that Claude could not infer.

DimensionReasoningScore

Conciseness

Mostly efficient and consistently repo-specific, but several sections could be tightened: the ~60-line render-baseline methodology prose (ABBA/BAAB schedule, MAD/IQR aggregation, harness SHA-256 hashing) duplicates what the body itself says lives in the e2e files' header comments; the 9-bullet 'Topics covered' list restates the reference file's own table of contents; and the 17-line executeBatched implementation elaborates a pattern derivable from the one-line rule. This matches anchor 3 ('could be tightened') rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Fully executable throughout: copy-paste-ready yarn commands with all variants (:trend, :quick, :scale), fast deterministic checks, environment knobs with defaults and ranges, a complete runnable executeBatched TypeScript implementation, exact primary-file paths, and the output location (.tmp/render-baseline/). Matches anchor 5: specific examples cover the common cases.

5 / 5

Workflow Clarity

Validation checkpoints are explicit: the 'Before running:' pre-flight checklist, the 1.3x regression gate with failure-vs-warning classification, and the rule 'do not claim a small optimization when the result is inconclusive'. Falls short of anchor 5 because the run-interpret-act sequence is never laid out as an ordered workflow and there is no explicit feedback loop for what to do when the gate fails; above anchor 3 because checkpoints are stated, not implicit.

4 / 5

Progressive Disclosure

A single one-level-deep reference (references/rules/performance.md) is clearly signaled with a topic list whose entries match the file's actual section headers, and inline rules are kept short with bulk detail in the reference. Falls short of anchor 5 because the inlined render-baseline methodology exceeds an overview's role when the authoritative methodology already lives in the e2e files' header comments, a minor organization gap matching anchor 4.

4 / 5

Total

16

/

20

Passed

Description

66%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 specific, well-scoped description with good natural trigger terms for the React performance domain. Its main weakness is the absence of any 'when to use' guidance: it says what the skill covers but never tells Claude when to reach for it. Phrasing capabilities as actions rather than topic nouns would also sharpen it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user reports slow renders, laggy lists, jank, or app hangs in React/React Native, or when changing Account Selector rendering or other perf-sensitive code.'

Convert the topic-noun list into action phrases (e.g. 'Fix unnecessary re-renders with memoization, migrate long lists to FlashList, diagnose memory leaks, reduce bundle size') to match the verb-led style of the top anchor.

Add commonly-said synonyms such as 'slow', 'laggy', 'jank', or 'app hang' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Performance optimization for React/React Native') plus five concrete areas ('re-renders, memoization, FlashList, memory leaks, and bundle size'), giving specific coverage. Falls short of anchor 5 because the areas are topic nouns rather than action phrases like the verb-led anchor examples ('Extract text and tables from PDF files, fill forms, merge documents').

4 / 5

Completeness

The 'what' is clearly and specifically stated, but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which the judging guidelines cap at 3. Not score 2 because the 'what' is concrete and multi-part rather than vague.

3 / 5

Trigger Term Quality

Includes natural terms users would say when needing this skill: 're-renders', 'memoization', 'memory leaks', 'bundle size', 'FlashList', 'React/React Native'. Missing common variations and synonyms such as 'slow', 'laggy', 'jank', or 'app hang', so it matches anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The React Native specifics (FlashList, RN memory leaks) create a clear niche, but generic terms like 're-renders', 'memoization', and 'bundle size' could also match a general React or web performance skill. Minor overlap risk with closely related skills matches anchor 4 rather than the minimal-conflict profile of anchor 5.

4 / 5

Total

15

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

OneKeyHQ/app-monorepo

Path

.skillshare/skills/1k-performance/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.