obsidian-bases

davila7/claude-code-templates · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/davila7/claude-code-templates --skill obsidian-bases
0 commentsdiscussion
summary

This skill enables Claude Code to create and edit valid Obsidian Bases (.base files) including views, filters, formulas, and all related configurations.

skill.md

Obsidian Bases Skill

This skill enables Claude Code to create and edit valid Obsidian Bases (.base files) including views, filters, formulas, and all related configurations.

Overview

Obsidian Bases are YAML-based files that define dynamic views of notes in an Obsidian vault. A Base file can contain multiple views, global filters, formulas, property configurations, and custom summaries.

File Format

Base files use the .base extension and contain valid YAML. They can also be embedded in Markdown code blocks.

Complete Schema

# Global filters apply to ALL views in the base
filters:
  # Can be a single filter string
  # OR a recursive filter object with and/or/not
  and: []
  or: []
  not: []

# Define formula properties that can be used across all views
formulas:
  formula_name: 'expression'

# Configure display names and settings for properties
properties:
  property_name:
    displayName: "Display Name"
  formula.formula_name:
    displayName: "Formula Display Name"
  file.ext:
    displayName: "Extension"

# Define custom summary formulas
summaries:
  custom_summary_name: 'values.mean().round(3)'

# Define one or more views
views:
  - type: table | cards | list | map
    name: "View Name"
    limit: 10                    # Optional: limit results
    groupBy:                     # Optional: group results
      property: property_name
      direction: ASC | DESC
    filters:                     # View-specific filters
      and: []
    order:                       # Properties to display in order
      - file.name
      - property_name
      - formula.formula_name
    summaries:                   # Map properties to summary formulas
      property_name: Average

Filter Syntax

Filters narrow down results. They can be applied globally or per-view.

Filter Structure

# Single filter
filters: 'status == "done"'

# AND - all conditions must be true
filters:
  and:
    - 'status == "done"'
    - 'priority > 3'

# OR - any condition can be true
filters:
  or:
    - 'file.hasTag("book")'
    - 'file.hasTag("article")'

# NOT - exclude matching items
filters:
  not:
    - 'file.hasTag("archived")'

# Nested filters
filters:
  or:
    - file.hasTag("tag")
    - and:
        - file.hasTag("book")
        - file.hasLink("Textbook")
    - not:
        - file.hasTag("book")
        - file.inFolder("Required Reading")

Filter Operators

Operator Description
== equals
!= not equal
> greater than
< less than
>= greater than or equal
<= less than or equal
&& logical and
|| logical or
! logical not

Properties

Three Types of Properties

  1. Note properties - From frontmatter: note.author or just author
  2. File properties - File metadata: file.name, file.mtime, etc.
  3. Formula properties - Computed values: formula.my_formula

File Properties Reference

Property Type Description
file.name String File name
file.basename String File name without extension
file.path String Full path to file
file.folder String Parent folder path
file.ext String File extension
file.size Number File size in bytes
file.ctime Date Created time
file.mtime Date Modified time
file.tags List All tags in file
file.links List Internal links in file
file.backlinks List Files linking to this file
file.embeds List Embeds in the note
file.properties Object All frontmatter properties

The this Keyword

  • In main content area: refers to the base file itself
  • When embedded: refers to the embedding file
  • In sidebar: refers to the active file in main content

Formula Syntax

Formulas compute values from properties. Defined in the formulas section.

formulas:
  # Simple arithmetic
  total: "price * quantity"
  
  # Conditional logic
  status_icon: 'if(done, "✅", "⏳")'
  
  # String formatting
  formatted_price: 'if(price, price.toFixed(2) + " dollars")'
  
  # Date formatting
  created: 'file.ctime.format("YYYY-MM-DD")'
  
  # Complex expressions
  days_old: '((now() - file.ctime) / 86400000).round(0)'

Functions Reference

Global Functions

Function Signature Description
date() date(string): date Parse string to date. Format: YYYY-MM-DD HH:mm:ss
duration() duration(string): duration Parse duration string
now() now(): date Current date and time
today() today(): date Current date (time = 00:00:00)
if() if(condition, trueResult, falseResult?) Conditional
min() min(n1, n2, ...): number Smallest number
max() max(n1, n2, ...): number Largest number
number() number(any): number Convert to number
link() link(path, display?): Link Create a link
list() list(element): List Wrap in list if not already
file() file(path): file Get file object
image() image(path): image Create image for rendering
icon() icon(name): icon Lucide icon by name
html() html(string): html Render as HTML
escapeHTML() escapeHTML(string): string Escape HTML characters

Any Type Functions

Function Signature Description
isTruthy() any.isTruthy(): boolean Coerce to boolean
isType() any.isType(type): boolean Check type
toString() any.toString(): string Convert to string

Date Functions & Fields

Fields: date.year, date.month, date.day, date.hour, date.minute, date.second, date.millisecond

Function Signature Description
date() date.date(): date Remove time portion
format() date.format(string): string Format with Moment.js pattern
time() date.time(): string Get time as string
relative() date.relative(): string Human-readable relative time
isEmpty() date.isEmpty(): boolean Always false for dates

Date Arithmetic

# Duration units: y/year/years, M/month/months, d/day/days, 
#                 w/week/weeks, h/hour/hours, m/minute/minutes, s/second/seconds

# Add/subtract durations
"date + \"1M\""           # Add 1 month
"date - \"2h\""           # Subtract 2 hours
"now() + \"1 day\""       # Tomorrow
"today() + \"7d\""        # A week from today

# Subtract dates for millisecond difference
"now() - file.ctime"

# Complex duration arithmetic
"now() + (duration('1d') * 2)"

String Functions

Field: string.length

Function Signature Description
contains() string.contains(value): boolean Check substring
containsAll() string.containsAll(...values): boolean All substrings present
containsAny() string.containsAny(...values): boolean Any substring present
startsWith() string.startsWith(query): boolean Starts with query
endsWith() string.endsWith(query): boolean Ends with query
isEmpty() string.isEmpty(): boolean Empty or not present
lower() string.lower(): string To lowercase
title() string.title(): string To Title Case
trim() string.trim(): string Remove whitespace
replace() string.replace(pattern, replacement): string Replace pattern
repeat() string.repeat(count): string Repeat string
reverse() string.reverse(): string Reverse string
slice() string.slice(start, end?): string Substring
split() string.split(separator, n?): list Split to list

Number Functions

Function Signature Description
abs() number.abs(): number Absolute value
ceil() number.ceil(): number Round up
floor() number.floor(): number Round down
round() number.round(digits?): number Round to digits
toFixed() number.toFixed(precision): string Fixed-point notation
isEmpty() number.isEmpty(): boolean Not present

List Functions

Field: list.length

Function Signature Description
contains() list.contains(value): boolean Element exists
containsAll() list.containsAll(...values): boolean All elements exist
containsAny() list.containsAny(...values): boolean Any element exists
filter() list.filter(expression): list Filter by condition (uses value, index)
map() list.map(expression): list Transform elements (uses value, index)
reduce() list.reduce(expression, initial): any Reduce to single value (uses value, index, acc)
flat() list.flat(): list Flatten nested lists
join() list.join(separator): string Join to string
reverse() list.reverse(): list Reverse order
slice() list.slice(start, end?): list Sublist
sort() list.sort(): list Sort ascending
unique() list.unique(): list Remove duplicates
isEmpty() list.isEmpty(): boolean No elements

File Functions

Function Signature Description
asLink() file.asLink(display?): Link Convert to link
hasLink() file.hasLink(otherFile): boolean<
how to use obsidian-bases

How to use obsidian-bases on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add obsidian-bases
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/davila7/claude-code-templates --skill obsidian-bases

The skills CLI fetches obsidian-bases from GitHub repository davila7/claude-code-templates and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/obsidian-bases

Reload or restart Cursor to activate obsidian-bases. Access the skill through slash commands (e.g., /obsidian-bases) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.837 reviews
  • Sofia Gupta· Dec 24, 2024

    I recommend obsidian-bases for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Hiroshi Menon· Dec 20, 2024

    Keeps context tight: obsidian-bases is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Michael Huang· Dec 16, 2024

    Useful defaults in obsidian-bases — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Chaitanya Patil· Dec 8, 2024

    Solid pick for teams standardizing on skills: obsidian-bases is focused, and the summary matches what you get after install.

  • Piyush G· Nov 27, 2024

    We added obsidian-bases from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sofia Mensah· Nov 23, 2024

    Keeps context tight: obsidian-bases is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Arya Desai· Nov 11, 2024

    Registry listing for obsidian-bases matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Shikha Mishra· Oct 18, 2024

    obsidian-bases fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mei Rao· Oct 14, 2024

    obsidian-bases is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Arya Shah· Oct 2, 2024

    obsidian-bases reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 37

1 / 4