scribe-clilisted

# scribe CLI — operations agent skill `scribe` is a single-binary Go CLI that runs a knowledge-base pipeline: discover repos → extract knowledge → mine agent sessions → absorb URLs → lint → reindex with qmd. It normally runs unattended on cron. This skill is for **driving the CLI by hand** — diagnosing health, running a step manually, and choosing the right command for a goal. Two sibling skills own the other halves and this skill routes to them: - **scribe-kb** — authoring/searching KB *content* (articles, drop files, qmd). - **scribe-kb-tidy** — working the `scribe lint` content-quality queue (split bloated, archive rolling, merge thin/self-named-dirs). ## Installation or bootstrap requests For zero-to-running setup, read the public, prompt-compatible runbook first: <https://getscribe.dev/setup.md>. It has separate command sequences for a personal Anthropic KB, local Ollama, a hosted OpenAI-compatible provider, the team owner, each team member, a second KB on one machine, and Linux cron. Follow one profile rather than mixing flags. Key distinctions the short command map cannot express: - Fresh/default KBs use `scribe init --path <kb> --bind`; `--bind` is what installs the machine-global Claude/Codex/Amp handshake. - Only the team owner uses `--team`, `--kb-name`, `--allow`, and `--provider`. Members clone, `cd` into the checkout, then run `scribe init --bind --yes`. - Quote a shared tilde path (`--allow '~/work'`) so the shell does not commit the owner's absol