jotlisted

# /jot Toolkit dispatcher for granular jotbook actions. This skill runs **only** in response to an explicit `/jot ...` slash command from the user. Never auto-invoke it. (Auto-staging after substantive explainers is the `jotbook-stage` skill's job, not this one.) Parse the user's invocation text immediately after `/jot`. Treat the first whitespace-separated token as the subcommand and the remainder as its arguments. Route as follows: - **`review`** → look at the next token: - If empty or `jots`, invoke the `jotbook-review` skill. - If `pencils`, invoke the `jotbook-pencil-review` skill. - Anything else: ask the user to clarify (`jots` or `pencils`). - **`ink`** → invoke the `jotbook-ink` skill. Pass the rest of the arguments as the jot slug (or comma-separated slugs). - **`pencil`** → invoke the `jotbook-pencil` skill. Pass the rest of the arguments as the jot slug or subject (single, or comma-separated slugs). The argument need not match an existing jot — `jotbook-pencil` will stage one first when given a fresh subject. Recognize an optional `--html` flag anywhere in the remaining arguments and forward it. If `pencil` is invoked with no argument at all, do NOT default — instead, tell the user the two valid forms (`/jot pencil <slug>` to draft, `/jot review pencils` to review the pencil backlog) and stop. - **`init`** → invoke the `jotbook-init` skill. The skill writes the starter settings file and handles the `.gitignore` prompt. - **`link`** → invoke the `jotbook-l