CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 reference whose code examples are uniformly executable and whose security guardrails are explicit and repeated at the point of use. The main cost is conciseness: duplicated rule/mistake listings, a table of crypto basics, and lengthy version-dependent narratives pad the token budget.

Suggestions

Merge "Common mistakes to flag in user code" into "Critical rules (read first)" (or cross-reference it) to eliminate the near-duplicate items on jwa.RS256(), jwk.Import/Export type parameters, ParseKey non-generic, and RequireKid(false).

Trim the algorithm-family table to the version-specific guidance (EdDSA vs Ed25519 deprecation, none refused) and drop generic crypto facts Claude already knows like "RSA, widest interop" and "smaller signatures than RSA".

Move the companion-modules tables and the ML-DSA Go 1.26/1.27 version-bridging narrative into a reference file (e.g. references/extensions.md), keeping SKILL.md to the lookup pointers and the "algorithm not registered" troubleshooting rule.

DimensionReasoningScore

Conciseness

Mostly efficient, version-specific high-value facts ("jwa algorithms are functions in v4, not constants"), but "Critical rules" and "Common mistakes" substantially repeat each other, the algorithm-family table re-explains crypto basics Claude already knows, and the ML-DSA version-bridging narrative runs long with time-sensitive version detail not placed in a deprecated/old-patterns section.

3 / 5

Actionability

Every section ships executable, copy-paste-ready Go covering the common cases (parse/verify/sign, JWK import/export, JWS, JWE, nested JWT serializer, typed error handling, field access), plus a concrete module-cache lookup command and exact documentation URLs.

5 / 5

Workflow Clarity

The workflows that exist are clearly sequenced with checkpoints: the nested-JWT receive flow is decrypt → check error → jwt.Parse with an emphatic "NEVER skip it" validation step, and "Where to look things up" gives an ordered source-preference sequence; no destructive or batch operation requires a missing feedback loop. Matches the 4 anchor — clear sequence with most checkpoints — rather than 5 because it is a reference-style skill without explicit checklists or feedback loops.

4 / 5

Progressive Disclosure

The single-file body is well-structured with clear headers, tables, and a prominent "Where to look things up" section with clearly signaled one-level-deep external navigation (pkg.go.dev, repo docs, examples README index); however, some inline content such as the companion-module tables and the detailed ML-DSA version narrative could live in a reference file, keeping it short of the 5 anchor.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong description with concrete, comprehensive capabilities and excellent distinctiveness from version-pinning and explicit scope boundaries. Its only weaknesses are the absence of an explicit "Use when..." trigger phrase and a few natural synonym terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user is writing Go code that imports github.com/lestrrat-go/jwx/v4, or asks about JWT/JWS/JWE/JWK handling in Go."

Include natural synonyms users would type, such as "JSON Web Token", "token", or "signing/verifying tokens", alongside the existing JWT/JWS/JWE/JWK terms.

Consider naming the common trigger scenarios (e.g., "verifying tokens from an issuer's JWKS endpoint", "migrating from jwx v2/v3") to sharpen when-to-use guidance.

DimensionReasoningScore

Specificity

"parse/sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid the common footguns" lists four concrete actions comprehensively covering the library's sub-packages, matching the top anchor; no minor coverage gap is evident to place it at 4.

5 / 5

Completeness

The "what" is concrete and the "when" is explicitly present via "For developers using jwx, not for developing the library itself", but there is no explicit "Use when..." trigger phrase, so it matches the anchor where both exist yet "when" could be more specific.

4 / 5

Trigger Term Quality

Natural terms like "Go", "jwx v4", "JWT", "JWS/JWE/JWK", and "algorithms" are present, but spelled-out synonyms such as "JSON Web Token", "token", or "signing" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The named module path, the pinned version ("v4"), and the explicit negative scope ("not for developing the library itself") give it a clear niche with minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 12 missing

Warning

Total

15

/

16

Passed

Repository

lestrrat-go/jwx

Path

agents/plugin/skills/guide/SKILL.md

Reviewed

Table of Contents

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.