Obsidian Bases

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. Version boundary disclosed in the skill: table and card views require Obsidian 1.9+, list 1.10+, native kanban 1.14+, and a map view requires the Maps plugin; these are documented minimums, not versions its offline tests exercised. Install "Obsidian Bases" for me. It explains, drafts and validates Obsidian Bases files (.base): YAML views over your vault notes with filters, formulas, properties, summaries and table, card, list or version-gated kanban views, for database-like vault views, reading lists and task trackers. Design and syntax questions are answered read-only: it inspects representative note properties and any existing .base file, defines the smallest filter selecting the intended notes, adds formulas only for values that must be computed, validates YAML, expression quoting, property names, formula references and null handling, and previews the complete file and expected result set. A requested .base EDIT is never written directly: the file stays under wiki/ in your vault and the change is built as one claude-obsidian.transaction.v1 bundle of operation type base, inspected first and applied once only with the approval hash (APPROVAL_SHA256 pattern), through the portable core. For detailed or version-sensitive fields it prefers a separately installed kepano/obsidian-skills obsidian-bases skill, then the current official Bases syntax documentation. One honesty caveat carried in its own text: date arithmetic has conflicting current source descriptions (milliseconds versus Duration), so its retained date formulas are unverified compatibility candidates, not guarantees, until tested in the user's app version. After an applied edit it reports the operation ID, exact changed path and validation performed, and never labels unobserved native rendering as tested. It does not commit Git. Repository: https://github.com/AgriciDaniel/claude-obsidian (the skill is the whole skills/obsidian-bases/ folder at the pinned commit: SKILL.md only, 1 file) 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/obsidian-bases/ 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 3cd5676434bc86618802e07cf44ff9c7a5d4c10fb7ecb412775b9fef9cfa82be 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 1 file only: SKILL.md, a compact workflow and fallback syntax reference. 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, and no .base file is drafted, validated or edited. - At use time, questions are read-only; a requested .base edit is written only as one inspected transaction applied with the approval hash (APPROVAL_SHA256 pattern), the file kept under wiki/ in my vault. Version gates from its text: table/cards need Obsidian 1.9+, list 1.10+, native kanban 1.14+, map needs the Maps plugin. - Its date-arithmetic formulas are explicitly unverified compatibility candidates in its own text (conflicting millisecond versus Duration descriptions); it must not assert them correct or rewrite existing formulas before a native check in my app version. - Do not draft or edit any .base file, do not run any transaction, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole obsidian-bases folder into the agent's skills directory, in a folder named exactly "obsidian-bases", keeping its single file (SKILL.md) at its root. 4. Verify with no network calls: frontmatter valid (name: obsidian-bases), the 1 file 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 .base edits go only through reviewed transactions under wiki/, and that its view types are gated by my Obsidian version (table/cards 1.9+, list 1.10+, kanban 1.14+)). 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.