lexbritvin
UserAgent Skills for Obsidian — plugin syntax (queries, tasks, charts, interactive UI), graph view tuning, vault auditing, heatmap visualizations. Compatible with Claude Code, Codex CLI, OpenCode, and any agent-skills runtime.
Categories
Indexed Skills (9)
obsidian-tasks-cli
Reads, filters, and updates Obsidian tasks using the CLI. Lists tasks, marks them done, toggles status, counts tasks, and runs advanced queries via the Tasks plugin API. Use when the user asks to see their tasks, check what's overdue, mark something done, analyze task progress, get a task summary, count tasks, or retrieve task data programmatically — even if they don't mention CLI or API.
obsidian-tasks-query
Creates Obsidian Tasks plugin query blocks with filters, sorting, grouping, and layout options. Use when the user asks to build a task dashboard, show overdue tasks, list tasks by priority, create a task view or report in a note, write a tasks code block, group tasks by project, filter tasks by folder or date, make a weekly review page, or anything involving a tasks query block in markdown.
obsidian-tasks-syntax
Creates and edits Obsidian Tasks plugin task lines with emoji-based or Dataview-style dates, priorities, recurrence, dependencies, and statuses. Use when the user asks to add a task, create a todo, set a due date, change priority, add recurrence, make a recurring reminder, edit a checkbox line, or anything involving task emoji signifiers (📅⏳🛫🔁) or Dataview-style task fields ([due:: ...], [priority:: ...]). Also use when the user says "remind me to", "add a todo", "new checkbox", or wants to understand the task format.
obsidian-charts
Authoring charts in Obsidian via the Charts plugin (`obsidian-charts` by phibr0) — covers the ` ```chart ` YAML codeblock (all types: bar, line, pie, doughnut, radar, polarArea, scatter, bubble, sankey), the ` ```advanced-chart ` JSON escape hatch, table-to-chart conversion (block-id linking via `id`/`file`/`layout`/`select`), and the `window.renderChart(data, container)` integration with DataviewJS (raw Chart.js v3 config). Use this skill whenever the user asks to draw a chart, plot, graph, time series, bar chart, pie/doughnut, radar/spider, scatter, bubble, or sankey diagram inside an Obsidian note, mentions ` ```chart `, ` ```advanced-chart `, `window.renderChart`, the Charts plugin, Chart.js inside Obsidian, asks to visualize a markdown table or daily-note metric, or wants to render any quantitative data over notes (mood/energy series, tag counts, books-by-rating, tasks-by-status). Trigger even when "Charts plugin" is not named — any request to visualise vault data inline goes here. Pair with the `obsidia
obsidian-dataview
Authoring queries, dashboards, and scripts for the Obsidian Dataview plugin — covers DQL (TABLE/LIST/TASK/CALENDAR), DataviewJS (`dv.*` API, DataArray, `dv.io`, `dv.view`, `dv.query`), inline DQL/JS, the metadata model (frontmatter, `Field:: value`, `[k:: v]`, `(k:: v)`, every `file.*` and task field), all DQL functions, and external plugin integration via `getAPI(app)`. Use this skill whenever the user mentions Dataview, DQL, DataviewJS, `dv.pages`, `dv.table`, `dv.taskList`, `dv.view`, `dv.io`, `file.tasks`, `file.outlinks`, `file.frontmatter`, asks to build a dashboard or query over notes ("list every note that…", "table of pages where…", "tasks due before…", "group books by genre"), writes ` ```dataview ` or ` ```dataviewjs ` blocks, uses inline `` `= …` `` or `` `$= …` ``, edits `.base` views or `dv.view` scripts, integrates Dataview from another plugin, or asks why a query returns wrong/empty results. Trigger even when "Dataview" is not named explicitly — any natural-language request to query Obsidian m
obsidian-graph-audit
Diagnose Obsidian Graph view health and clean up over-connection — identify render-only edges (dashboards as topics, log files), mega-categories, broken refs, and false categories that are inflating the graph. Use whenever the user reports the graph feels tangled, overconnected, hairball-like, or noisy, even if they don't explicitly say "audit". Triggers include "why is my graph a hairball", "audit my graph", "graph cleanup", "find graph noise", "too many connections", "graph feels tangled", "what shouldn't be on the graph", "my graph is overconnected", "graph is a mess", "what to exclude from the graph", "why are unrelated notes connected".
obsidian-graph
Configure Obsidian Graph view — color groups, filters, forces, display settings, palette choice. Use whenever the user wants to change how the graph looks or what it shows, including coloring by folder/category/topic/tag, hiding noise via filter, adjusting forces (repel/link distance), or picking a palette. Triggers include "configure the graph", "color the graph", "fix the graph", "show/hide tags on the graph", "exclude folder from graph", "graph.json", "color groups", "graph filter", "graph forces", "graph palette", "make graph readable", "spread the graph out", "highlight hubs on the graph", "why is the graph one color".
obsidian-heatmap
Build activity heatmaps in Obsidian — GitHub-style year overview via the Heatmap Calendar plugin (Richardsl), and custom DataviewJS heatmaps (weeks × days, rows × cols matrices, project activity grids) when the plugin is not enough. Use whenever the user asks about heatmaps, calendar visualizations, streaks, "did I do X every day", year-in-pixels, contribution graphs, GitHub-style activity views, daily-log visualizations, or wants to render any time-based intensity grid in a note.
obsidian-meta-bind
Authoring buttons, input fields, view fields, and embeds for the Obsidian Meta Bind plugin. Use whenever the user asks to add an interactive control, button, input, viewfield, INPUT[...] / VIEW[...] / BUTTON[...] syntax, or a meta-bind code block. Covers schema, valid enum values, inline references, JS Engine integration, and the most common validation pitfalls (e.g. "Invalid input at 'style'", "Button ID not found", trailing-comma traps).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.