agentleFS
Sign inStart free
nnawar706nnawar706/fluento/.agents/skills/clerk-cli/SKILL.md

clerk-cli

Skill0 starsChanged 5 months agoNo licenceView on GitHub

Operate the Clerk CLI (`clerk` binary) for authentication, user/org/session management, deploy verification, instance config, env keys, and any Clerk Backend or Platform API call. Use when the user mentions Clerk management tasks, "list clerk users", "create a clerk user", "update organization", "pull clerk config", "clerk env pull", "clerk doctor", "clerk deploy", "clerk deploy status", "clerk api", or any ad-hoc Clerk API request. Prefer the CLI over raw HTTP: it handles auth, key resolution, app/instance targeting, and formatting automatically.

  • Reads credentials
  • Installs packages

5 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use clerk-billing, clerk-expo and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sanketbodkeSkill

    clerk-billing

    Clerk Billing for subscription management - render Clerk's PricingTable

    Also in 3 projects that use this

  • AymenjdilySkill

    clerk-expo

    Add Clerk authentication to Expo and React Native apps using @clerk/expo.

    Also in 3 projects that use this

  • elpiartheraSkill

    clerk-orgs

    Clerk Organizations for B2B SaaS - create multi-tenant apps with org switching, role-based access, verified domains, and enterprise SSO. Use for team workspaces, RBAC, org-based routing, member management.

    Also in 4 projects that use this

  • elpiartheraSkill

    clerk-testing

    E2E testing for Clerk apps. Use with Playwright or Cypress for auth flow tests.

    Also in 4 projects that use this

  • +1 more from elpiarthera

The file

We split this skill into the rules it gives an agent

9 rules. 2 are common, 1 is distinctive, and 6 are very specific to this project.

  • 2

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free