メニュー
Use this when you need to install, run, or understand the `solo2` command-line tool — listing devices, updating firmware, or driving the on-device apps (admin, FIDO, OATH, PIV, NDEF). Use it whenever a task involves talking to a Solo 2 key from the host.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use this to build and flash custom firmware onto a Solo 2 Hacker key — including checking the lock/seal state (Secure vs Hacker, which is the PFR seal field, not secure boot), matching the build to the key's storage mode, and validating the equivalent build on an EVK first. Use it WHENEVER you are about to write firmware to a physical Hacker key, because a bad flash bricks it permanently.
Use this to find the right tested, hands-on tutorial for doing something real with a Solo 2 key — passkeys, SSH, git signing, file/disk encryption, TOTP/HOTP, password stores, or post-quantum signing. Use it when a user asks "how do I use my Solo for X" or when recommending a concrete workflow.
SOC 職業分類に基づく
| name | solo2-cli |
| description | Use this when you need to install, run, or understand the `solo2` command-line tool — listing devices, updating firmware, or driving the on-device apps (admin, FIDO, OATH, PIV, NDEF). Use it whenever a task involves talking to a Solo 2 key from the host. |
solo2 CLIsolo2 is the host tool for Solo 2 keys. Source is in cli/; run solo2 --help (or cargo run -- --help) for the authoritative, version-specific surface.
cargo install solo2 # installs the `solo2` binary
solo2 list # list connected devices (alias: solo2 ls)
cargo run -- list # run from this repo without installing
Linux: install the udev rule cli/70-solo2.rules; the CCID apps (OATH/PIV/OpenPGP) need a PC/SC stack (pcscd). macOS/Windows have PC/SC built in. FIDO is plain USB-HID (no driver).
solo2 list — enumerate keys (shows UUID, firmware version, locked/unlocked).solo2 update [--dry-run] [--yes] [--all] [--with <file.sb2>] — install the latest SoloKeys-signed firmware; downloads, verifies SHA-256, flashes. Prompts on major updates. --with flashes a specific .sb2.solo2 app <APP> … — talk to an on-device application (below).solo2 bootloader {list|reboot} — interact with keys in bootloader mode.solo2 pki ca fetch-certificate <R1|T1|S3|…> — fetch Solo 2 PKI certs.solo2 completion {bash|fish|zsh|powershell} — shell completions.infer_subcommands is on, so unambiguous prefixes work (e.g. solo2 app fido i → init).
solo2 app …)wink (blink LED to identify), version, uuid, locked (Secure=locked / Hacker=unlocked), maintenance (reboot into LPC55 bootloader), restart (reboot as Solo 2), aid.init, wink. (Credential create/assert is done by a FIDO2 client/browser; see the solo2-examples skill.)register (positional args or --uri), list, totp/hotp, delete <label>, rename, reset, aid. TOTP/HOTP secrets stored on the key.data, capabilities, aid (tap-to-URL).solo2 app admin wink before destructive ops; target a specific key with the device selector flags (solo2 --help).solo2 app admin locked is the quick way to tell a Secure key (locked) from a Hacker (unlocked).flash-solo-hacker skill.examples/ — see the solo2-examples skill.