Clerk Orgs

Name: Clerk Orgs
Author: clerk

Official

clerk·vlatest·security

This skill helps you identify and list organizations associated with a given topic, streamlining research and analysis.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add clerk/skills --skill clerk-orgs -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

clerk

Matched to the vendor's own GitHub organisation.

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 28 Sept 2026

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
Makes no network calls.
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.
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 clerk/skills at 863ff165de.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 863ff165de
Manifest: skills/features/clerk-orgs/SKILL.md
Scanned: 6 files, 1,042 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

The clerk-orgs skill enables AI agents to manage and interact with organizational structures, such as user roles, permissions, and team hierarchies. It provides tools for creating, updating, and retrieving information about organizations, making it useful in applications that require multi-tenant or role-based access control.

When to use it

Managing user access across multiple teams within a single application
Setting up role-based permissions for different departments or groups
Automating the creation of new organizations during onboarding processes

Key capabilities

Create and manage organization records
Assign and modify user roles within an organization
Retrieve organizational data based on user input

Example prompts

"Create a new organization called 'TechCorp' with admin access for [email protected]."
"List all users in the 'Marketing' team under the 'Acme Inc.' organization."
"Update the role of [email protected] to 'Manager' in the 'Sales' department."

Tips & gotchas

Ensure that your application has proper authentication and authorization mechanisms before using this skill.
This skill assumes a predefined schema for organizations, so be sure to align it with your data model.