jazz-permissions-security

Use this skill when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications. It covers the hierarchy of Groups, Accounts, and CoValues, ensuring data is private by default and shared securely through cascading permissions and invitations.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/jazz-permissions-security/SKILL.md

Quality

Content

65%

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

A highly actionable, well-structured reference packed with concrete Jazz-specific code, but it is a monolithic single file whose Quick Reference recap duplicates earlier content and whose destructive access operations lack explicit verification loops.

Suggestions

Remove or sharply trim the 'Quick Reference' section, whose recap of cascading rules, invite links, and public access duplicates content already in the Patterns and References sections — this is the main conciseness drag.

Add a verify-before-act step to destructive operations (e.g. check `getRoleOf` and confirm target before `removeMember`/role downgrade) to introduce the validate→fix→retry feedback loop the scoring notes expect for access changes.

Move the detailed per-pattern code examples and API snippets (Validating Permissions, Managing Groups, the Pattern 5 hierarchy) into a bundled reference file, keeping SKILL.md as an overview, to improve progressive disclosure for this size of skill.

Dimension	Reasoning	Score
Conciseness	The body is dense with Jazz-specific, non-obvious detail and avoids explaining general concepts Claude knows, but the 'Quick Reference' section largely recapitulates cascading rules, invite links, and public access already covered above, so not every token earns its place — matching the score-2 'could be tightened' anchor rather than the lean score-3 anchor.	2 / 3
Actionability	Provides abundant concrete, executable code throughout — `group.addMember(bob, "writer")`, `createInviteLink(organization, "writer")`, `useAcceptInvite({...})`, and a full join-request flow — with specific function names and parameters, matching the score-3 'copy-paste ready' anchor rather than the pseudocode score-2 anchor.	3 / 3
Workflow Clarity	The Troubleshooting section sequences verification steps (check `$jazz.owner`, membership, `getRoleOf`), but destructive member-removal and role-change operations lack explicit validate-then-confirm feedback loops, which per the scoring notes caps this dimension at 2 rather than 3.	2 / 3
Progressive Disclosure	Sections are well organized and external references are clearly signaled with specific URLs, but for a ~360-line skill all detailed patterns and API examples are inline in SKILL.md with no split into bundle files, fitting the score-2 'content that should be separate is inline' anchor; the under-50-line exception does not apply.	2 / 3
	Total	9 / 12 Passed

Description

92%

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 strong, specific, Jazz-scoped description with explicit what-and-when triggers and good natural keyword coverage. Its only real weakness is a trigger ('designing data schemas') that conflicts with a sibling skill the body itself defers to.

Suggestions

Drop or qualify 'designing data schemas' from the description's trigger clause, since the body's 'Do NOT Use' section routes schema design to the jazz-schema-design skill — this conflict is what caps distinctiveness.

Lead with a third-person declarative capability statement (e.g. 'Manages Jazz permissions…') before the 'Use this skill when' trigger, to match the rubric's preferred voice and front-load the 'what'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('designing data schemas, implementing sharing workflows, or auditing access control') and specific domain entities ('Groups, Accounts, and CoValues… cascading permissions and invitations'), matching the score-3 anchor. The imperative 'Use this skill when' mirrors the rubric's own good examples ('Use when', 'Use it when') and carries no first/second-person pronoun subject, so the voice penalty does not apply.	3 / 3
Completeness	Explicitly answers both 'what' ('It covers the hierarchy… ensuring data is private by default and shared securely through cascading permissions and invitations') and 'when' ('Use this skill when designing data schemas, implementing sharing workflows, or auditing access control'), matching the score-3 anchor.	3 / 3
Trigger Term Quality	Includes natural user-facing terms — 'sharing workflows', 'permissions', 'access control', 'invitations', 'data schemas' — giving good coverage of phrases a Jazz user would actually say, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Jazz-specific niche is distinct, but the 'designing data schemas' trigger directly overlaps with the explicitly-named jazz-schema-design skill the body directs users to instead, fitting the score-2 'could still overlap with similar skills' anchor rather than the conflict-free score-3 anchor.	2 / 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-permissions-security/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.