Skip to content
TrustedSkillsbeta
Back to all skills

Jazz Permissions Security

Checked
garden-co·vlatest·security·MIT

Automates granular access control based on jazz project roles, ensuring secure development workflows within Garden Co's environment.

Repository

Install on your platform

This skill no longer installs under the name jazz-permissions-security. garden-co/jazz has no skill named "jazz-permissions-security" any more. It was renamed, moved or deleted upstream.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-30. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

garden-co

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: 127.0.0.1.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    127.0.0.1local

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned garden-co/jazz at 5f42b14f4d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5f42b14f4d
Manifest
.agents/skills/analyze-local-telemetry/SKILL.md
Scanned
1 file, 135 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, jazz-permissions-security, provides a mechanism to manage and enforce access controls within an AI agent's environment. It allows you to define granular permissions, ensuring that specific actions or resources are only accessible based on predefined rules. The skill aims to enhance security by limiting potential damage from unauthorized operations or data breaches.

When to use it

  • Restricting API Access: Limit which APIs the agent can call and under what conditions (e.g., only allow access to a specific endpoint after authentication).
  • Data Sensitivity Control: Prevent the agent from accessing or modifying sensitive data unless explicitly authorized.
  • Workflow Security: Secure automated workflows by ensuring that only designated steps are executed with appropriate permissions.
  • User Role Management: Implement different levels of access for various users interacting with the AI agent, controlling their capabilities and scope.

Key capabilities

  • Permission Definition: Define specific actions and resources requiring protection.
  • Access Control Enforcement: Automatically enforce defined permission rules.
  • Granular Permissions: Support fine-grained control over access rights.
  • API Integration: Integrate with existing APIs to manage permissions at the API level.

Example prompts

  • "Set a permission that allows only authenticated users to delete files in the 'reports' directory."
  • "Restrict the agent from accessing the database unless it has the 'read_data' permission."
  • "Create a rule that requires two-factor authentication before executing any financial transactions."

Tips & gotchas

The effectiveness of this skill depends on clearly defining your permissions and ensuring they align with your security requirements. Incorrectly configured permissions could either overly restrict functionality or leave vulnerabilities unaddressed.