jazz-schema-design

Design and implement collaborative data schemas using the Jazz framework. Use this skill when building or working with Jazz apps to define data structures using CoValues. This skill focuses exclusively on schema definition and data modeling logic.

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

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, Jazz-specific reference with executable code, a sequenced checklist, and migration feedback loops. Its main weaknesses are length/verbosity in a few caution passages and a monolithic structure that underuses progressive disclosure despite well-signaled external links.

Suggestions

Move the permissions deep-dive and/or the CoValue type reference table into bundled reference files under ./references/, keeping SKILL.md as a lean overview with one-level-deep pointers.

Tighten the 'USE EXTREME CAUTION' block to a single crisp rule (avoid `sameAsContainer` when child permissions may ever need to diverge) instead of restating the warning multiple times.

Collapse the four overlapping relationship code examples into one annotated example that marks one-to-one, one-to-many, and many-to-many variations inline.

Dimension	Reasoning	Score
Conciseness	The body is dense with genuinely Jazz-specific content (no basic-concept padding) and assumes programming competence, but sections like the repetitive 'USE EXTREME CAUTION' paragraph and several near-duplicate relationship code blocks could be tightened; it is mostly efficient rather than lean.	2 / 3
Actionability	It provides executable, copy-paste-ready TypeScript throughout — `co.map()`, `withPermissions()`, `withMigration()`, getters for forward refs, and concrete usage like `author.posts.$jazz.set(...)` — with specific API calls rather than pseudocode.	3 / 3
Workflow Clarity	A 'Design Checklist' sequences the work and includes validation items ('Ensure there are no TS or linting errors', 'Ensure an initial migration exists'), and the migration example shows an explicit guard/exit-early feedback loop for a load-time operation.	3 / 3
Progressive Disclosure	Sections are well organized and end-of-file external references are clearly signaled and one level deep ('Load these on demand'), but the file is a ~430-line monolith with the permissions deep-dive, type table, and pattern catalog all inline where a split into bundled reference files would aid navigation.	2 / 3
	Total	10 / 12 Passed

Description

90%

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-structured, third-person description that clearly states capability and explicit use-when triggers within a distinct niche. The only weakness is that the action verbs (design, implement, define) are somewhat abstract compared to the most concrete anchor examples.

Suggestions

Swap abstract verbs for more granular concrete actions, e.g. 'Define CoValue schemas, configure schema-level permissions, model relationships, and plan migrations using the Jazz framework.'

Add a couple of natural trigger phrasings users might say (e.g. 'data model', 'Jazz schema', 'CoValue') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and actions ('Design and implement collaborative data schemas', 'define data structures using CoValues'), but the verbs are comparatively abstract rather than a list of granular concrete actions, so it sits at 'names domain and some actions' rather than the multi-action anchor.	2 / 3
Completeness	It answers both 'what' ('Design and implement collaborative data schemas using the Jazz framework') and 'when' with an explicit 'Use this skill when building or working with Jazz apps...' trigger clause.	3 / 3
Trigger Term Quality	It surfaces natural terms a Jazz user would say — 'Jazz apps', 'data schemas', 'data structures', 'CoValues', 'schema definition', 'data modeling' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	The scoped claim 'focuses exclusively on schema definition and data modeling logic' plus Jazz/CoValue-specific triggers carve a clear niche unlikely to fire for sibling Jazz skills.	3 / 3
	Total	11 / 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: .cursor/skills/jazz-schema-design/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.