tools/skills/himalaya/SKILL.md
Himalaya email CLI (IMAP/SMTP). Use when working with the himalaya candy.
npx skillsauth add overthinkos/overthink-plugins himalayaInstall 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 (run: step) |
| Depends | rust |
# box charly.yml — name-first: compose the candy via a child node
my-box:
candy:
base: fedora
my-box-candy:
candy:
- himalaya
openclaw-full (via openclaw-full metalayer)/charly-coder:rust — required Rust toolchain dependency/charly-openclaw:openclaw-full — metalayer that includes himalaya/charly-infrastructure:gnupg — pairs with himalaya for PGP-encrypted email/charly-build:secrets — provision IMAP/SMTP credentials for himalaya/charly-core:shell — run himalaya interactively inside a container/charly-build:build — compiles himalaya via the Cargo builder during image buildUse when the user asks about:
himalaya candy/charly-image:layer — candy authoring reference (charly.yml schema, plan-step verbs, service declarations)/charly-check:check — declarative testing (check: block, charly check box, charly check live)tools
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).