wendy-device-interop — Claude Code skill: what it does, how to install
This skill sets out how wendy-agent devices receive and verify changes from the SaaS stack. Use it when working on signed requests, device polling, or image delivery.
npx skills add wendylabsinc/claude-skills --skill wendy-device-interop -a claude-codeWhat wendy-device-interop does
The skill guides changes to the way wendy-agent communicates with the cloud queue and decides whether to apply an update. A device checks the operator’s signature, request freshness, and device binding itself; the cloud cannot push a state-changing command. Verification and apply results are recorded with a correlation_id for audit tracing.
When SaaS cannot be reached, the agent keeps its current state. It rejects artifacts or signatures it cannot verify. The device uses its own mTLS certificate, and images are meant to pass through wendy-proxy rather than come directly from a registry. The proxy is planned, not live, so image delivery through it is not ready. The skill also requires the stack to retain a self-hosted path and points to references/postbox-verification.md and references/image-pull.md.
What it helps with
- verify a change request before applying it
- design device polling for the cloud postbox
- handle stale checkpoints or SaaS outages
- define image delivery through
wendy-proxy
Example prompts for the agent
- Check whether our device polling follows
wendy-device-interop. - Explain how the device should validate a signed change request.
- What should the agent do when SaaS is unreachable or a checkpoint is stale?
How to install wendy-device-interop
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-interop -a claude-code2Manually: put the files in place
~/.claude/skills/wendy-device-interop/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wendy-device-interop/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-interop -a codex2Manually: put the files in place
.agents/skills/wendy-device-interop/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-interop -a cursor2Manually: put the files in place
.cursor/skills/wendy-device-interop/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wendylabsinc/claude-skills wendy-device-interop2Manually: put the files in place
.github/skills/wendy-device-interop/SKILL.md1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-interop -a gemini-cli2Platform CLI
gemini skills install https://github.com/wendylabsinc/claude-skills --path wendy-device-interopManually: put the files in place
.devin/skills/wendy-device-interop/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-device-interop -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-interop
How do I install wendy-device-interop in Claude Code?
Run npx skills add wendylabsinc/claude-skills --skill wendy-device-interop -a claude-code. The skill file is placed at ~/.claude/skills/wendy-device-interop/SKILL.md.
What does wendy-device-interop do?
It guides how a device receives and checks changes before applying them, records audit outcomes, and handles failures without accepting unverified material.
How are images pulled by the device?
The intended route is through wendy-proxy, with the device authenticating using its own mTLS certificate. The proxy is planned but not live yet.
