Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Implement WebAuthn passkeys avoiding critical security and compatibility pitfalls.
Implement WebAuthn passkeys avoiding critical security and compatibility pitfalls.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
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.
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.
Challenge must be unique per ceremony โ reused challenges enable replay attacks Origin validation is mandatory โ missing check allows phishing from similar domains Store and verify sign count โ detects cloned authenticators when count doesn't increment Never implement CBOR parsing manually โ use established libraries, crypto is hard
Use battle-tested libraries โ SimpleWebAuthn (JS), py_webauthn (Python), webauthn-rs (Rust) Challenges expire quickly โ 60-120 seconds max, store server-side Store credential ID as base64 โ binary data, needs encoding for database Store public key in COSE format โ libraries handle this, don't transform it
Credential ID โ unique identifier, used in allowCredentials Public key โ COSE format, for signature verification Sign count โ integer, increment check detects cloning Transports hint โ helps browser suggest correct authenticator
userVerification: "required" enforces biometric/PIN โ "preferred" may skip verification Attestation usually unnecessary โ requiring it reduces device compatibility Allow multiple passkeys per account โ users have multiple devices Resident key capability varies โ don't assume all authenticators support discoverable credentials
Empty allowCredentials enables discoverable credentials โ but not all passkeys are discoverable Timeout too short frustrates users โ 120 seconds minimum for cross-device flows Cross-device auth (QR code) adds latency โ don't timeout during Bluetooth handshake
Provide password fallback โ not all users have passkey-capable devices Conditional UI (mediation: "conditional") for autocomplete โ passkeys appear in username field Clear messaging on registration โ users don't understand "security key" terminology Account recovery path required โ hardware loss shouldn't lock out account forever
Apple iCloud Keychain syncs across Apple devices โ but not to Android/Windows Google Password Manager syncs Android + Chrome โ but not to Apple devices Windows Hello is TPM-backed, local by default โ doesn't sync 1Password/Bitwarden provide cross-platform sync โ broadest compatibility option
Chrome DevTools > Application > WebAuthn โ simulate authenticators without hardware Virtual authenticators in CI โ no physical keys needed for automated tests Test both resident and non-resident credentials โ different flows Cross-browser testing essential โ Safari, Chrome, Firefox implementations vary
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.