coder/skills/claude-code/SKILL.md
Claude Code CLI installed globally via npm from @anthropic-ai/claude-code. Use when working with Claude Code, AI coding assistants, or Anthropic tooling.
npx skillsauth add overthinkos/overthink-plugins claude-codeInstall 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 |
|----------|-------|
| Dependencies | nodejs |
| Install files | charly.yml, task: |
PATH additions: ~/.local/bin
# charly.yml
my-dev:
candy:
- claude-code
/charly-coder:nodejs -- required dependency (provides npm)/charly-coder:codex, /charly-coder:gemini — sibling AI CLIs (all three share the npm-global install pattern)/charly-hermes:hermes-full-layer — metalayer that bundles this with codex, gemini, dev-tools, devops-tools/charly-hermes:hermes — primary box that ships this CLI/charly-image:layer — candy authoring reference/charly-check:check — declarative testing framework (this candy's test verifies ${HOME}/.npm-global/bin/claude + claude --version)Use when the user asks about:
claude-code candytools
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).