Name: jwx-guide-v4
Rating: 65.60000000000001 (1 reviews)
Author: lestrrat-go

jwx-guide-v4

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. For developers using jwx, not for developing the library itself.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agents/plugin/skills/guide/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized jwx v4 reference with excellent executable code and sharp footgun guidance. Its main weakness is progressive disclosure: substantial reference catalogs live inline in SKILL.md with no local companion files to offload them.

Suggestions

Move the companion-module catalogs, error-type list, and algorithm tables into a references/ file (e.g. COMPANIONS.md, ERRORS.md) and link to them one level deep, leaving SKILL.md as a leaner overview.

Trim or collapse the more obscure experimental companion modules (reddy-pqchpke, mlkem) to a brief mention plus a link, since they are draft-spec and rarely needed.

Add a short "Verify before answering" checkpoint in the lookup workflow that names which source to cite for an API claim, reinforcing the existing ordered-source procedure.

Dimension	Reasoning	Score
Conciseness	Dense and reference-style with no padding over concepts Claude already knows (it never explains what a JWT is), but at ~330 lines some detailed catalogs like the companion-module tables could be trimmed or moved.	4 / 5
Actionability	Provides copy-paste-ready, executable Go for every common case — verify, sign, JWK parse/import/export, JWS, JWE, errors — with concrete option names and exact function-call syntax.	5 / 5
Workflow Clarity	The "Where to look things up" section is a clearly ordered procedure and sections are prioritized ("read first"), but there are no validation checkpoints because the skill is a reference rather than a destructive/batch workflow.	4 / 5
Progressive Disclosure	Sections are well-organized and external sources (pkg.go.dev, GitHub docs, examples repo) are clearly signaled, but no local bundle files exist and large reference catalogs (companion modules, error types, algorithm tables) are inlined in a 330-line SKILL.md rather than split into one-level-deep reference files.	3 / 5
	Total	16 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that names concrete jwx capabilities and pins the library/version niche precisely. It would benefit from an explicit "Use when…" trigger clause listing the natural phrases users say.

Suggestions

Add an explicit "Use when the user mentions JWTs, JWS, JWE, JWK, token signing/verification, or the lestrrat-go/jwx v4 library" trigger clause to lift completeness.

Include a few synonyms/extensions (e.g. "token signing", "JWKS", "key sets") to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete action areas — "parse/sign JWTs", "work with JWS/JWE/JWK", "pick algorithms", "avoid the common footguns" — giving multi-action coverage of the jwx surface, though key-management specifics are not enumerated.	4 / 5
Completeness	Clearly states what the skill does and gives explicit use scoping ("For developers using jwx, not for developing the library itself"), which serves as equivalent trigger guidance, but lacks concrete "Use when the user mentions X" trigger phrases that would make the when fully explicit.	4 / 5
Trigger Term Quality	Includes natural terms a Go developer would say ("JWTs", "JWS", "JWE", "JWK", "algorithms", "github.com/lestrrat-go/jwx v4") with good coverage, but lacks synonyms or extension-area terms that would round it out.	4 / 5
Distinctiveness Conflict Risk	Scoped to a single named library at a pinned major version ("github.com/lestrrat-go/jwx v4") and explicitly excludes library-development use, giving it a clear niche with minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 12 missing	Warning

	Total	15 / 16 Passed

Repository: lestrrat-go/jwx
Path: agents/plugin/skills/guide/SKILL.md
Commit: 1d2d051

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.