New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Jwx Companion Bulk

by lestrrat-go in lestrrat-go/jwx

Apply bulk operations across all jwx companion modules. An agent skill from lestrrat-go/jwx.

MITAuto-check passedBackend & APIs

Install Jwx Companion Bulk

skills CLI
$ npx skills add lestrrat-go/jwx --skill jwx-companion-bulk -a claude-code

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

GitHub CLI
$ gh skill install lestrrat-go/jwx jwx-companion-bulk --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/lestrrat-go/jwx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/jwx-companion-bulk .claude/skills/jwx-companion-bulk && 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
jwx-companion-bulk
GitHub stars
2.4k
Token cost
~1.9k tokens
SKILL.md length
804 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Apply bulk operations across all jwx companion modules. An agent skill from lestrrat-go/jwx.

  • Works in 7 steps: Read Config → Ensure Clones → Pre-flight Checks → …
  • Tasks that involve Authentication
  • SKILL.md covers Arguments, 1. Read Config, 2. Ensure Clones and 3. Pre-flight Checks, plus 7 more sections
  • Calls git, go and gh

What it does

Jwx Companion Bulk is an agent skill from lestrrat-go/jwx. Apply bulk operations across all jwx companion modules. Args: <instructions...

Its SKILL.md is about 1.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 Authentication. It works with Go. The repository describes itself as: Complete implementation of JWx (Javascript Object Signing and Encryption/JOSE) technologies for Go. golang jwt jws jwk jwe. The licence is MIT.

When your agent uses it

  • Tasks that involve Authentication

Example prompts

  • “/jwx-companion-bulk”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Read Config
  2. Ensure Clones
  3. Pre-flight Checks
  4. Determine Execution Strategy
  5. Commit
  6. PR (only with --pr)
  7. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 03115b6. 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

    Shell commands in SKILL.md call:

    • git
    • go
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    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

Jwx Companion Bulk loads about 1.9k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 804 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~1.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 lestrrat-go/jwx at commit 03115b6, republished under its MIT licence (© lestrrat-go). 804 words, ~1,893 tokens.

Download SKILL.mdSave it as .claude/skills/jwx-companion-bulk/SKILL.md (or your agent's skills folder).
name
jwx-companion-bulk
description
Apply bulk operations across all jwx companion modules. Args: <instructions...>

jwx-companion-bulk

Apply a uniform operation across jwx companion modules (github.com/jwx-go/*). Handles cloning, branching, applying changes, verifying, committing, and reporting.

Arguments

/jwx-companion-bulk <instructions...>

  • $INSTRUCTIONS (required) — what to do across companion modules. Free-form text.
Flags (parsed from instructions)
  • --modules=<name,name,...> — target only these modules (comma-separated names)
  • --ref-module=<name> — use this module as the reference/template for file-copy operations
  • --pr — push branches and create PRs (off by default; commits locally only)
  • --dry-run — show what would change without modifying anything

If instructions are ambiguous, ask the user before proceeding.

1. Read Config

  1. Read companions.yaml from the project root.
  2. Parse the modules list. Each entry has: name, repo, branch.
  3. If --modules= was provided, filter to only those names. Error if a name is not found.

2. Ensure Clones

For each module in the (filtered) list:

  1. If $PROJECT/.companions/repo/<name>/ does not exist:

    cd $PROJECT
git clone <repo> .companions/repo/<name>

  2. If it already exists, update it:

    cd $PROJECT/.companions/repo/<name>
git fetch origin

  3. Determine the default branch for each module:

    • If branch is set in the config, use that.
    • Otherwise, read origin/HEAD:
      cd $PROJECT/.companions/repo/<name>
git symbolic-ref refs/remotes/origin/HEAD
      This returns e.g. refs/remotes/origin/develop/v4 — strip the prefix.
    • If origin/HEAD is not set, query GitHub:
      gh repo view <org>/<name> --json defaultBranchRef --jq .defaultBranchRef.name

  4. Checkout the default branch:

    cd $PROJECT/.companions/repo/<name>
git checkout <default-branch>
    cd $PROJECT/.companions/repo/<name>
git pull --ff-only

3. Pre-flight Checks

Run these on ALL targeted modules BEFORE modifying ANY:

  1. Clean working tree: git status --porcelain must produce empty output. If any module is dirty, report which ones and STOP.

  2. Remote reachable (only if --pr): git ls-remote origin HEAD must succeed.

  3. gh auth (only if --pr): gh auth status must succeed.

If pre-flight fails, report the failures and stop. Do not partially proceed.

4. Determine Execution Strategy

Decide whether this is a mechanical or creative operation:

  • Mechanical (same change replicated): dependency bumps, file sync/copy, adding identical files, updating CI workflows, version string changes.
  • Creative (independent work per module): lint-fix, refactor, bug fixes, anything where changes differ per module.

Heuristics:

  • Keywords "fix", "refactor", "lint" suggest creative.
  • Keywords "update", "sync", "add", "copy", "bump" suggest mechanical.

When unsure, ask the user: "Same mechanical change per module, or independent work per module?"

Mechanical: Prototype then Replicate
  1. Pick first module from list (or --ref-module if specified).
  2. Create a feature branch from the module's default branch:
    cd $PROJECT/.companions/repo/<name>
git checkout -b <branch-name> <default-branch>
    Use ordinary branch naming: <category>-<short-description> (e.g. chore-bump-jwx-dep).
  3. Apply instructions to this module.
  4. Verify (if module has go.mod):
    cd $PROJECT/.companions/repo/<name>
go build ./...
    cd $PROJECT/.companions/repo/<name>
golangci-lint run ./...
  5. Record exactly what changed: files modified/added/deleted, nature of change.
  6. For each remaining module: a. Create feature branch (same name). b. Replicate the change, adapting module-specific values (module name in import paths, go.mod module path, etc.). c. Verify (go build + golangci-lint if has go.mod). d. If verification fails, revert (git checkout .), delete the branch, record failure, continue to next module.
Creative: Parallel Subagents
  1. Spawn one Agent per module, all in a single parallel block.
  2. Each agent receives:
    • Module path: $PROJECT/.companions/repo/<name>
    • Default branch name
    • The instructions
    • Directions to: create a feature branch, do the work, verify, commit.
  3. Subagents do NOT have Skill tool access. Give them explicit instructions.
  4. Wait for all agents, collect results.
Show full SKILL.md (326 more words)Show less

5. Commit

For each module where changes were made and verification passed:

  1. Stage relevant files:
    cd $PROJECT/.companions/repo/<name>
git add <files>
  2. Commit following standard commit message rules.

6. PR (only with --pr)

For each module where changes were committed:

  1. Push the feature branch:
    cd $PROJECT/.companions/repo/<name>
git push -u origin <branch-name>
  2. Create PR:
    cd $PROJECT/.companions/repo/<name>
gh pr create --title "<title>" --body "<body>"
    Target the module's default branch.
  3. Record PR URL.

7. Report

Always end with a report:

## Companion Module Bulk Operation Report

**Operation**: <summary of instructions>
**Date**: YYYY-MM-DD
**Modules targeted**: N
**Succeeded**: X | **Skipped**: Y | **Failed**: Z

| Module | Branch | Status | PR | Notes |
|--------|--------|--------|----|-------|
| ... | ... | success/skipped/failed | URL or — | ... |

### Files Changed
- <list of files modified across modules>

### Errors (if any)
- **<module>**: <error description>

Adaptation Rules

When replicating changes across modules, adapt these patterns:

PatternAdaptation
Module name in go.modRead actual module path from the target's go.mod
Module name in CI YAMLPackage-specific test paths
Import pathsAdjust jwx-go/<proto> to jwx-go/<target>
Default branchUse branch from companions.yaml for each module
Modules without go.mod (benchmarks)Skip Go-specific steps (build, lint, dep update)

Error Handling

ErrorResponse
Dirty working treeSTOP entirely (pre-flight)
go build fails after changeRevert, record failure, continue others
golangci-lint fails after changeRevert, record failure, continue others
Module not applicable (e.g. no go.mod for dep update)Skip, report "not applicable"
PR creation failsReport failure, branch still pushed
Git push failsReport, do not retry, continue others
File already matches desired stateReport "already up to date", skip

Hard Rules

  • NEVER commit directly to default branch — always create a feature branch.
  • NEVER force-push.
  • NEVER proceed on a module with dirty working tree.
  • ALWAYS run pre-flight on ALL modules before modifying ANY.
  • ALWAYS verify go build ./... and golangci-lint run ./... before committing (for modules with go.mod).
  • ALWAYS report per-module results even on partial failure.
  • ALWAYS cd into $PROJECT/.companions/repo/<name> before running ANY command (git, go, golangci-lint) for that module. NEVER use git -C, --git-dir, or --work-tree instead — they don't apply to non-git tools, and the shell's working directory stays in the parent jwx repo so its git context leaks through.
  • NEVER use compound commands (&&, ||, ;) in Bash calls.
  • PRs are OFF by default. Only push/create PRs when --pr is specified.

© lestrrat-go, 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 .claude/skills/jwx-companion-bulk of lestrrat-go/jwx.

Open the folder on GitHubat commit 03115b6

Compare with similar skills

Jwx Companion Bulk 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.

Jwx Companion Bulk compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jwx Companion Bulk this skilllestrrat-go/jwx2.4k—~1.9kAutomated safety check: PassMIT
JWTkataras/jwt212—~1.5kAutomated safety check: PassMIT
Human Writingkataras/jwt212—~1.9kAutomated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Supabase Development and Debuggingsupabase/agent-skills2.7k3 repos~3.6kAutomated safety check: PassMIT
Better Auth Best Practiceslatitude-dev/latitude-llm4.7k7 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • JWT

    kataras/jwt

    Development guide for the jwt JSON Web Token library for Go (github.com/kataras/jwt).

    212 GitHub stars~1.5k tokensUpdated 28 days ago
    Backend & APIsAuto-check passed

  • Human Writing

    kataras/jwt

    A skill your agent uses when writing or editing any prose in this repository - the book's preface, its chapters and epilogue, the brand kit notes, the agent skill documents, the changelog, and the…

    212 GitHub stars~1.9k tokensUpdated 28 days ago
    DevelopmentAuto-check passed

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed

  • Supabase Development and Debugging

    supabase/agent-skills

    Official

    General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.

    2.7k GitHub starsUsed in 3 repos~3.6k tokens
    Backend & APIsAuto-check passed

  • Better Auth Best Practices

    latitude-dev/latitude-llm

    Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.

    4.7k GitHub starsUsed in 7 repos~1.6k tokens
    Backend & APIsAuto-check passed

  • Gitnexus Exploring

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.

    106 GitHub starsUsed in 12 repos~749 tokens
    Backend & APIsAuto-check passed

More from lestrrat-go/jwx

  • Jwx Guide V4

    lestrrat-go/jwx

    Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse/sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid the common footguns.

    2.4k GitHub stars~5.7k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Jwx Companion Bulk

What does Jwx Companion Bulk do?

Apply bulk operations across all jwx companion modules. An agent skill from lestrrat-go/jwx. Jwx Companion Bulk is an agent skill from lestrrat-go/jwx. Apply bulk operations across all jwx companion modules.

When should I use Jwx Companion Bulk?

Jwx Companion Bulk fits situations like: tasks that involve Authentication.

How do I install Jwx Companion Bulk in Claude Code?

Run `npx skills add lestrrat-go/jwx --skill jwx-companion-bulk -a claude-code`. Or copy the skill folder (.claude/skills/jwx-companion-bulk in lestrrat-go/jwx) into .claude/skills/jwx-companion-bulk in your project. Claude Code loads it when a task matches its description.

How do I install Jwx Companion Bulk in Codex?

Run `npx skills add lestrrat-go/jwx --skill jwx-companion-bulk -a codex`. Or copy the skill folder (.claude/skills/jwx-companion-bulk in lestrrat-go/jwx) into .agents/skills/jwx-companion-bulk in your project. Codex loads it when a task matches its description.

Can I use Jwx Companion Bulk 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 lestrrat-go/jwx --skill jwx-companion-bulk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jwx-companion-bulk, .gemini/skills/jwx-companion-bulk, .github/skills/jwx-companion-bulk and .opencode/skills/jwx-companion-bulk in your project.

What does Jwx Companion Bulk need to run?

Going by SKILL.md and its folder, Jwx Companion Bulk needs the command-line tools its instructions call (git, go and gh).

Does Jwx Companion Bulk access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Jwx Companion Bulk 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 Jwx Companion Bulk use?

Jwx Companion Bulk 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 Jwx Companion Bulk use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 Jwx Companion Bulk?

Skills that share tags, products or a category with Jwx Companion Bulk: JWT (kataras/jwt, 212 stars), Human Writing (kataras/jwt, 212 stars), Fortify Development (coollabsio/coolify, 63k stars) and Supabase Development and Debugging (supabase/agent-skills, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jwx Companion Bulk?

lestrrat-go (a GitHub organization) maintains it in lestrrat-go/jwx, which has 2,433 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

Source: lestrrat-go/jwx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.