Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Security & Compliance
JWT
Implement secure JWT authentication with proper validation and token handling.
skill openclawclawhub Free
Implement secure JWT authentication with proper validation and token handling.
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, algorithms.md, attacks.md, lifecycle.md, validation.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Quick Reference
TopicFileAlgorithm selectionalgorithms.mdToken lifecyclelifecycle.mdValidation checklistvalidation.mdCommon attacksattacks.md
Security Fundamentals
JWTs are signed, not encrypted—anyone can decode and read the payload; never store secrets in it Always verify signature before trusting claims—decode without verify is useless for auth The alg: none attack: reject tokens with algorithm "none"—some libraries accepted unsigned tokens Use strong secrets: HS256 needs 256+ bit key; short secrets are brute-forceable
Algorithm Choice
HS256 (HMAC): symmetric, same key signs and verifies—good for single service RS256 (RSA): asymmetric, private key signs, public verifies—good for distributed systems ES256 (ECDSA): smaller signatures than RSA, same security—preferred for size-sensitive cases Never let the token dictate algorithm—verify against expected algorithm server-side
Required Claims
exp (expiration): always set and verify—tokens without expiry live forever iat (issued at): when token was created—useful for invalidation policies nbf (not before): token not valid until this time—for scheduled access Clock skew: allow 30-60 seconds leeway when verifying time claims
Audience & Issuer
iss (issuer): who created the token—verify to prevent cross-service token theft aud (audience): intended recipient—API should reject tokens for other audiences sub (subject): who the token represents—typically user ID Token confusion attack: without aud/iss validation, token for Service A works on Service B
Token Lifecycle
Access tokens: short-lived (5-15 min)—limits damage if stolen Refresh tokens: longer-lived, stored securely—used only to get new access tokens Refresh token rotation: issue new refresh token on each use, invalidate old one Revocation is hard—JWTs are stateless; use short expiry + refresh, or maintain blacklist
Storage
httpOnly cookie: immune to XSS, but needs CSRF protection localStorage: vulnerable to XSS, but simpler for SPAs Memory only: most secure, but lost on page refresh Never store in URL parameters—visible in logs, history, referrer headers
Validation Checklist
Verify signature with correct algorithm (don't trust header's alg) Check exp is in future (with clock skew tolerance) Check iat is not unreasonably old (optional policy) Verify iss matches expected issuer Verify aud includes your service Check nbf if present
Common Mistakes
Storing sensitive data in payload—it's just base64, not encrypted Huge payloads—JWTs go in headers; many servers limit header size to 8KB No expiration—indefinite tokens are security nightmares Same secret across environments—dev tokens work in production Logging tokens—they're credentials; treat as passwords
Key Rotation
Use kid (key ID) claim to identify which key signed the token JWKS (JSON Web Key Set) endpoint for public key distribution Overlap period: accept old key while transitioning to new After rotation, old tokens still valid until they expire—plan accordingly
Implementation
Use established libraries—don't implement JWT parsing yourself Libraries: jsonwebtoken (Node), PyJWT (Python), java-jwt (Java), golang-jwt (Go) Middleware should reject invalid tokens early—before any business logic
Category context
Identity, auth, scanning, governance, audit, and operational guardrails.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
5 Docs
- SKILL.md
- algorithms.md
- attacks.md
- lifecycle.md
- validation.md