CtrlK
BlogDocsLog inGet started
Tessl Logo

jazz-testing

Use this skill when you need to write, review, or debug automated tests for applications built on the Jazz framework. This skill provides the correct architectural patterns for simulating local-first synchronization and multi-user environments without resorting to invalid mocking strategies.

66

Quality

83%

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

The canonical home for this skill is jazz-testing in garden-co/classic-jazz

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, actionable, and uses progressive disclosure effectively with real reference files and executable examples. The main weakness is mild redundancy between the Common Pitfalls and Quick Reference sections that could be trimmed for token efficiency.

Suggestions

Remove or compress the Quick Reference section since it duplicates Common Pitfalls and earlier guidance, cutting tokens without losing information.

Add a brief full example showing createJazzTestAccount with a custom AccountSchema and isCurrentActiveAccount so the documented parameters are executable end-to-end.

DimensionReasoningScore

Conciseness

The body is mostly efficient with useful code examples, but the Quick Reference section restates Common Pitfalls content (reload CoValues after setActiveAccount, call setupJazzTestSync in beforeEach) and the Key Heuristic overlaps the Fundamental Principles, so it could be tightened.

3 / 5

Actionability

Provides executable TypeScript examples (setupJazzTestSync in beforeEach, the unauthorized-writes flow, runWithoutActiveAccount) with specific API parameters, covering common cases copy-paste ready; minor gaps remain around custom AccountSchema usage.

4 / 5

Workflow Clarity

Patterns are clearly sequenced (setup sync -> create accounts -> switch active account -> reload CoValue) with expect() assertions acting as validation checkpoints; not a destructive/batch operation so no cap applies, though explicit feedback loops are light.

4 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references to real bundle files (references/react-test-provider.tsx, provider-context.tsx, Provider.svelte, jazz.svelte.ts) plus an on-demand external-links section, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

87%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, complete, and well-differentiated, clearly stating what the skill does and when to use it with natural trigger language. Its only weakness is the second-person voice ('when you need to'), which costs a specificity point, and slightly thin synonym coverage in the trigger terms.

Suggestions

Rephrase the trigger clause in third person (e.g., 'Use when writing, reviewing, or debugging automated tests for Jazz applications') to avoid the second-person voice penalty.

Add a few natural synonyms to the description (e.g., 'unit and integration tests') so trigger coverage does not depend on the body.

DimensionReasoningScore

Specificity

Lists several concrete actions (write, review, or debug automated tests; simulate local-first synchronization and multi-user environments; avoid invalid mocking) for comprehensive coverage, but the second-person phrasing 'when you need to' triggers the voice penalty reducing it from 5 to 4.

4 / 5

Completeness

Explicitly answers both 'what' (correct architectural patterns for simulating sync and multi-user environments without mocking) and 'when' (Use this skill when you need to write, review, or debug automated tests for Jazz) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger terms like 'write, review, or debug automated tests' and 'Jazz framework' are present and would be said by users, but the description lacks common synonyms (unit/integration tests, specs) that appear only in the body.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (the Jazz framework's local-first sync testing) with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

100%

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