wendy-contributing
by Joanniswendy-contributing is a practical guide for contributing to WendyOS, covering Yocto builds, wendy-agent internals, E2E testing, and device-specific OS behavior. Use it for wendy-contributing usage when you need help with meta-wendyos layers, bitbake recipes, mDNS/Avahi, device identity, or wendy-contributing for Backend Development.
This skill scores 78/100, which means it is a solid listing candidate for users working on WendyOS contributions. The repository gives enough real workflow guidance to help an agent trigger the skill correctly and act with less guesswork than a generic prompt, though users should still expect some manual navigation because the repo relies on one SKILL.md file and linked references rather than packaged helper assets.
- Strong triggerability: the description names concrete use cases like Yocto builds, wendy-agent internals, E2E testing, and mDNS/Avahi configuration.
- Operationally useful content: the body covers WendyOS architecture, agent behavior, and Yocto image targets for Jetson, VM, and Raspberry Pi.
- Good install decision signal: valid frontmatter, no placeholder markers, substantial body length, and repo/file references suggest a real working skill rather than a stub.
- No install command or support files are provided, so adoption depends on reading the markdown and any referenced docs.
- Experimental/test signal in the repository context suggests users should treat the skill as contributor-focused rather than a polished end-user workflow guide.
Overview of wendy-contributing skill
wendy-contributing is a focused guide for people contributing to WendyOS and its surrounding tooling, especially when the task touches Yocto builds, wendy-agent, E2E tests, or platform-specific OS behavior. It helps you move from “I need to change something in WendyOS” to the exact repo areas, build flow, and validation steps that matter.
Who this skill is for
Use the wendy-contributing skill if you are working on WendyOS images, meta-wendyos layers, bitbake recipes, bbappend changes, agent internals, or service behavior like mDNS/Avahi and device identity. It is especially relevant for wendy-contributing for Backend Development when backend work depends on how the OS packages, runs, or exposes services.
What it helps you do
The real job-to-be-done is not general Linux help; it is making safe, reviewable changes in a constrained embedded OS stack. The skill helps you understand how WendyOS is assembled, how wendy-agent behaves, and how to validate changes before you assume they are correct.
What makes it different
Unlike a generic prompt, wendy-contributing gives you an opinionated path through the work: architecture first, then build system, then testing. That matters because Yocto and agent changes often fail for reasons that are invisible from the code you initially touched.
How to Use wendy-contributing skill
Install and point it at the right task
Install the wendy-contributing skill with npx skills add Joannis/claude-skills --skill wendy-contributing. Then use it when your request can be expressed as a WendyOS contribution task, not as a broad “explain Linux” request.
Give it the right input shape
Strong input describes the target area, device class, and desired outcome. For example: “Update the meta-wendyos-rpi recipe so wendy-agent starts with a new environment variable on Raspberry Pi 5, and tell me what to test in the image.” That is much better than “fix startup.”
Read the source in the right order
Start with SKILL.md, then inspect the referenced yocto-meta-layers.md, system-internals.md, and raspberry-pi.md files if present in the skill package. Those paths tell you whether the change is about layer selection, runtime behavior, or device-specific constraints.
Use a WendyOS-aware workflow
A good wendy-contributing usage flow is: identify the subsystem, confirm the target layer or service, draft the smallest change, then ask for the relevant build or E2E check. For backend-adjacent work, include how the OS-side behavior should affect API calls, container lifecycle, or service discovery so the output stays grounded in the actual runtime.
wendy-contributing skill FAQ
Is wendy-contributing only for OS engineers?
No. It is useful for backend, platform, and infrastructure developers who need to understand how WendyOS behaves at runtime or how their service depends on the OS packaging. If your change crosses app code and device behavior, this skill is a good fit.
When should I not use it?
Do not use wendy-contributing for generic Yocto tutorials, unrelated Linux administration, or ordinary application debugging that has no WendyOS dependency. If the problem is outside the WendyOS build, agent, or device stack, a general prompt is usually enough.
Is this better than asking a model directly?
Yes, when the task depends on WendyOS-specific conventions. The wendy-contributing guide reduces guesswork about image targets, agent behavior, and validation expectations, which is where generic prompts often become vague or incomplete.
Is it beginner-friendly?
It is beginner-friendly if you can describe a concrete change request and you are willing to read the linked context files before editing. It is less helpful if you need a full embedded Linux introduction from scratch.
How to Improve wendy-contributing skill
Provide the exact target and platform
The best results come when you specify the platform, such as Jetson, Raspberry Pi 4/5, or ARM64 VM, plus the layer or component you expect to touch. “Fix service startup on edgeos-rpi-image” is more actionable than “make it work on WendyOS.”
Include observable success criteria
Tell the skill what “done” looks like: boot succeeds, the agent exposes gRPC on port 50051, an E2E test passes, or a package appears in the image. This helps wendy-contributing prioritize validation instead of only suggesting code edits.
Share constraints early
If you have a limited build environment, no access to hardware, or a requirement to avoid image size growth, say so up front. Those constraints materially change the best wendy-contributing usage path and the recommended test strategy.
Iterate from build to runtime
After the first answer, refine with build logs, failing test output, or the exact file you changed. The most useful follow-up prompts ask for the next diagnostic step, the likely cause, or the minimal fix rather than a broad re-explanation of the whole system.