Skills kitchenowl-cli

Use kitchenowl-cli from terminal with pipx install, auth, and core read/write commands for KitchenOwl.

install

source · Clone the upstream repo

git clone https://github.com/openclaw/skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/apetersson/kitchenowl" ~/.claude/skills/clawdbot-skills-kitchenowl-cli && rm -rf "$T"

manifest: skills/apetersson/kitchenowl/SKILL.md

source content

KitchenOwl CLI Skill

Use this skill when the user wants to install and operate KitchenOwl via the

kitchenowl

CLI.

Install and verify

Prefer

pipx

for isolated CLI installs.

pipx install kitchenowl-cli
kitchenowl --help
kitchenowl --version

Upgrade:

pipx upgrade kitchenowl-cli

Authentication

kitchenowl auth login --server https://kitchenowl.example.com
kitchenowl auth status
kitchenowl auth logout

auth login

accepts

--username

and

--password

flags (or prompts interactively) and always asks for the server when

--server

is omitted, defaulting to the last saved host. The CLI stores

server_url

access_token

refresh_token

user

, and any saved defaults in

~/.config/kitchenowl/config.json

(or

$XDG_CONFIG_HOME/kitchenowl/config.json

auth logout

removes the tokens from that file but leaves the configured server URL.

Command usage rules

Start with read-only commands before mutating data.
Ask for confirmation before destructive commands (
```
delete
```
,
```
remove-item
```
, bulk edits).
Prefer explicit IDs and
```
--household-id
```
for all scoped commands.
Use
```
--json
```
whenever output is consumed programmatically.

Core command groups

Use

references/commands.md

as the canonical command set for:

auth
config/server settings
households and members
shopping lists
recipes
users