← Back to Skills Marketplace
apetersson

KitchenOwl

by apetersson · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
610
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install kitchenowl
Description
Use kitchenowl-cli from terminal with pipx install, auth, and core read/write commands for KitchenOwl.
README (SKILL.md)

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

  1. Start with read-only commands before mutating data.
  2. Ask for confirmation before destructive commands (delete, remove-item, bulk edits).
  3. Prefer explicit IDs and --household-id for all scoped commands.
  4. 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
Usage Guidance
This skill is internally consistent with its purpose (install and use the KitchenOwl CLI). Before installing: review the kitchenowl-cli project (the metadata references a GitHub repo) to confirm it's the legitimate package; pipx installs code from PyPI so you should trust the package/maintainer. Be aware the CLI stores server_url, access_token and refresh_token in ~/.config/kitchenowl/config.json (or $XDG_CONFIG_HOME). If you provide credentials, plan to revoke tokens if you uninstall or no longer trust the package, and avoid using high‑privilege or shared credentials. If you want extra caution, inspect the package source or run it in a disposable environment before granting real credentials.
Capability Analysis
Type: OpenClaw Skill Name: kitchenowl Version: 1.0.0 The skill bundle is designed to install and operate the `kitchenowl-cli` using `pipx`. All commands and instructions are directly related to this stated purpose, including installation, authentication, and various command groups for managing KitchenOwl resources. The `SKILL.md` provides clear guidance to the AI agent, including best practices like asking for confirmation before destructive commands. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, prompt injection attempts to subvert the agent's purpose, or obfuscation. The storage of tokens in `~/.config/kitchenowl/config.json` is standard for CLI tools and not an instruction for exfiltration.
Capability Assessment
Purpose & Capability
Name/description state installing and using kitchenowl-cli; the skill declares the kitchenowl CLI binary and shows pipx install in the instructions and metadata. Required items (binary name, pipx install) are proportional to the purpose.
Instruction Scope
SKILL.md only instructs how to install, authenticate, and run read/write CLI commands. It documents that the CLI persists server_url, access_token, refresh_token, and user in ~/.config/kitchenowl/config.json, but does not direct the agent to read unrelated files or exfiltrate data to unexpected endpoints.
Install Mechanism
The skill recommends pipx install kitchenowl-cli (typical for Python CLIs). This installs third‑party code from PyPI into the environment — a normal mechanism but one that requires trusting the package source and maintainer.
Credentials
The skill requests no environment variables or unrelated credentials. The only sensitive data referenced are the CLI's access/refresh tokens stored in the user's XDG config path, which is expected for an auth'd CLI.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or modifications to other skills. It only instructs use of the CLI and does not attempt to change agent/system configuration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install kitchenowl
  3. After installation, invoke the skill by name or use /kitchenowl
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
initial version of the kitchenowl skill that enables agents to use kitchenowl-cli
Metadata
Slug kitchenowl
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is KitchenOwl?

Use kitchenowl-cli from terminal with pipx install, auth, and core read/write commands for KitchenOwl. It is an AI Agent Skill for Claude Code / OpenClaw, with 610 downloads so far.

How do I install KitchenOwl?

Run "/install kitchenowl" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is KitchenOwl free?

Yes, KitchenOwl is completely free (open-source). You can download, install and use it at no cost.

Which platforms does KitchenOwl support?

KitchenOwl is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created KitchenOwl?

It is built and maintained by apetersson (@apetersson); the current version is v1.0.0.

💬 Comments