← ClaudeAtlas

jotbook-pencillisted

Render one or more jots — or a fresh subject, which is staged as a jot first — into a provisional long-form draft (a "pencil") for later evaluation. Source jots are preserved and no cross-links are written — promotion happens later via `/jotbook-pencil-review`.
koloskus/jotbook · ★ 0 · DevOps & Infrastructure · score 72
Install: claude install-skill koloskus/jotbook
# Pencil a jot into a provisional draft You're producing the long-form version of a jot (or merged jots) for later evaluation. A pencil is a draft: it lives in `pencils_dir`, the source jot(s) stay in `jots_dir`, and no cross-links into existing entries are written. Promotion to a finished entry happens later, via `/jot review pencils`. ## Resolve configuration Read `.claude/jotbook.local.md` if present. From the frontmatter, extract: | field | default | meaning | |---|---|---| | `jots_dir` | `docs/jotbook/_jots/` | where staged jots live | | `pencils_dir` | `docs/jotbook/_pencils/` | where pencils are written | | `output_format` | `markdown` | global output mode — informs cross-link style but does NOT change a pencil's format unless `--html` is passed | | `template_path` | (none) | path to an HTML template — required when `--html` is passed | The **body** of the settings file (everything after the closing `---`) is optional house-style guidance — voice, tone, conventions, terminology. If present, treat it as authoritative for stylistic decisions. If `pencils_dir` does not exist, create it — but first briefly note to the user what you're doing and why, e.g. *"Creating `<pencils_dir>` to hold pencil drafts (first time penciling in this project, or the directory was renamed in settings)."* This avoids a context-free mkdir prompt. ## Inputs - One or more jot slugs from the user's invocation (single slug, or comma-separated to consolidate into one pencil). The argument ca