CLI for the Skylight Calendar private API.

Unofficial. Not affiliated with Skylight. Use with accounts you own.

skycli wraps a broad private-API surface: frames, categories, chores, rewards, calendar events, lists/grocery, meals, photos, routines, bounties, rotations, export/import, status, analytics, and watch.

• Agent instructions
• Command index
• Machine-readable command catalog: skycli commands --json

brew tap jwmoss/tap
brew install skycli

Or:

brew install jwmoss/tap/skycli

go install github.com/jwmoss/skycli@latest

git clone https://github.com/jwmoss/skycli ~/github/skycli
cd ~/github/skycli
make build
./skycli version

skycli auth login --email you@example.com
skycli frames list                   # find your frame ID
skycli frames set-default 5312425
skycli --doctor                      # verify token + connectivity
skycli categories                    # find category/person IDs
skycli chores list --json

The full command surface is documented under docs/commands.

• Auth
• Frames
• Chores
• Rewards
• Calendar
• Lists and grocery
• Meals, photos, and routines
• Reports, analytics, home, and watch
• Export, import, config, and raw HTTP

For scripts and agents:

skycli commands --json
skycli --json

Use one of the auth commands, then verify the account with skycli --doctor.

skycli auth login --email you@example.com
skycli auth import-mac
skycli auth set-token
skycli auth status --json

See auth docs for login, macOS import, token storage, and non-interactive usage.

Use skycli commands --json to discover the command surface and docs paths. Every bounded command supports --json; table-style commands also support --plain for stable TSV. Data goes to stdout, logs/errors to stderr. Exit codes: 0 success, 1 runtime error, 2 usage error. --trace-http emits one line per request to stderr without including the bearer token.

Global flags such as --json, --readonly, and --frame may appear before or after the command, before a literal --:

skycli chores list --json
skycli --json chores list
skycli chores list --readonly --json

Run real-account read-only integration checks with:

make live-readonly-smoke

make fmt
make test
make vet
make ci
make build
make live-readonly-smoke
make release-check
make release-snapshot

CI intentionally stays small: cross-platform go test, go vet, and go build. Release checks are separate so local development stays fast while tagged builds still validate the GoReleaser configuration and Homebrew formula generation path.

The GoReleaser version is pinned by GORELEASER_VERSION in Makefile and must match .github/workflows/release.yml. Before tagging, run:

make ci
make release-check
make release-snapshot

Tagging vX.Y.Z triggers GoReleaser to build release archives, publish GitHub release assets, and update the jwmoss/homebrew-tap formula. The release workflow needs a HOMEBREW_TAP_TOKEN secret with write access to that tap repository.

Early, unofficial, and private-API backed, with --body / --body-file available on several typed commands for fields that are discovered before first-class flags are added.

MIT