lemoncrowlisted

# LemonCrow Thin pass-through to the real `lc` CLI (already built, already validated) — `lc agent` / `lc skill` / `lc set` / any other documented subcommand. Run the right CLI command, relay its output. Never invent cost numbers, validation, or confirmation logic here; the CLI already owns all of that. Not the cross-host bulk installer (`lc install optionals` is CLI-only, never called from this skill). ## Resolve your host first — every invocation From your own runtime, not by asking the user and not by letting the CLI auto-detect: - Running inside Claude Code → `--host claude` - Running inside Codex CLI → `--host codex` - Running inside Antigravity → `--host antigravity` (skills only — there is no `lc agent` subcommand there; skip straight to `lc skill ...` below) Global scope by default. Add `--workspace <dir>` only if the user names a specific workspace/repo distinct from the current one. ## Operating loop 1. Parse the user's message into an action — `install` / `remove` / `list` / `set` / other CLI verb — and its argument. 2. **`list`** (no name to resolve): run both, show both outputs as-is: ```bash lc agent list --host <host> lc skill list --host <host> ``` User said "agents" or "skills" specifically → run only that one. 3. **`install <name>` / `remove <name>`** — the user does not say whether `<name>` is an agent or a skill; don't ask. Try agent first, fall back to skill on failure: ```bash lc agent <install|remove> <name> --host <host>