Wiki Fold Skill for Claude
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit the fold.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/AgriciDaniel/claude-obsidian --skill wiki-foldThe instruction itself
4 sections, as written by the authorExtractive log fold
Create an additive rollup of raw wiki/log.md entries. Never modify, move, or
delete child entries or their pages. Do not perform fold-of-folds or trigger a
fold automatically.
Resolve the portable core from this skill's installation. Resolve the user vault
by explicit --vault, CLAUDE_OBSIDIAN_VAULT, workspace config, then
current-directory discovery. Never treat the plugin/product root as a vault.
PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
test -f "$CORE"
This skill needs no network egress. Do not call external services.
Select a bounded range
Use batch exponent k with size 2^k; default to k=4. An explicit entry range
may override it. If fewer entries exist than requested, report the shortfall and
stop rather than folding a partial batch.
Read the selected log entries completely. Read referenced child pages only when
the log lacks enough context: target 0-10 reads, hard ceiling 15. Missing pages
remain explicit page_missing records.
Derive the structural ID only from inputs:
fold-k{K}-from-{EARLIEST-DATE}-to-{LATEST-DATE}-n{COUNT}
If wiki/folds/{FOLD_ID}.md already exists, return a no-op. Replacing it requires
an explicit force request and a separately reviewed replace proposal.
Draft extractively
Follow fold-template.md. Every child log entry must
have one deterministic child_key in frontmatter and exactly one matching row
in the Child Entries table. Do not deduplicate children by page, although the
final Child Pages link list may be deduplicated.
Every outcome must name its source entry. Every number must be verifiable in the
selected entry. A cross-entry theme must name at least two contributing entries.
Prefer ambiguous in source or source missing to invention. When a child page
and log entry disagree, preserve both and identify the mismatch; the log entry is
the fold's primary source.
Run these checks before proposing any write:
- deterministic ID and exact entry count;
- frontmatter/table bijection;
- numeric traceability;
- source citation for every outcome and theme;
- no change to a child, source, source ledger, or claim ledger.
A fold adds no new factual evidence, so it does not upgrade claim assessments or
create source records. Report discovered contradictions for later review instead
of editing canonical claims.
Preview by default
Return the complete fold draft, ID, child range, read budget, and proposed changed
paths without modifying the vault. Parallel agents may check child entries and
return extracts, but only the orchestrator assembles the fold; workers never
write.
When the user explicitly says to apply or commit the fold, build one
claude-obsidian.transaction.v1 bundle with operation_type: fold. Read
the transaction contract. Couple:
wiki/folds/{FOLD_ID}.mdincreatemode by default;- the fold catalog entry in
wiki/index.md; - one new top-of-file fold entry in
wiki/log.md.
Do not update wiki/hot.md. Record SHA-256 preconditions for all three targets.
Do not use host Write/Edit, Obsidian transport writes, deprecated locks, automatic
commits, or one apply per file.
Inspect before the single apply:
python3 "$CORE" transaction inspect /path/to/fold-bundle.json --vault /path/to/vault
# Set APPROVAL_SHA256 to the inspect result's approval_sha256 after review.
python3 "$CORE" transaction apply /path/to/fold-bundle.json --vault /path/to/vault \
--approved-plan-sha256 "$APPROVAL_SHA256"
Report the operation ID and exact changed paths. The identical bundle and ID are
idempotent. On exit 75, re-read and rebuild; after interruption, use
transaction recover.
Git history is a separate optional action:
python3 "$CORE" checkpoint OPERATION_ID --vault /path/to/vault
Observe all selected entries, verify traceability and counts, then grow the
rollup only from what its children actually say.
Other skills for the same job
different authors, same section of the catalogue
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
How to use it
Take agricidaniel/wiki-fold from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.