Skip to content

README.md

Latest commit

 

History

History
109 lines (78 loc) · 3.96 KB

README.md

File metadata and controls

109 lines (78 loc) · 3.96 KB
Raw

The jwt skill, for AI assistants

skill/jwt/ is an agent skill for github.com/kataras/jwt: one SKILL.md router plus five self-contained reference documents (the API map with real signatures, security, keys and JWKS, validators and blocklisting, and testing). An assistant loads the reference that matches your task instead of guessing at an API.

It exists because a general model knows Go and JWT in the abstract well, and this library's exact shape only vaguely. The most common failure is a confident, wrong signature, or a plausible-looking example lifted from doc.go's prose (which is not compiled or tested, and does contain mistakes). These documents are written against the source and are meant to be re-verified against it whenever the two disagree.

Plexon AI

Plexon AI is a desktop assistant for Windows, macOS and Linux, built by the author of this library, and it is the recommended way to use this skill. Turn the skill on from the Skills panel, or install the Software Developer persona, which enables it alongside the rest of its engineering tooling. Download Plexon AI.

Claude Code

Install it (recommended)

This repository is also a plugin marketplace, so the CLI can install the skill and update it in place. Two commands:

claude plugin marketplace add kataras/jwt
claude plugin install jwt@kataras-jwt

The same pair works as slash commands inside a session (/plugin marketplace add kataras/jwt, then /plugin install jwt@kataras-jwt). Later:

claude plugin marketplace update kataras-jwt   # pull newer versions
claude plugin details jwt                      # what it contains and its token cost
claude plugin uninstall jwt                    # remove it

--scope user is the default. Pass --scope project to record the install in the current project instead, so your team picks it up from your repository.

The plugin ships one skill and nothing else: no commands, no agents, no hooks, no MCP servers. Installing it cannot change how Claude Code behaves outside of jwt work.

Try it without installing

claude --plugin-dir /path/to/jwt

Loads the skill from a checkout for that session only, which is the quickest way to test a change you are making to the skill itself.

Copy the folder instead

A skill is just a folder, so you can skip the plugin machinery entirely and drop it into your skills directory. Personal, available in every project:

npx degit kataras/jwt/skill/jwt ~/.claude/skills/jwt

Project-scoped:

npx degit kataras/jwt/skill/jwt .claude/skills/jwt

Without npx, clone and copy:

git clone --depth 1 https://github.com/kataras/jwt /tmp/jwt
cp -r /tmp/jwt/skill/jwt ~/.claude/skills/jwt

Claude Code loads it on the next session. Update by copying over the top, remove by deleting the folder. This route has no version tracking, which is the trade-off against the plugin install above.

Codex, Cursor, Copilot and other assistants

Any tool that reads Markdown instructions can use this. Vendor the folder into your project and point your agent configuration at it, for example from AGENTS.md, a Cursor rule, or a Copilot instructions file:

When working with github.com/kataras/jwt, read skill/jwt/SKILL.md first and load the
reference document it points to for the task at hand.
npx degit kataras/jwt/skill/jwt skill/jwt

Google Code Wiki

For questions about the library's own internals rather than help writing code against it, the free Code Wiki for jwt is generated from this repository and stays in sync with it, commit by commit.

Keeping it honest

If a reference document contradicts the library source, the source is right. Please open an issue or a pull request rather than working around it locally: a wrong signature here becomes a wrong signature in someone's generated code.