api-canvas

Register, query, and export tabular data in Obsidian vaults using SQL.

654|102|Updated Jan 23, 2025
One-click install
npx skills add https://github.com/cyanheads/obsidian-mcp-server --skill api-canvas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-canvas
Source: https://github.com/cyanheads/obsidian-mcp-server/tree/main/skills/api-canvas
Command: npx skills add https://github.com/cyanheads/obsidian-mcp-server --skill api-canvas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @duckdb/node-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a primitive framework for executing ad-hoc SQL queries and data analysis across registered tabular data within Obsidian vaults, facilitating complex data workflows.

Core Features & Use Cases

  • Registering External Data: Load and register tables from upstream APIs or datasets into a unified analytical workspace.
  • SQL Querying: Run SQL commands over multiple registered tables to analyze and extract insights.
  • Data Export: Export query results to CSV, Parquet, or JSON formats for further use.
  • Use Case: Data analysts can register multiple datasets from different sources, perform cross-table queries, and export combined results for reporting.

Quick Start

Use the api-canvas skill to register a dataset from an API, execute a SQL query, and export the results as a CSV file.

Frequently Asked Questions about api-canvas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run SQL queries on tabular data stored in an Obsidian vault?

Register external datasets into a unified workspace and execute SQL commands across multiple tables to extract insights using in-memory analytics.

Can I export SQL query results to CSV or Parquet from Obsidian?

Export SQL query results to CSV, Parquet, or JSON formats directly from the analytical workspace for reporting and further use outside the vault.

Do I need DuckDB to perform ad-hoc data analysis on Obsidian vault files?

DuckDB and related dependencies are required to facilitate in-memory analytics, enabling ad-hoc SQL queries and data analysis across registered tabular data.

What is the best way to combine multiple API datasets for cross-table analysis in Obsidian?

Load and register tables from upstream APIs into a unified analytical workspace, allowing cross-table SQL queries and export of combined results.

Does this approach work for lightweight ad-hoc analysis without a full database server?

Designed for lightweight environments, it uses in-memory analytics to facilitate complex data workflows and ad-hoc analysis without a full database server setup.