← ClaudeAtlas

setuplisted

One-time onboarding - probes the machine, surveys the documents, grills the user, writes config.yaml, anchors the wiki in the instructions file, runs the first pass over the inboxes. Use when the workspace has no config.yaml yet, or the user asks to set up wikidoc.
smkg75/wikidoc · ★ 2 · Data & Documents · score 73
Install: claude install-skill smkg75/wikidoc
# Setup Run once in the life of an installation. The output: a `config.yaml` filled from evidence found in the user's own documents, instruction files that point at the wiki instead of duplicating it, and a first real pass already run over every configured inbox. Work in `$WIKIDOC_HOME` (default `~/.wikidoc`); create it if missing. Scripts live in `scripts/` at the plugin root (`scripts/` sits beside `skills/`, two levels up from this file); invoke them by absolute path. ## 1. PROBE Find out what this machine can do by trying it, not by assuming from the platform name. ```bash python3 -VV python3 -c "import importlib.util as u;print({m:bool(u.find_spec(m)) for m in ('yaml','pypdf','pypdfium2','send2trash','striprtf')})" ``` `yaml` is required (`python3 -m pip install --user pyyaml`; on a PEP 668 Python add `--break-system-packages`, or make a venv and use its interpreter). The others are optional: without the PDF libraries, PDFs go through vision; without `send2trash`, removal falls back to a workspace folder. A slower pass, not a wrong one. Then the filesystem, in the user's document root. **Count the cloud placeholders FIRST** — the other probes create empty files, and empty files are exactly what that count looks for: - **cloud placeholders** — `.icloud` files or zero-byte stand-ins: files that are not materialised have no bytes to classify. - **xattr round-trip** — write an extended attribute on a scratch file, read it back. Failure means `memory.jsonl` is the