jazz-performance

Use this skill when optimizing Jazz applications for speed, responsiveness, and scalability. Covers crypto setup, efficient data modeling, and UI patterns to prevent lag.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

The content is highly actionable and well-structured with one-level reference files and a clear decision heuristic, with the only real weakness being some redundant summary sections that pad the token budget.

Suggestions

Remove redundancy between Common Pitfalls, Quick Checklist, and Quick Reference — consolidate to a single checklist to reclaim tokens without losing guidance.

Consider compressing the large SLOW-vs-FAST useCoState example into a shorter focused snippet, keeping the ❌/✅ contrast but trimming the surrounding boilerplate.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with lean ❌/✅ code pairs and a Quick Reference, but there is redundancy (Common Pitfalls repeats the selector note verbatim and the Quick Checklist overlaps earlier sections) and one long UI code block that could be trimmed.	2 / 3
Actionability	Provides fully executable TS/TSX throughout — flat CoValue creation, setDefaultSchemaPermissions, shallow vs deep useCoState loading, and a lightweight-selector-plus-useMemo pattern — copy-paste ready with concrete examples.	3 / 3
Workflow Clarity	As a single-purpose guidance skill it has an unambiguous structure (When to Use / Do NOT Use / Core Concepts / Quick Checklist), and the key heuristic makes the decision path clear; per the simple-skills note this warrants a 3.	3 / 3
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references (references/node-api.md and references/wasm.md, both verified to exist), keeping detail out of the main body appropriately.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 clear, third-person, and answers both what and when with natural trigger terms, though its capability list is moderately specific rather than exhaustive and could overlap with adjacent skills.

Suggestions

Tighten specificity by naming concrete actions (e.g. 'profile load times, choose CoValue vs Zod types, configure Node-API/WASM crypto, optimize React selectors') instead of the broad 'crypto setup, efficient data modeling, and UI patterns'.

Strengthen distinctiveness by scoping the trigger to Jazz-specific symptoms (e.g. 'slow CoValue sync, deep group extension, expensive useCoState selectors') to reduce overlap with general performance or sibling Jazz skills.

Dimension	Reasoning	Score
Specificity	Names the Jazz domain and several action areas ('crypto setup, efficient data modeling, and UI patterns to prevent lag') but does not enumerate comprehensive concrete actions, matching the anchor that names a domain and some actions.	2 / 3
Completeness	Explicitly answers both what ('Covers crypto setup, efficient data modeling, and UI patterns') and when ('Use this skill when optimizing Jazz applications for speed...'), matching the anchor requiring explicit triggers for both.	3 / 3
Trigger Term Quality	Uses natural user-facing terms ('speed', 'responsiveness', 'scalability', 'lag') that a user would plausibly say when needing this skill, giving good coverage of natural trigger language.	3 / 3
Distinctiveness Conflict Risk	The Jazz-performance niche is reasonably specific, but the broad performance framing ('speed, responsiveness, and scalability') could still overlap with general optimization or sibling Jazz skills, so it is not yet a fully conflict-free niche.	2 / 3
	Total	10 / 12 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: garden-co/classic-jazz
Path: packages/cursor-docs/.skills/jazz-performance/SKILL.md
Commit: 4f90501

Reviewed: 6 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.