overthinkos/charly-version
core/skills/charly-version/SKILL.md
Show charly CLI version information. MUST be invoked before any work involving: charly version command or checking installed charly version. Named `charly-version` (not `version`) to disambiguate from Claude Code's built-in `/version` slash command.
tools
Updated Jun 14, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins charly-versionInstall 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 14, 2026, 5:47 AM194.9s1 file scanned
SKILL.md
- name:
- charly-version
- description:
- |
- MUST be invoked before any work involving:
- charly version command or checking installed charly version.
charly version -- CLI Version
Overview
Displays the installed version of the charly CLI binary.
Quick Reference
| Action | Command | Description |
|--------|---------|-------------|
| Show version | charly version | Print charly version string |
Usage
charly version
Testing Note
charly version writes the CalVer tag to stdout via fmt.Println.
Declarative tests should match stdout: — for example
candy/charly/charly.yml uses:
- id: charly-version
command: /usr/local/bin/charly version
exit_status: 0
stdout:
- matches: "[0-9]{4}\\.[0-9]+"
VersionCmd writes via fmt.Println (not Go's builtin println,
which bypasses os.Stderr and writes directly to fd 2) so the
in-process MCP tool-call path — which captures os.Stdout — surfaces
the version correctly. See /charly-check:check Authoring Gotcha #5 and
/charly-build:charly-mcp-cmd "Capture model" for the capture-pipeline detail.
Cross-References
/charly-core:charly-doctor-- Full host dependency and health check/charly-build:settings— runtime config wheresecret_backendand other settings live/charly-image:image— build-mode family that stamps CalVer tags matching this version/charly-check:check— declarative testing framework (Gotcha #5 covers the stdout rule)/charly-build:charly-mcp-cmd— MCP server section explains why the stream choice matters for the capture pipeline/charly-internals:go—charly/version.goCalVer computation;main.goVersionCmd.Runusingfmt.Println
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