overthinkos/rust
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.
development
Updated May 24, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins rustInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 24, 2026, 5:31 AM123.5s1 file scanned
SKILL.md
- name:
- rust
- description:
- |
rust -- Rust compiler and Cargo
Layer Properties
| Property | Value |
|----------|-------|
| Install files | layer.yml (packages only) |
PATH additions: ~/.cargo/bin
Packages
RPM: rust, cargo
DEB: rustc, cargo
Usage
# image.yml
my-image:
layers:
- rust
Used In Images
- No enabled images use this layer directly
- Transitive dependency of
language-runtimes(used inbazzite)
When to use the rust layer vs the build-toolchain rust+cargo packages
Two 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 /ov-coder:rust to the runtime layers list of the image |
| Rustc/cargo at build time only, for compiling a cdylib that's copied into the final image (e.g., pixelflux_wayland) | Already provided by /ov-distros:fedora-builder via /ov-coder:build-toolchain's system rust+cargo packages — no extra layer 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.
Related Layers
/ov-coder:language-runtimes-- includes rust as a dependency/ov-coder:build-toolchain-- now also shipsrust+cargofor builder-stage compilation
When to Use This Skill
Use when the user asks about:
- Rust compiler in containers
- Cargo builds or Rust development
- The
rustlayer
Author + Test References
/ov-image:layer— layer authoring reference (tasks, vars, env_provides, tests block syntax)/ov-eval:eval— declarative testing framework for theeval:block
Related Skills
overthinkos/agents
development
VerifiedTrustedCommunity
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
SKILL.mdUpdated May 31, 2026
overthinkos/workspace-mount
tools
VerifiedTrustedCommunity
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
SKILL.mdUpdated May 30, 2026
overthinkos/android
development
VerifiedTrustedCommunity
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
SKILL.mdUpdated May 26, 2026
overthinkos/git-workflow
tools
VerifiedTrustedCommunity
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.
SKILL.mdUpdated May 25, 2026