coder/skills/rust/SKILL.md
Rust compiler and Cargo package manager via system packages (RPM/DEB). Use when working with Rust development or Cargo builds.
npx skillsauth add overthinkos/overthink-plugins rustInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Install files | charly.yml (packages only) |
PATH additions: ~/.cargo/bin
RPM: rust, cargo
DEB: rustc, cargo
# charly.yml
my-image:
candy:
- rust
language-runtimesrust candy vs the build-toolchain rust+cargo packagesTwo places now ship a Rust toolchain. Choose based on where you need it:
| Need | Use |
|------|-----|
| Rustc/cargo at runtime in the final container (developer shells, CI runners, on-the-fly cargo builds) | Add /charly-coder:rust to the runtime candies list of the box |
| Rustc/cargo at build time only, for compiling a cdylib that's copied into the final image (e.g., pixelflux_wayland) | Already provided by /charly-distros:fedora-builder via /charly-coder:build-toolchain's system rust+cargo packages — no extra candy needed |
Builder-stage cargo (the build-toolchain path) keeps the runtime image small because the toolchain stays in the multi-stage builder and never lands in the final layers.
/charly-coder:language-runtimes -- includes rust as a dependency/charly-coder:build-toolchain -- now also ships rust+cargo for builder-stage compilationUse when the user asks about:
rust candy/charly-image:layer — candy authoring reference (tasks, vars, env_provide, tests block syntax)/charly-check:check — declarative testing framework for the check: blocktools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).