wendy-contributing — Claude Code skill: what it does, how to install
Guides contributors building WendyOS Yocto images, configuring agent internals, and running end-to-end integration tests.
npx skills add wendylabsinc/claude-skills --skill wendy-contributing -a claude-codeWhat wendy-contributing does
This skill acts as a contributor reference for WendyOS, an embedded Linux system targeting edge hardware like NVIDIA Jetson, Raspberry Pi boards, and ARM64 emulation targets. It explains the setup of layers like meta-wendyos-jetson or meta-wendyos-rpi, along with running bitbake targets through bootstrap scripts or Docker environments on macOS.
It also details the internal architecture of wendy-agent, a gRPC daemon on port 50051 that receives deployments directly from source code instead of standard registries. A dedicated section covers Swift integration suites in E2ETests/. Standard GitHub Actions runners do not support nested virtualization, so testing VM workloads requires local hardware or self-hosted instances.
What it helps with
- Build WendyOS target images using bitbake and meta layers
- Configure Swift E2E test suites with fast-path execution
- Debug containerd daemon workflows and gRPC control sockets
- Prepare virtual development environments for local edge testing
Example prompts for the agent
- Show me how to compile the edgeos-image layer for NVIDIA Jetson targets
- Run the wendy-agent Swift integration test suite against my active VM
- Explain how container deployments work via the wendy run CLI
How to install wendy-contributing
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-contributing -a claude-code2Manually: put the files in place
~/.claude/skills/wendy-contributing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wendy-contributing/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-contributing -a codex2Manually: put the files in place
.agents/skills/wendy-contributing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-contributing -a cursor2Manually: put the files in place
.cursor/skills/wendy-contributing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wendylabsinc/claude-skills wendy-contributing2Manually: put the files in place
.github/skills/wendy-contributing/SKILL.md1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-contributing -a gemini-cli2Platform CLI
gemini skills install https://github.com/wendylabsinc/claude-skills --path wendy-contributingManually: put the files in place
.devin/skills/wendy-contributing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill wendy-contributing -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-contributing
How to install wendy-contributing in Claude Code?
Run npx skills add wendylabsinc/claude-skills --skill wendy-contributing -a claude-code in your terminal. The configuration writes directly to ~/.claude/skills/wendy-contributing/SKILL.md.
What does wendy-contributing do?
It gives your coding agent practical context on WendyOS internals, covering Yocto compilation targets, device agent architecture, and VM test execution.
Why is the E2E_USE_EXISTING_VM variable needed during testing?
Setting E2E_USE_EXISTING_VM=true prevents redundant virtual machine health probes, dropping individual test runtimes significantly.