Wiki Fold

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — USE REQUIREMENTS DISCLOSED FIRST: this skill works on your own Obsidian vault and runs through the portable core of the claude-obsidian repository, scripts/claude-obsidian.py, which lives at the repository root OUTSIDE this skill's folder, together with the shared contracts it links to (under skills/wiki/references/ in that same product root, for example the provenance and operation-transaction contracts). Installing this listing copies only this skill's folder: without a full claude-obsidian installation (the core, its contracts, python3 to run it, and a selected user vault) the skill cannot run its transactions as designed. The family orchestrator is the separate wiki skill of the same repository. No account, no key and no payment are needed to copy the files, and nothing is run during installation. This skill needs no network egress at use time, and its own text forbids calling external services. Install "Wiki Fold" for me. It creates a bounded, extractive rollup (a fold) of recent entries of your vault's wiki/log.md: by default a batch of 2^k entries with k=4 (16 entries), or an explicit entry range; if fewer entries exist than requested it reports the shortfall and stops rather than folding a partial batch. It never modifies, moves or deletes child entries or their pages, never performs fold-of-folds and never triggers automatically. The fold is drafted extractively under the bundled references/fold-template.md: every child entry gets one deterministic child_key, exactly one matching row in the Child Entries table, every outcome names its source entry, every number must be verifiable in its entry, and a cross-entry theme must name at least two contributing entries; missing pages stay explicit page_missing records, and disagreements between a child page and its log entry are preserved, the log entry being the primary source. A fold adds no new factual evidence: it upgrades no claim assessment and creates no source records. Preview is the default: it returns the complete draft, its structural ID (derived only from its inputs), the child range, the read budget (target 0-10 child-page reads, hard ceiling 15) and the proposed changed paths WITHOUT modifying the vault. Only when you explicitly say to apply or commit the fold does it build one claude-obsidian.transaction.v1 bundle of operation type fold coupling the new wiki/folds/{FOLD_ID}.md (create mode; an existing fold is a no-op, replacing it needs an explicit force request and a separately reviewed replace proposal), its catalog entry in wiki/index.md and one new entry in wiki/log.md, inspected first and applied once only with the approval hash (APPROVAL_SHA256 pattern). A Git checkpoint is a separate optional action, only when requested. Repository: https://github.com/AgriciDaniel/claude-obsidian (the skill is the whole skills/wiki-fold/ folder at the pinned commit: SKILL.md, references/fold-template.md, 2 files in total) Pinned version: install the code at commit 2e545563172f97f02ecaaaab376ceea1246a0583 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/AgriciDaniel/claude-obsidian into a temporary folder, check out commit 2e545563172f97f02ecaaaab376ceea1246a0583, and copy the skills/wiki-fold/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 df61e257eaaed9a3ea413af9cb5e27bc8b3f6bac04eff96565af484787bb823f - references/fold-template.md: SHA-256 9542a4a5c9b34f54458d01ac542039e2d893da03dbac061ff99f06d2b13b1111 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 2 files: SKILL.md and references/fold-template.md, the bundled fold page template it must follow (read in full for this listing). The core it runs (scripts/claude-obsidian.py) and the transaction contract it links to live outside this folder, in the full claude-obsidian product root. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, no log is read and no fold is drafted or applied. At use time it calls no external services and needs no network egress. - At use time the default is a dry-run preview that modifies nothing. A vault write happens only when I explicitly say to apply or commit the fold: one inspected transaction applied with the approval hash (APPROVAL_SHA256 pattern), creating wiki/folds/{FOLD_ID}.md plus its wiki/index.md catalog entry and one wiki/log.md entry. Child entries and pages are never modified, moved or deleted. - The fold is extractive and traceable: deterministic ID from its inputs, one table row per child entry, every number verifiable in its source entry, missing pages recorded as page_missing, and no claim is upgraded and no source record created by a fold. - Do not read any log, draft any fold or apply anything during this install: using it is a separate step that only starts when I ask for it later, and applying is a further explicit step after the preview. 3. When I say "yes, install", install it as a skill: copy the whole wiki-fold folder into the agent's skills directory, in a folder named exactly "wiki-fold", keeping its 2 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: wiki-fold), the 2 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that a full claude-obsidian installation (portable core and contracts at the product root) and my own Obsidian vault are required to use it, that preview is the default and nothing is written until I explicitly say to apply the fold, and that it makes no network calls). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.