wendy-device-enrollment — Claude Code skill: enrolling WendyOS devices
Walks your agent through first-touch enrollment of WendyOS devices in pki-core and the certificate lifecycle that follows.
npx skills add wendylabsinc/claude-skills --skill wendy-device-enrollment -a claude-codeWhat wendy-device-enrollment does
This skill is a reference the agent consults when a WendyOS device has to join pki-core. Three files ship with it: device tiers, first touch, and trusted time. Two first-boot paths are covered. With a network, the operator asks for a token while installing the OS, the cloud forwards the signed request to pki-core, and a single-use token bound to that device and tenant comes back. Airgapped, the machine links to the operator's computer, generates a CSR, and the operator carries a signed request to the cloud for a grant.
The keypair is created on the device itself and the private half stays there. A platform root travels inside the OS image, so the delivered chain gets checked against what was already flashed instead of being trusted on sight. Renewal runs unattended over ACME/EST, yet it only works while the current certificate is valid; an expired one needs a standing proof, such as re-attestation or an operator grant. When trusted time cannot be established, the device holds its state rather than guessing.
Any interop change must leave the self-hosted path intact, and the skill points to wendy-self-hosted for that. It distills AAA Contract v0.21; where the contract and the skill disagree, the contract is the one to follow. Have the hardware on your desk and pki-core reachable before you start.
What it helps with
- enroll a WendyOS device online at first boot
- run enrollment in an airgapped network via CSR
- work out device tiers and TPM, OP-TEE or eFuse attestation
- recover a device whose certificate has expired
- keep renewals automatic over ACME/EST
Example prompts for the agent
- Explain how to enroll a WendyOS device with pki-core over the network
- The device has no internet — how do I get the CSR and the operator grant?
- The cert expired; walk me through re-enrollment
How to install wendy-device-enrollment
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-enrollment -a claude-code2Manually: put the files in place
~/.claude/skills/wendy-device-enrollment/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wendy-device-enrollment/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-enrollment -a codex2Manually: put the files in place
.agents/skills/wendy-device-enrollment/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-enrollment -a cursor2Manually: put the files in place
.cursor/skills/wendy-device-enrollment/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wendylabsinc/claude-skills wendy-device-enrollment2Manually: put the files in place
.github/skills/wendy-device-enrollment/SKILL.md1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-enrollment -a gemini-cli2Platform CLI
gemini skills install https://github.com/wendylabsinc/claude-skills --path wendy-device-enrollmentManually: put the files in place
.devin/skills/wendy-device-enrollment/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-enrollment -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about wendy-device-enrollment
How do I install wendy-device-enrollment in Claude Code?
Run npx skills add wendylabsinc/claude-skills --skill wendy-device-enrollment -a claude-code. The skill lands at ~/.claude/skills/wendy-device-enrollment/SKILL.md.
What does wendy-device-enrollment do?
It gives the agent guidance on bringing WendyOS devices into pki-core: picking the online or airgapped flow, handling tokens, renewals, and recovery after a certificate expires.
Does it depend on the SaaS stack?
No. The wendy stack has to run without SaaS, and the skill tells you to consult wendy-self-hosted before touching interop code. A SaaS-only feature counts as unfinished.