CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-performance

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

56

Quality

65%

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

67%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 content is concise, actionable, and well-structured with a verified single-level reference. Its main weakness is the absence of a measurement/validation workflow, which limits workflow clarity for performance changes that should be verified.

Suggestions

Add a short validation workflow: measure before/after (e.g. render count, bundle size, AppHang trace) and confirm the change improved the target metric.

Expand the 'Heavy Operations' row into a runnable InteractionManager/runAfterInteractions snippet rather than just naming the APIs.

Make the quick-reference thresholds explicit in code (e.g. show windowSize={5} in a FlashList example) to raise actionability.

DimensionReasoningScore

Conciseness

The body is well-structured with a tight quick-reference table and focused code, mostly assuming Claude's competence; the 'Built-in Optimizations' table and topic list add minor padding that could be trimmed.

4 / 5

Actionability

It provides a copy-paste ready executeBatched implementation and concrete thresholds (concurrency 3-5, windowSize={5}), but some guidance stays at topic level (e.g. 'InteractionManager, setTimeout') without runnable snippets.

4 / 5

Workflow Clarity

The skill offers optimization patterns rather than a sequenced diagnostic workflow, and includes no validation/measurement checkpoints (e.g. how to confirm a re-render reduction or measure bundle size) for these performance changes.

3 / 5

Progressive Disclosure

SKILL.md is a clear overview with a single one-level-deep reference ([performance.md](references/rules/performance.md)) that is a real file, and inline content is appropriately summarized rather than duplicated.

4 / 5

Total

15

/

20

Passed

Description

63%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 specific and distinct, listing concrete performance topics, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding natural trigger phrases would lift both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user reports React/React Native performance problems, slow lists, UI freezes, or excessive re-renders.'

Include user-natural synonyms such as 'slow', 'jank', 'lag', and 'AppHang' to broaden trigger coverage.

Reframe topic nouns as concrete actions (e.g. 'reduce re-renders', 'detect memory leaks') to strengthen specificity.

DimensionReasoningScore

Specificity

The description names the domain (React/React Native performance) and lists several concrete optimization areas ('re-renders, memoization, FlashList, memory leaks, and bundle size'), but these are topics rather than executable actions, leaving minor coverage gaps.

4 / 5

Completeness

It clearly states 'what' the skill does (performance optimization for specific topics) but lacks any 'Use when...' trigger clause, which the rubric caps at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

It surfaces several natural user-facing terms (re-renders, memoization, memory leaks, bundle size, FlashList) but omits synonyms like 'slow', 'jank', 'lag', or 'performance issues' that users commonly say.

4 / 5

Distinctiveness Conflict Risk

The React/React Native performance niche with OneKey-specific terms is mostly distinct, with only minor overlap risk against general coding-patterns or Sentry skills.

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.

Validation13 / 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
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.