doc-db-query

Generate SQLite queries for Doc DB plugin documentation filtering.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Albatross679/0313temp --skill doc-db-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-db-query
Source: https://github.com/Albatross679/0313temp/tree/main/.claude/skills/doc-db-query
Command: npx skills add https://github.com/Albatross679/0313temp --skill doc-db-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Doc databases in VSCode require writing SQL to filter and locate documentation entries. This skill automates generating correct SQLite queries from natural language or frontmatter filters.

Core Features & Use Cases

  • Generates queries for the doc-db.runQuery command, handling main and junction-table references.
  • Supports filtering by frontmatter properties and multi-field values via EXISTS subqueries, enabling precise results.
  • Use cases include listing docs by category, status, or keywords, or retrieving metadata for a set of docs.

Quick Start

Generate a query that lists documentation entries with a given frontmatter property such as category or status.

Frequently Asked Questions about doc-db-query

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

FAQPage Schema
How do I generate SQLite queries to search documentation by frontmatter properties in VS Code?

Generate SQLite queries to search documentation by frontmatter properties in VS Code by translating natural language filters into valid SQL, handling main tables and junction tables with correlated subqueries for multi-field values. Results always include _file_path for inline editing.

Can I filter documentation entries by multiple tags or multi-field frontmatter values using SQLite?

Yes, you can filter documentation entries by multiple tags or multi-field frontmatter values using SQLite. The generated queries apply EXISTS subqueries against junction tables to precisely match and retrieve documentation entries with complex multi-field metadata.

What's the best way to list documentation entries by category or status across markdown files?

The best way to list documentation entries by category or status across markdown files is generating SQLite queries that target frontmatter properties within the documentation database, returning matching entries alongside their _file_path for direct access.

How does the Doc DB extension handle inline editing of queried documentation files?

Inline editing of queried documentation files is handled by automatically including the _file_path column in every generated SQLite query result, allowing direct navigation and modification of the documentation entries within the VS Code environment.

Does this query generation approach work with standard SQLite syntax for VS Code workflows?

Yes, this query generation approach works with standard SQLite syntax for VS Code workflows. It satisfies schema rules for main tables and junction tables, using correlated subqueries to execute via the doc-db.runQuery command without external dependencies.