obsidian-baseslisted

# Obsidian Bases Skill ## Workflow 1. Create or open the target `.base` file and keep it valid YAML. 2. Define scope with the smallest useful `filters`. 3. Prefer existing file metadata and note properties before inventing new schema. 4. Add formulas only when the requested view cannot be expressed with raw properties. 5. Add one or more views with a clear `order` and optional grouping or summaries. 6. Validate YAML syntax, formula references, and quoted strings before finishing. ## Property Discipline Prefer Obsidian-native file properties and existing note properties before introducing new frontmatter fields. - Use `file.name`, `file.basename`, `file.folder`, `file.path`, `file.ext`, `file.ctime`, `file.mtime`, `file.tags`, `file.links`, `file.backlinks`, `file.embeds`, and `file.properties` when they satisfy the request. - Prefer `file.hasTag(...)`, `file.inFolder(...)`, and `file.hasLink(...)` for scope filters instead of adding duplicate custom metadata. - Do not add custom properties such as `status`, `priority`, `due`, `category`, `type`, `author`, `pages`, or `cover` unless the user asks for them, the vault already uses them, or the requested view cannot be built from native metadata. - When custom note properties are needed, keep them minimal and make the Base consume the existing schema rather than inventing extra fields. ## Minimal Schema Base files use the `.base` extension and contain valid YAML. ```yaml filters: and: [] formulas: age_days: '(now() -