Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views.
SkillScore87Maintained
Automatic
◆Knowledge Management pack
Last verified 9/20/2026
What it changes
Passed 18 of 21 test cases with the skill, and 9 of 21 without it.
Without skill43%
With skill87%
Checks it passed that the model alone missed
Identifies cards as a standard Base view type
Configures column sequence using the order key
Sets human-readable column titles using displayName
and 14 more in the full report
11 fixed9 passed either way2 still failing1 broke
Pass-rate lift
+43 pp
Tokens
+16%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 9/20/2026v220 of 23 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
When generating a transaction bundle to create or edit a Base file in the vault, which subfolder relative to vault root should store the file, and what operation_type field value should be used?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies placing .base files inside the wiki/ folder
Missed
Passed
Sets operation_type to base in the transaction bundle
Missed
Passed
case-12 · gemini-3.6-flash · 9/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md141 linessingle file
Obsidian Bases
Use this as a compact workflow and fallback syntax reference. Prefer a
separately installed kepano/obsidian-skillsobsidian-bases skill, then the
current official Bases syntax, for
detailed or version-sensitive fields and functions.
Answer design and syntax questions read-only. For a requested .base edit,
resolve the user vault and use one inspected transaction; never write the file
directly.
Resolve the installed product root from this skill's own location, not from the
vault or current working directory:
PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
test -f "$CORE"
Every ../wiki/references/ link in this file resolves the same way, relative
to this skill's own directory under $PRODUCT_ROOT, never relative to the
selected vault's wiki/ directory.
Workflow
Inspect representative note properties and any existing .base file.
Define the smallest filter that selects the intended notes.
Add formulas only for values that must be computed.
Choose views and display order. Do not assume a view type or option is
supported by the user's Obsidian version or installed plugins.
Validate YAML, expression quoting, property names, formula references, and
null handling.
Preview the complete file and expected result set before a mutation.
If an edit was requested, read
operation-transactions.md,
keep the .base file under wiki/, and build one
claude-obsidian.transaction.v1 bundle with operation_type: base. Inspect
it, then set APPROVAL_SHA256 to the returned approval_sha256 only after
review and apply once: