CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

performance

Keep app loads and interactions responsive as data grows. Use when a page feels slow, jumps, or lags, or when changing a data read, list, polling path, startup path, or performance-sensitive UI.

Quality

80%

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 ./.agents/skills/performance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 lean, well-organized, directive-style guidance skill: no fluff, no over-explanation, specific latency budgets, and concrete patterns throughout. The main room for improvement is actionability — naming measurement tools or one concrete example per section — and making the investigation workflow's sequence more explicit.

DimensionReasoningScore

Conciseness

The body is pure directives — "Batch related reads instead of issuing one query per row", "Give loading placeholders the final content's basic geometry" — with no padding, no explanation of concepts Claude already knows, and brief justifications only where they change behavior ("Hosted serverless instances can restart, so startup work can repeat"). This matches anchor 5: lean, assumes competence, every token earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is concrete: numeric thresholds ("aiming for 100 ms", "within 400 ms") and named patterns (paginate/window, optimistic update "then confirm or roll back on failure"). However there is no code, command, or tooling, and some directives remain judgment calls ("measure before adding caches" names no measurement method), fitting anchor 4 rather than fully executable anchor 5.

4 / 5

Workflow Clarity

Content is organized by concern with the measure-first principle stated up front, and the final section gives an investigation sequence with a verification checkpoint ("Verify that the user-visible action completed before comparing timings or memory"). There is no destructive or batch operation requiring a validation cap, but the workflow is implicit across sections rather than an explicitly sequenced process, fitting anchor 4.

4 / 5

Progressive Disclosure

Clear section headers, no nested or buried references, and no overview-level content inlined that clearly belongs in separate files. With roughly 70 lines and no external file references it sits just above the under-50-line case that would earn a 5, matching anchor 4 (good structure, minor organization gaps).

4 / 5

Total

17

/

20

Passed

Description

70%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 well-crafted description with an explicit, multi-trigger 'Use when' clause written in third-person imperative voice and no fluff. The main gap is specificity: the 'what' is a single goal statement rather than a list of concrete capabilities, and a few common performance synonyms are absent from the triggers.

Suggestions

Name 2-3 concrete capabilities in the 'what' clause, e.g. "Trim list reads, batch and paginate queries, keep startup work out of request paths, and keep interactions responsive as data grows."

Add common user phrasings to the triggers, such as "slow", "lagging", "optimize", "speed up", "latency", or "slow queries".

Consider mentioning the investigation/measurement angle ("find the cost users actually wait on") in the description so it triggers on profiling requests, not just code changes.

DimensionReasoningScore

Specificity

"Keep app loads and interactions responsive as data grows" names the app-performance domain with 1-2 high-level actions, but lists no concrete techniques (paginate, batch reads, defer startup work, index), matching anchor 3 rather than 4.

3 / 5

Completeness

Both parts are present: an explicit "Use when..." clause with several concrete trigger situations, and a clear 'what' ("Keep app loads and interactions responsive as data grows"). The 'what' is a single goal clause rather than a concrete capability list, keeping it just below anchor 5.

4 / 5

Trigger Term Quality

Triggers include natural phrases users would say — "a page feels slow, jumps, or lags", "changing a data read, list, polling path, startup path" — but common synonyms like "optimize", "speed up", "latency", "slow query", or "rendering" are missing, so it fits anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Triggers like "polling path", "startup path", and "performance-sensitive UI" carve a distinct performance niche; only minor overlap risk with general web-development or debugging skills via the broad "page feels slow" trigger.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/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.