wendy
by Joanniswendy skill guide for building, deploying, and managing apps on WendyOS edge devices. Use it for wendy install, wendy usage, device discovery, Swift app deployment, remote debugging on ARM64, and workflows for NVIDIA Jetson or Raspberry Pi 4/5. Best when you need structured, JSON-first CLI steps instead of guesswork.
This skill scores 79/100, which means it is a solid listing candidate for directory users who need WendyOS-specific help. The repository gives enough trigger guidance and workflow detail to help an agent act with less guesswork than a generic prompt, though users should still expect some dependence on WendyOS command behavior rather than a fully self-contained toolchain.
- Explicit trigger scope for Wendy/WendyOS, wendy CLI, wendy.json, edge deployment, Swift ARM64 debugging, and Jetson/Raspberry Pi use cases.
- Operational guidance includes concrete commands like `wendy --experimental-dump-help`, `wendy run`, `wendy init`, and device/network management flows.
- Frontmatter is valid and the body is substantial, with multiple headings and no placeholder markers, suggesting real workflow content rather than a stub.
- No install command, support files, or referenced companion docs were found, so adoption depends mostly on the single SKILL.md file.
- The file excerpt shows the `wendy init` section cut off in the preview, so users may still need to inspect the full skill for completeness and edge-case handling.
Overview of wendy skill
What the wendy skill is for
The wendy skill helps you work with WendyOS edge devices through the wendy CLI, from initial setup to deployment and remote management. It is best for developers who need a practical Wendy guide for creating projects, running apps, discovering devices, and pushing changes to supported hardware.
Who should use it
Use the wendy skill if you are targeting NVIDIA Jetson or Raspberry Pi 4/5 devices, or if you are developing on ARM64/AMD64 VMs before deploying to WendyOS hardware. It is also useful when you need a deployment workflow for Swift apps on edge devices and want fewer guesses about the right CLI commands.
What makes it different
Unlike a generic prompt about embedded deployment, the wendy skill is centered on the wendy toolchain and its JSON-driven command style. That matters if you want structured output, fewer interactive prompts, and a workflow that maps cleanly from local development to device deployment.
How to Use wendy skill
Start with the right install context
Use the skill in a repo where the task is clearly about WendyOS, device setup, or app deployment. If you are using a skill manager, install wendy with the repository path that points to the skill folder, then load the skill before asking for commands, device steps, or deployment advice. For best results, keep the prompt focused on one goal such as wendy install, wendy usage, or wendy for Deployment.
Give wendy the inputs it needs
The wendy skill works best when you provide the target device, app type, and your current stage. A strong request looks like: “I have a Swift app for a Raspberry Pi 5 on WendyOS. Show the wendy commands I need, the expected wendy.json fields, and the safest deploy workflow.” A weak request is just “help me deploy,” because it leaves the skill to infer hardware, project shape, and output format.
Read the core files first
Start with SKILL.md, then inspect any linked wendy.json.md reference before trying commands. If your local copy includes only the skill file, treat that as the source of truth for supported workflows: wendy init, wendy run, wendy discover, device WiFi setup, agent update, and OS install. For usage clarity, confirm whether the task expects JSON output, since the skill explicitly prefers structured command output to avoid interactive dialogs.
Use a workflow that matches deployment
A reliable pattern is: define the device target, run discovery, confirm the device state, create or validate wendy.json, then execute the relevant command with JSON output enabled. If you are asking for a deployment plan, say whether you need first-time setup, repeatable CI-style deployment, or remote debugging on ARM64. That distinction changes the command sequence and the amount of device prep required.
wendy skill FAQ
Is wendy only for WendyOS?
Yes, the wendy skill is specifically for WendyOS and its device workflow. If your project is not targeting WendyOS, a generic deployment prompt or another platform-specific skill will usually fit better.
Do I need to know the wendy CLI already?
No, but you should know your target hardware and what you want done. The wendy skill is useful for turning a rough goal into exact wendy usage steps, especially when you need to avoid interactive command behavior or guesswork around flags.
When should I not use the wendy skill?
Do not use it for general embedded Linux advice that has nothing to do with WendyOS, or for deployment systems that do not use the wendy CLI. It is also a poor fit if you only need a high-level conceptual overview and do not intend to run commands.
Is it good for beginners?
Yes, if the beginner already has a WendyOS target in mind. The skill is practical, but it assumes you can name the device class, project language, and deployment goal so the output can be specific instead of generic.
How to Improve wendy skill
Give the skill a concrete deployment target
The fastest way to improve output is to specify the exact device and environment: Jetson production device, Raspberry Pi test unit, or VM used for development. The wendy skill can then narrow the workflow, avoid irrelevant steps, and focus on the right install or deploy path.
Include your project shape and constraints
Tell the skill whether you are starting from scratch, updating an existing Wendy Lite project, or integrating Wendy into a Swift app. Also mention constraints like “must be non-interactive,” “needs JSON output,” or “must work over remote debugging on ARM64.” Those details materially change the commands and help the wendy guide avoid unsafe assumptions.
Ask for the missing pieces, not just commands
If your first result is too broad, ask for the exact wendy.json fields, the smallest valid wendy init flow, or the wendy run sequence for your device. For deployment work, the best follow-up is usually a check on prerequisites, device discovery, and whether the app package or entitlement settings need adjustment.
Iterate using one failure at a time
When wendy output does not work, report the exact command, the device type, and the error text. Then ask for a corrected command or a minimal repro path. That produces better results than asking for a full rewrite, because the skill can target the blocking step instead of re-explaining the whole WendyOS process.