# Query Obsidian Bases from AI Tools

Obsidian Bases data can be hard to inspect from an AI coding session. This skill shows Claude, Codex, and Claude Code how to query a local Bases RPC plugin and summarize structured note data.

## Install

```bash
npx skillstore add artemxtech/bases
```

## Metadata

- - Slug: artemxtech-bases
- - Version: 1.0.0
- - Author: ArtemXTech
- - GitHub username: ArtemXTech
- - License: MIT
- - Repository: https://github.com/ArtemXTech/personal-os-skills/tree/main/skills/bases
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands, network
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/artemxtech-bases
- - Manifest: https://skillstore.pages.dev/api/skills/artemxtech-bases/manifest

## Capabilities

- Lists available Obsidian bases through the local RPC endpoint.
- Queries a named base and view when the user provides the path and view name.
- Retrieves schema information to discover available fields.
- Shows expected response fields such as path, name, and frontmatter.
- Demonstrates jq filters for extracting names and selected frontmatter values.

## Use Cases

- Review project note status: Query a project base and summarize active, blocked, or completed notes.
- Inspect vault schemas: Discover available fields before building filters, dashboards, or reports.
- Extract structured note lists: Pull names and selected frontmatter values from a base view for quick review.

## Prompt Templates

### List my bases

```
Use the bases skill to list available Obsidian bases from the local RPC endpoint. Ask before running any command.
```

### Query a specific view

```
Query the Obsidian base at [base path] and view [view name]. Summarize the returned records by name and status.
```

### Discover fields first

```
Get the schema for [base path] and [view name], then recommend useful fields for a concise report.
```

### Create a focused summary

```
Query [base path] view [view name], extract names and selected frontmatter fields, and summarize trends without exposing unrelated notes.
```

## Limitations

- Requires the Obsidian Bases Query plugin to be installed and running.
- Only documents access through the localhost RPC endpoint.
- Does not provide authentication, authorization, or plugin setup automation.
- Can only query data exposed by the installed plugin and selected base view.

## Best Practices

- Ask for user approval before running commands that read local vault data.
- Query the schema before assuming field names in a base view.
- Limit summaries to the base, view, and fields requested by the user.

## Anti Patterns

- Do not run RPC queries against private notes without explicit user consent.
- Do not assume the plugin is installed or reachable before checking.
- Do not expose full frontmatter when the user only requested a narrow summary.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T10:21:20.32\+00:00
- - Summary: Static command and network findings are mostly true positives in documentation examples that call a local Obsidian RPC service with curl and process results with jq. The weak cryptographic algorithm finding is a false positive from the RPC description, and no prompt injection or malicious exfiltration intent was found.

## Stats

- - Views: 230
- - Downloads: 7
- - Favorites: 0
- - Popularity score: 0