dataview-troubleshooting

Diagnose Dataview query and metadata issues in Obsidian.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/benoberkfell/claude-plugins --skill dataview-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dataview-troubleshooting
Source: https://github.com/benoberkfell/claude-plugins/tree/main/plugins/dataview/skills/dataview-troubleshooting
Command: npx skills add https://github.com/benoberkfell/claude-plugins --skill dataview-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Dataview troubleshooting helps identify and resolve issues where Dataview queries return nothing, fields are not indexed, or tasks and data don't appear as expected in Obsidian.

Core Features & Use Cases

  • Guided checks for common problems: missing metadata, misnamed fields, incorrect FROM sources, and implicit field limitations.
  • Step-by-step remediation for stale or incorrect query results, including best practices for frontmatter and inline fields.
  • Use Case: When a query yields empty results, you can quickly verify the metadata, field normalization, and source scope to restore expected outputs.

Quick Start

Run the diagnostic steps on a failing Dataview query and implement the suggested fixes.

Frequently Asked Questions about dataview-troubleshooting

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

FAQPage Schema
Why does my Dataview query return no results in Obsidian?

Dataview queries return no results when frontmatter fields are missing, incorrectly named, or FROM sources reference invalid paths. Validate metadata normalization, ensure correct source scope, and confirm inline fields are properly formatted to restore expected outputs.

How do I fix Obsidian notes where Dataview fields fail to index?

Dataview fields fail to index due to implicit field limitations or misnamed metadata. Enforce strict validation of frontmatter and inline fields, normalize field naming conventions, and verify the query references the correct indexed properties.

When should I use Dataview versus DataviewJS in Obsidian?

Use Dataview for standard queries, task lists, and metadata retrieval across notes. Switch to DataviewJS when you need custom JavaScript logic, dynamic rendering, or complex conditional formatting that standard Dataview query syntax cannot support.

What is the best way to troubleshoot missing tasks in an Obsidian Dataview query?

Missing tasks in a Dataview query often stem from incorrect source references or unvalidated inline fields. Run diagnostic checks on your query's FROM scope, normalize field naming, and verify task metadata is properly structured.

How do I resolve unexpectedly empty or stale Dataview results across multiple notes?

Empty or stale Dataview results across notes require checking incorrect FROM sources and validating frontmatter consistency. Apply step-by-step remediation to normalize field naming and ensure all referenced metadata is correctly indexed.

Does Dataview support querying implicit fields in Obsidian frontmatter?

Dataview supports implicit fields but they have known limitations that can cause unexpected query behavior. Validate your frontmatter structure and normalize field naming to ensure these implicit properties are correctly indexed and retrieved.