overthinkos/arch-test
distros/skills/arch-test/SKILL.md
Test box for Arch Linux pacman and AUR package installation. MUST be invoked before building or troubleshooting the arch-test box.
development
Updated Jun 22, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins arch-testInstall 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: Jun 22, 2026, 6:33 AM121.2s1 file scanned
SKILL.md
- name:
- arch-test
- description:
- |
arch-test
Test box that validates both pac: (pacman) and aur: (AUR) package formats on Arch Linux. Used to verify the multi-distro build system handles Arch packaging correctly.
arch-test lives in the overthinkos/arch repo (git submodule at
box/arch). The test candies arch-pac-test / arch-aur-test are vendored
locally in this repo's candy/ (resolved via its discover: block); the arch
base + arch-builder are bare-local in the same self-contained submodule
(import: []) — base: arch. Build from
the submodule: cd box/arch && charly box build arch-test.
Box Properties
| Property | Value | |----------|-------| | Base | arch | | Build | pac, aur | | Layers | agent-forwarding, arch-pac-test, arch-aur-test | | Platforms | linux/amd64 | | Registry | ghcr.io/overthinkos |
What It Tests
pac:format (via arch-pac-test) — installsneovimandripgrepfrom official Arch reposaur:format (via arch-aur-test) — installsyay-binfrom the AUR using arch-builder
Quick Start
charly box build arch-test
charly shell arch-test
Verification
charly shell arch-test -c "nvim --version" # pac: package installed
charly shell arch-test -c "rg --version" # pac: package installed
charly shell arch-test -c "which yay" # aur: package installed
Related
/charly-distros:arch— base image/charly-distros:arch-builder— builder image (provides yay for AUR builds)/charly-distros:arch-pac-test— pacman test candy/charly-distros:arch-aur-test— AUR test candy
When to Use This Skill
MUST be invoked when the task involves building or troubleshooting the arch-test box, or validating Arch Linux package format support.
Related
/charly-image:image— image family umbrella (candy:image entries — those carryingbase:/from:— incharly.yml, build/validate/inspect/list)/charly-build:build— the embedded build vocabulary (distros, builders, init-systems)
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 14, 2026