Agent skill

Jazz Permissions Security

by garden-co in garden-co/classic-jazz

A skill your agent uses when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications.

MITAuto-check passedBackend & APIs

Install Jazz Permissions Security

skills CLI
$ npx skills add garden-co/classic-jazz --skill jazz-permissions-security -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install garden-co/classic-jazz jazz-permissions-security --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/garden-co/classic-jazz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/jazz-permissions-security .claude/skills/jazz-permissions-security && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
jazz-permissions-security
GitHub stars
2.5k
Token cost
~2.9k tokens
SKILL.md length
849 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications.

  • Works in 3 steps: Verify Ownership: Is the CoValue owned… → Verify Membership: Is the target user a… → Check References: Does the user have a…
  • Designing data schemas
  • SKILL.md covers When to Use This Skill, Do NOT Use This Skill For, Key Heuristic for Agents and Core Concepts, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Jazz Permissions Security is an agent skill from garden-co/classic-jazz. 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.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Authorization and RBAC. The repository describes itself as: A new kind of database that's distributed across your frontend, containers, serverless functions and its own storage cloud. The licence is MIT.

When your agent uses it

  • Designing data schemas
  • Implementing sharing workflows
  • Auditing access control in Jazz applications

Example prompts

  • “/jazz-permissions-security”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Verify Ownership: Is the CoValue owned by the expected Group? Check $jazz.owner.
  2. Verify Membership: Is the target user a member of that Group?
  3. Check References: Does the user have a way to discover the ID (e.g. through a reference in their account root)?

What it can do on your machine

Read from SKILL.md and the folder at commit 4f90501. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and svelte).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • jazz.tools
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jazz Permissions Security loads about 2.9k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 849 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from garden-co/classic-jazz at commit 4f90501, republished under its MIT licence (© garden-co). 849 words, ~2,899 tokens.

Download SKILL.mdSave it as .claude/skills/jazz-permissions-security/SKILL.md (or your agent's skills folder).
name
jazz-permissions-security
description
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.

Jazz Permissions & Security

When to Use This Skill

  • Structuring apps for multi-tenant or multi-user collaboration
  • Implementing sharing workflows, "Share" buttons, Invite Links, or Team management
  • Deciding who should own CoValues
  • Debugging "User cannot see data" or "Data is read-only" issues
  • Configuring permissions for Server Workers. Remember: Workers are just Accounts; they need to be invited to Groups like any other user

Do NOT Use This Skill For

  • Creating or designing schemas (use the jazz-schema-design skill)
  • Authentication
  • Generic UI component styling

Key Heuristic for Agents

If a user asks "How do I share X with Y?" or "Why can't I access this?", this is usually a Group Ownership issue.

Core Concepts

Security is cryptographic and group-based. Every CoValue has an owner, and access is controlled through Groups. You add users to a Group, and that Group owns the CoValues.

Groups can be members of other groups, creating hierarchical permission structures with inherited roles.

Critical Rule: Just because List A contains a reference to Item B does NOT mean readers of List A can see Item B. Item B must be owned by a Group the reader has access to.

The Ownership Hierarchy

Private

When creating CoValues without a specified owner, Jazz creates a new Group with the current account as the owner and sole admin member.

Code: MyMap.create({ ... })

Shared Data

To share data, you can either create a new Group and add members to it, or use an existing Group with multiple members.

Code: MyMap.create({ ... }, { owner: teamGroup })

Roles & Permissions Matrix

Jazz uses fixed roles. You cannot create custom roles.

RoleCapabilityBest For
adminRead, Write, Delete, Invite Members, Revoke Access, Change RolesTeam Owners, Creators
managerRead, Write, Add/Remove readers/writersDelegated management
writerRead, WriteCollaborators, Team Members
readerRead OnlyObservers, Public Links
writeOnlyWrite Only (Blind submissions)Voting, Dropboxes

All users can downgrade themselves or leave a group. Admins cannot be removed/downgraded except by themselves. Managers cannot remove/downgrade each other, but can remove/downgrade lower roles.

Note: Only admins can delete CoValues.

Managing Groups

When assigning roles, you can add Accounts, Groups, or "everyone". When adding a group, the most permissive role wins for members with multiple entitlements.

ts
const group = co.group().create();
const bob = await co.account().load(bobsId);

if (bob.$isLoaded) {
  group.addMember(bob, "writer");
  group.addMember(bob, "reader"); // Change role
  group.removeMember(bob);
}

Validating Permissions

ts
const red = MyCoMap.create({ color: "red" });
const me = co.account().getMe();

if (me.canAdmin(red)) {
  console.log("I can add users of any role");
} else if (me.canManage(red)) {
  console.log("I can share value with others");
} else if (me.canWrite(red)) {
  console.log("I can edit value");
} else if (me.canRead(red)) {
  console.log("I can view value");
}

// Or get role directly
red.$jazz.owner.getRoleOf(me.$jazz.id); // "admin"

Fundamental Patterns

Pattern 1: Creating Shared Data

Must pass the correct owner explicitly to ensure visibility.

ts
// ❌ WRONG: Defaults to private, other members won't see it
const task = Task.create({ title: "Fix bug" });
project.tasks.push(task);

// ✅ RIGHT: Explicitly set owner
const task = Task.create(
  { title: "Fix bug" },
  { owner: project.$jazz.owner }
);
project.tasks.push(task);

// ✅ ALSO RIGHT: Create new group for independent permissions
const taskGroup = co.group().create();
taskGroup.addMember(project.$jazz.owner, 'writer');
const task = Task.create({ title: "Fix bug" }, { owner: taskGroup });

Note: Inline creation (passing JSON) automatically handles group inheritance based on schema configuration (default is extendsContainer).

You MUST NOT use an Account as a CoValue owner.

Pattern 2: The Invite Flow

React:

ts
import { createInviteLink } from "jazz-tools/react";
const inviteLink = createInviteLink(organization, "writer");

Svelte:

ts
import { createInviteLink } from "jazz-tools/svelte";
const inviteLink = createInviteLink(organization, "writer");

Generates URL: .../#/invite/[CoValue ID]/[inviteSecret]

Accepting Invites

React:

tsx
import { useAcceptInvite } from "jazz-tools/react";

useAcceptInvite({
  invitedObjectSchema: Organization,
  onAccept: async (organizationID) => {
    const organization = await Organization.load(organizationID);
    if (!organization.$isLoaded) throw new Error("Could not load");
    me.root.organizations.$jazz.push(organization);
  },
});

Svelte:

svelte
<script lang="ts">
  import { InviteListener } from "jazz-tools/svelte";
  
  new InviteListener({
    invitedObjectSchema: Organization,
    onAccept: async (organizationID) => {
      const organization = await Organization.load(organizationID);
      if (!organization.$isLoaded) throw new Error("Could not load");
      me.current.root.organizations.$jazz.push(organization);
    },
  });
</script>

Programmatic:

ts
await account.acceptInvite(organizationId, inviteSecret, Organization);
Invite Secrets
ts
const groupToInviteTo = Group.create();
const readerInvite = groupToInviteTo.$jazz.createInvite("reader");
await account.acceptInvite(group.$jazz.id, readerInvite);

⚠️ Security: Invites do not expire and cannot be revoked. Never pass secrets as route parameters or query strings—only use fragment identifiers (hash in URL).

Pattern 3: Public Data

"Public" means "readable by anyone who knows the CoValue ID".

ts
const group = Group.create();
group.addMember("everyone", "writer");
// Or use alias
group.makePublic("writer"); // Defaults to "reader"
Pattern 4: Requesting Invites

Use writeOnly role for request lists—users can submit requests but not read others.

ts
const JoinRequest = co.map({
  account: co.account(),
  status: z.literal(["pending", "approved", "rejected"]),
});

function createRequestsToJoin() {
  const requestsGroup = Group.create();
  requestsGroup.addMember("everyone", "writeOnly");
  return RequestsList.create([], requestsGroup);
}

async function sendJoinRequest(requestsList, account) {
  const request = JoinRequest.create(
    { account, status: "pending" },
    requestsList.$jazz.owner
  );
  requestsList.$jazz.push(request);
}

async function approveJoinRequest(joinRequest, targetGroup) {
  const account = await co.account().load(joinRequest.$jazz.refs.account.id);
  if (account.$isLoaded) {
    targetGroup.addMember(account, "reader");
    joinRequest.$jazz.set("status", "approved");
    return true;
  }
  return false;
}
Pattern 5: Cascading Permissions (Groups as Members)

Groups can be added as members of other groups, creating hierarchies.

ts
const playlistGroup = Group.create();
const trackGroup = Group.create();
trackGroup.addMember(playlistGroup);

When you add groups as members:

  • Permissions are granted indirectly
  • Roles are inherited (except writeOnly)
  • Revoking access from member group removes access to container group

Warning: Deep nesting can cause performance issues.

Show full SKILL.md (320 more words)Show less
Role Inheritance Rules

Most Permissive Role Wins:

ts
const addedGroup = Group.create();
addedGroup.addMember(bob, "reader");

const containingGroup = Group.create();
containingGroup.addMember(bob, "writer");
containingGroup.addMember(addedGroup);
// Bob stays writer (higher than inherited reader)
Overriding Roles
ts
const organizationGroup = Group.create();
organizationGroup.addMember(bob, "admin");

const billingGroup = Group.create();
billingGroup.addMember(organizationGroup, "reader");
// All org members get reader access to billing, regardless of org role
Other Operations
ts
// Remove group
containingGroup.removeMember(addedGroup);

// Get parent groups
containingGroup.getParentGroups(); // [addedGroup]
Inline CoValue Creation

Jazz automatically manages group ownership for nested CoValues:

ts
const board = Board.create({
  title: "My board",
  columns: [["Task 1.1", "Task 1.2"], ["Task 2.1", "Task 2.2"]],
});

Each column and task gets a new group that inherits from the referencing CoValue's owner.

Example: Team Hierarchy
ts
const companyGroup = Group.create();
companyGroup.addMember(CEO, "admin");

const teamGroup = Group.create();
teamGroup.addMember(companyGroup);
teamGroup.addMember(teamLead, "admin");
teamGroup.addMember(developer, "writer");

const projectGroup = Group.create();
projectGroup.addMember(teamGroup);
projectGroup.addMember(client, "reader");

Troubleshooting

"User cannot see data"
  1. Verify Ownership: Is the CoValue owned by the expected Group? Check $jazz.owner.
  2. Verify Membership: Is the target user a member of that Group?
  3. Check References: Does the user have a way to discover the ID (e.g. through a reference in their account root)?
"Data is read-only"
  1. Check Role: Use red.$jazz.owner.getRoleOf(me.$jazz.id) to check the actual role. reader cannot write.
Cascading Issues
  1. Group Membership: If Group A is a member of Group B, check that the user is a member of Group A with a role that permits the desired action in Group B.
  2. Unsupported Roles: Remember writeOnly does not cascade.

Quick Reference

Ownership: Admin/manager modifies group membership, not CoValue ownership, which cannot be modified.

Permission inheritance: Nested CoValues inherit permissions from parent when created inline (behavior can be modified at the schema level).

Access control: Only members of a Group can access CoValues owned by that Group. References alone don't grant access.

Public access: makePublic() or addMember("everyone", "reader") makes Groups readable by anyone with the Group ID.

Invite links: createInviteLink() generates shareable URLs. Accept with useAcceptInvite() (React), InviteListener (Svelte) or account.acceptInvite().

Invite security: Never pass secrets as route parameters/query strings. Only use fragment identifiers.

Requesting access: writeOnly role on requests list allows non-members to submit join requests for admin review.

Cascading: Groups can be members of other groups. Roles inherit (admin, manager, writer, reader), but writeOnly doesn't. Most permissive role wins. Use getParentGroups() to inspect hierarchy.

References

When using an online reference via a skill, cite the specific URL to the user to build trust.

© garden-co, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/jazz-permissions-security of garden-co/classic-jazz.

Open the folder on GitHubat commit 4f90501

Compare with similar skills

Jazz Permissions Security next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jazz Permissions Security compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jazz Permissions Security this skillgarden-co/classic-jazz2.5k—~2.9kAutomated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
K8s Security PoliciesCybereason-Public/owLSM28012 repos~2kAutomated safety check: PassGPL-2.0
Payloadpayloadcms/payload45k5 repos~6.2kAutomated safety check: PassMIT
Convex Setup Authspokvulcan/poker-planning1158 repos~1.8kAutomated safety check: PassMIT
Cognitoitsmostafa/aws-agent-skills1.2k1 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed
  • K8s Security Policies

    Cybereason-Public/owLSM

    Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.

    280 GitHub starsUsed in 12 repos~2k tokens
    Backend & APIsAuto-check passed
  • Payload

    payloadcms/payload

    A skill your agent uses when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API).

    45k GitHub starsUsed in 5 repos~6.2k tokens
    Backend & APIsAuto-check passed
  • Convex Setup Auth

    spokvulcan/poker-planning

    Sets up Convex auth, identity mapping, and access control. An agent skill from spokvulcan/poker-planning.

    115 GitHub starsUsed in 8 repos~1.8k tokens
    Backend & APIsAuto-check passed
  • Cognito

    itsmostafa/aws-agent-skills

    AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Backend & APIsAuto-check passed
  • Abp Authorization

    abpframework/abp

    ABP permission system - PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, multi-tenancy side.

    14k GitHub stars~1.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from garden-co/classic-jazz

All 8 skills in this repo
  • Jazz Performance

    garden-co/classic-jazz

    A skill your agent uses when optimizing Jazz applications for speed, responsiveness, and scalability.

    2.5k GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Jazz Testing

    garden-co/classic-jazz

    A skill your agent uses when you need to write, review, or debug automated tests for applications built on the Jazz framework.

    2.5k GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Jazz UI Development

    garden-co/classic-jazz

    A skill your agent uses when building, debugging, or optimizing Jazz applications.

    2.5k GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Benchmarking

    garden-co/classic-jazz

    A skill your agent uses when writing or running performance benchmarks for Jazz packages.

    2.5k GitHub stars~3.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Jazz Schema Design

    garden-co/classic-jazz

    Design and implement collaborative data schemas using the Jazz framework.

    2.5k GitHub stars~3.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Changeset

    garden-co/classic-jazz

    Generate changeset files for versioning and changelog management in this monorepo.

    2.5k GitHub stars~538 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Jazz Permissions Security

What does Jazz Permissions Security do?

A skill your agent uses when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications. Jazz Permissions Security is an agent skill from garden-co/classic-jazz. Use this skill when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications.

When should I use Jazz Permissions Security?

Jazz Permissions Security fits situations like: designing data schemas; implementing sharing workflows; auditing access control in Jazz applications.

How do I install Jazz Permissions Security in Claude Code?

Run `npx skills add garden-co/classic-jazz --skill jazz-permissions-security -a claude-code`. Or copy the skill folder (.cursor/skills/jazz-permissions-security in garden-co/classic-jazz) into .claude/skills/jazz-permissions-security in your project. Claude Code loads it when a task matches its description.

How do I install Jazz Permissions Security in Codex?

Run `npx skills add garden-co/classic-jazz --skill jazz-permissions-security -a codex`. Or copy the skill folder (.cursor/skills/jazz-permissions-security in garden-co/classic-jazz) into .agents/skills/jazz-permissions-security in your project. Codex loads it when a task matches its description.

Can I use Jazz Permissions Security in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add garden-co/classic-jazz --skill jazz-permissions-security -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jazz-permissions-security, .gemini/skills/jazz-permissions-security, .github/skills/jazz-permissions-security and .opencode/skills/jazz-permissions-security in your project.

What does Jazz Permissions Security need to run?

SKILL.md names no scripts, command-line tools or credentials: Jazz Permissions Security is instructions for the agent only.

Does Jazz Permissions Security access the network?

SKILL.md names 2 domains. As links in the text: jazz.tools and github.com. This is read from the text; nothing was executed.

Is Jazz Permissions Security safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Jazz Permissions Security use?

Jazz Permissions Security is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jazz Permissions Security use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jazz Permissions Security?

Skills that share tags, products or a category with Jazz Permissions Security: Configuring Horizon (coollabsio/coolify, 63k stars), K8s Security Policies (Cybereason-Public/owLSM, 280 stars), Payload (payloadcms/payload, 45k stars) and Convex Setup Auth (spokvulcan/poker-planning, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jazz Permissions Security?

garden-co (a GitHub organization) maintains it in garden-co/classic-jazz, which has 2,534 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 7, 2026.

Source: garden-co/classic-jazz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.