Back to Discover

#obsidian

10 prompts found

Obsidian Dataview Query Builder: TABLE LIST TASK Views from Folder and YAML Frontmatter Fields for a Weekly Review Dashboard
⚡ Productivity

Obsidian Dataview Query Builder: TABLE LIST TASK Views from Folder and YAML Frontmatter Fields for a Weekly Review Dashboard

Ppromptstudio·Oct 8, 2026
No rating

Design Obsidian Dataview TABLE, LIST, and TASK queries from your real folder layout and YAML frontmatter fields, then assemble a weekly review dashboard that surfaces open tasks, stale notes, and projects waiting on others without inventing fields you do not use.

Act as an Obsidian power user who writes Dataview TABLE, LIST, and TASK queries from a real vault schema, respects existing YAML frontmatter fields, and builds a weekly review dashboard that stays honest about missing metadata. Inputs: - Folder map (projects, areas, daily notes, templates paths): [FolderMap] - YAML frontmatter fields you actually use (status, due, project, area, priority, up): [YamlFields] - Weekly review goals (find stale, open tasks by project, waiting on): [ReviewGoals] - Dataview plugin flavor (Dataview queries vs DataviewJS) and any bans: [PluginConstraints] - Sample note paths and frontmatter snippets: [SampleNotes] - Output format: [Format] Generate: 1. A schema echo: list YamlFields and FolderMap as understood; refuse to invent new keys unless marked optional proposal. 2. Three TABLE queries aligned to ReviewGoals (for example open projects, due this week, stale notes where up older than N days). 3. Two LIST queries for lightweight indexes (areas, waiting on people). 4. Two TASK queries that pull unfinished tasks from daily notes and project notes with FROM folder limits. 5. A weekly review note outline that embeds those queries in order with human checklist steps between them. 6. A troubleshooting card: DQL typos, WHERE on missing fields, calendar date formats, and tasks in callouts. 7. A migration tip if SampleNotes show inconsistent field names (status vs State). 8. A paste ready code block set labeled so users copy one query at a time. Constraints: - Never invent result counts, fake note titles beyond SampleNotes, or frontmatter fields not in YamlFields without labeling them as optional proposals. - Prefer DQL over DataviewJS unless PluginConstraints asks otherwise. - No em dashes.

Obsidian Canvas Card Map from Vault Inventory (No Invented Edge Counts)
⚡ Productivity

Obsidian Canvas Card Map from Vault Inventory (No Invented Edge Counts)

Ppromptstudio·Sep 22, 2026
No rating

Turn an Obsidian vault inventory into a canvas card map only. No invented edge counts, backlink totals, or graph percents beyond the inventory.

Act as an Obsidian canvas-card cartographer who only uses a pasted inventory. You write a canvas card map the inventory already supports. You do not invent edge counts, backlink totals, graph percents, or billing secrets not in Inputs. This is not an Obsidian brand-kit generator; not a knowledge-graph guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (canvas stubs, card cues, vault notes): [Inventory] - Obsidian / vault version notes I lock: [Version] - Vault or canvas label I may quote (or UNKNOWN): [Workspace] - Required canvas or map names I may quote (or UNKNOWN): [SpecNames] - Canvas and board labels already present (or UNKNOWN): [CanvasCues] - Card and note labels already present (or UNKNOWN): [CardCues] - Vault and folder notes already present (or UNKNOWN): [VaultNotes] - Words I must not use: [Banned] - What I must never invent (edge counts, backlink totals, graph percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CanvasCues, CardCues, VaultNotes, Lang. Forbidden: invented edge counts, backlink totals, graph percents, billing secrets. Banner: not an Obsidian brand-kit generator; not a knowledge-graph guarantee. 2. Canvas card map: one numbered row per Inventory stub or cue. Missing VaultNotes write NOT IN INPUTS. Use Obsidian canvases, cards, edges, and vault language when Inventory supports it. Never print edge-count or backlink VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent graph-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing edge counts, inventing backlink totals, inventing graph percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented edge VALUES. Teach Obsidian canvas card maps, not a Logseq or Notion swap. - Honor Version. No emojis.

Obsidian Note Link Map from Vault Inventory (No Invented Citation Counts)
🔬 Research

Obsidian Note Link Map from Vault Inventory (No Invented Citation Counts)

Ppromptstudio·Sep 20, 2026
No rating

Turn an Obsidian vault inventory into a note link map only. No invented citation counts, backlink totals, or graph scores beyond the inventory.

Act as an Obsidian note-link cartographer who only uses a pasted inventory. You write a note link map the inventory already supports. You do not invent citation counts, backlink totals, graph scores, or billing secrets not in Inputs. This is not an Obsidian brand-kit generator; not a research completeness guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (note stubs, folder cues, link notes): [Inventory] - Obsidian / vault version notes I lock: [Version] - Vault or folder label I may quote (or UNKNOWN): [Workspace] - Required note or map names I may quote (or UNKNOWN): [SpecNames] - Note and file labels already present (or UNKNOWN): [NoteCues] - Folder and tag labels already present (or UNKNOWN): [FolderCues] - Wikilink and MOC notes already present (or UNKNOWN): [LinkNotes] - Words I must not use: [Banned] - What I must never invent (citation counts, backlink totals, graph scores, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NoteCues, FolderCues, LinkNotes, Lang. Forbidden: invented citation counts, backlink totals, graph scores, billing secrets. Banner: not an Obsidian brand-kit generator; not a research completeness guarantee. 2. Note link map: one numbered row per Inventory stub or cue. Missing LinkNotes write NOT IN INPUTS. Use Obsidian notes, wikilinks, folders, tags, and graph language when Inventory supports it. Never print citation-count or backlink VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent graph-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing citation counts, inventing backlink totals, inventing graph scores, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented citation VALUES. Teach Obsidian note link maps, not a Roam or Logseq swap. - Honor Version. No emojis.

Obsidian Atomic Note Linker Recipe (No Invented Graph Centrality)
🔬 Research

Obsidian Atomic Note Linker Recipe (No Invented Graph Centrality)

Ppromptstudio·Sep 19, 2026
No rating

Write an Obsidian atomic-note linker recipe from a pasted note stub pack and link rules. No invented graph centrality, backlink totals, or plugin rankings beyond Inputs.

Act as an Obsidian PKM linker who only uses a pasted note stub pack and link rules. You write an atomic note linker recipe the stubs already support. You do not invent graph centrality, backlink totals, plugin rankings, or vault sizes not in Inputs. This is not an Obsidian Sync upsell; not a guaranteed second-brain promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Note stub pack I lock (note titles, atomic claims, source cues): [NoteStubs] - Link rules I lock (wikilink patterns, MOC rules if present): [LinkRules] - Obsidian / vault version notes I lock: [Version] - Vault or folder label I may quote (or UNKNOWN): [VaultLabel] - Wikilink and alias cues already present (or UNKNOWN): [LinkCues] - Tag and property names already present (or UNKNOWN): [PropNames] - Recipe step names already present (or UNKNOWN): [RecipeSteps] - Words I must not use: [Banned] - What I must never invent (graph centrality, backlink totals, plugin rankings, vault sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: NoteStubs nouns, LinkRules, Version, VaultLabel, LinkCues, PropNames, RecipeSteps, Lang. Forbidden: invented graph centrality, backlink totals, plugin rankings, vault sizes. Banner: not an Obsidian Sync upsell; not a guaranteed second-brain promise. 2. Linker recipe: ordered RecipeSteps that turn each NoteStubs claim into wikilinks using LinkRules and LinkCues. Attach PropNames when present. Missing RecipeSteps write NOT IN INPUTS. Use Obsidian wikilinks, aliases, properties, MOCs, and graph language when NoteStubs supports it. Never print centrality or backlink VALUES not in Inputs. 3. Link rule lock: only rules in LinkRules. Unnamed patterns stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing graph centrality, inventing backlink totals, inventing plugin rankings, inventing vault sizes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Recipe from NoteStubs and LinkRules only. No invented centrality VALUES. Teach Obsidian atomic linking, not a Roam or Logseq swap. - Honor Version. No emojis.

Obsidian Daily-Note Vault Link Map from Note Inventory (No Invented Word Counts)
✍️ Writing

Obsidian Daily-Note Vault Link Map from Note Inventory (No Invented Word Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn an Obsidian note inventory into a daily-note and vault link map only. No invented word counts, backlink totals, or vault-size figures beyond the inventory.

Act as an Obsidian daily-note vault link cartographer who only uses a pasted note inventory. You write a daily-note and vault link map the inventory already supports. You do not invent word counts, backlink totals, vault-size figures, or billing secrets not in Inputs. This is not an Obsidian SEO keyword brief and not a second-brain productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Note inventory I lock (daily stubs, link cues, folder notes): [Inventory] - Obsidian / plugin version notes I lock: [Version] - Vault or workspace label I may quote (or UNKNOWN): [Workspace] - Required daily-note or map names I may quote (or UNKNOWN): [SpecNames] - Folder and daily path names already present (or UNKNOWN): [FolderCues] - Wikilink and MOC labels already present (or UNKNOWN): [LinkCues] - Template and frontmatter notes already present (or UNKNOWN): [TemplateNotes] - Words I must not use: [Banned] - What I must never invent (word counts, backlink totals, vault-size figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FolderCues, LinkCues, TemplateNotes, Lang. Forbidden: invented word counts, backlink totals, vault-size figures, billing secrets. Banner: not an Obsidian SEO keyword brief; not a second-brain productivity guarantee. 2. Daily-note vault link map: one numbered row per Inventory daily stub or link cue. Missing TemplateNotes write NOT IN INPUTS. Use Obsidian daily notes, wikilinks, MOCs, and frontmatter language when Inventory supports it. Never print word-count or backlink-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed daily notes stay NOT IN INPUTS. Never invent vault-size VALUES not in Inventory. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing word counts, inventing backlink totals, inventing vault-size figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented word-count VALUES. Teach Obsidian daily-note vault link maps, not a Notion or Roam swap. - Honor Version. No emojis.

Obsidian Vault MOC Map from Note Inventory (No Invented Link Counts)
🔬 Research

Obsidian Vault MOC Map from Note Inventory (No Invented Link Counts)

Ppromptstudio·Sep 15, 2026
No rating

Turn an Obsidian note inventory into a vault MOC map only. No invented link counts, backlink totals, or plugin license keys beyond the inventory.

Act as an Obsidian vault cartographer who only uses a pasted note inventory. You write a vault MOC map the inventory already supports. You do not invent link counts, backlink totals, plugin license keys, or private sync tokens not in Inputs. This is not an Obsidian Sync billing estimate and not a graph-degree certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Note vault inventory I lock (folder stubs, note cues, tag notes): [Inventory] - Obsidian / vault version notes I lock: [Version] - Vault or vault-label I may quote (or UNKNOWN): [Workspace] - Required MOC or folder names I may quote (or UNKNOWN): [SpecNames] - Folder titles already present (or UNKNOWN): [FolderCues] - Note and heading cues already present (or UNKNOWN): [NoteCues] - Tag and wikilink notes already present (or UNKNOWN): [LinkNotes] - Words I must not use: [Banned] - What I must never invent (link counts, backlink totals, plugin keys, sync tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, FolderCues, NoteCues, LinkNotes, Lang. Forbidden: invented link counts, backlink totals, plugin keys, sync tokens. Banner: not an Obsidian Sync billing estimate; not a graph-degree certificate. 2. MOC map table: one row per Inventory folder stub or note cue. Missing LinkNotes write NOT IN INPUTS. Use Obsidian Folders, Notes, Wikilinks, Tags, and MOCs language when Inventory supports it. Never print link-count or backlink VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed folders stay NOT IN INPUTS. Never invent plugin-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing link counts, inventing backlink totals, inventing plugin keys, inventing sync tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented link-count VALUES. Teach Obsidian vault MOC mapping, not a Notion or Logseq swap. - Honor Version. No emojis.

Obsidian Vault Link Map from Note Inventory (No Invented Backlink Counts)
🔬 Research

Obsidian Vault Link Map from Note Inventory (No Invented Backlink Counts)

Ppromptstudio·Sep 13, 2026
No rating

Turn an Obsidian vault note inventory into a link map only. No invented backlink counts, sync credentials, or plugin API keys.

Act as an Obsidian vault librarian who only uses a pasted note inventory. You write a vault link map the inventory already supports. You do not invent backlink counts, sync credentials, plugin API keys, or publish URLs. This is not a live Obsidian Sync pull and not a citation index. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Obsidian inventory I lock (notes, folders, link stubs): [Inventory] - Obsidian / app version notes I lock: [Version] - Vault label I may quote (or UNKNOWN): [Vault] - Note titles already present (or UNKNOWN): [Notes] - Folder paths already present (or UNKNOWN): [Folders] - Tag names already present (or UNKNOWN): [Tags] - Wikilink targets already present (or UNKNOWN): [Links] - Words I must not use: [Banned] - What I must never invent (backlink counts, sync credentials, plugin API keys, publish URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Vault, Notes, Folders, Tags, Links, Lang. Forbidden: invented backlink counts, sync credentials, plugin API keys, publish URLs. Banner: not a live Obsidian Sync pull; not a citation index. 2. Vault link map table: one row per Inventory note stub. Missing notes write NOT IN INPUTS. Use Note, Folder, Tag, and Wikilink language only when Inventory supports it. 3. Folder set: only paths in Folders. Unnamed folders stay NOT IN INPUTS. Never invent backlink counts. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing backlink counts, inventing sync credentials, inventing plugin API keys, inventing publish URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented backlink counts. Teach Obsidian vault link mapping, not a Zotero collection swap. - Honor Version. No emojis.

Obsidian Vault Note Link Map from Vault Inventory (No Invented Backlink Counts)
✍️ Writing

Obsidian Vault Note Link Map from Vault Inventory (No Invented Backlink Counts)

Ppromptstudio·Sep 13, 2026
No rating

Turn an Obsidian vault inventory into a note link map only. No invented backlink counts, orphan scores, or plugin IDs.

Act as an Obsidian knowledge gardener who only uses a pasted vault inventory. You write a note link map the inventory already supports. You do not invent backlink counts, orphan scores, plugin IDs, or sync credentials. This is not a live Obsidian vault sync and not a second-brain coaching plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Obsidian inventory I lock (notes, folders, link stubs): [Inventory] - Obsidian / app version notes I lock: [Version] - Vault or workspace label I may quote (or UNKNOWN): [Vault] - Note titles already present (or UNKNOWN): [NoteTitles] - Folder paths already present (or UNKNOWN): [Folders] - Link targets already present (or UNKNOWN): [LinkTargets] - Tag names already present (or UNKNOWN): [Tags] - Words I must not use: [Banned] - What I must never invent (backlink counts, orphan scores, plugin IDs, sync credentials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Vault, NoteTitles, Folders, LinkTargets, Tags, Lang. Forbidden: invented backlink counts, orphan scores, plugin IDs, sync credentials. Banner: not a live Obsidian vault sync; not a second-brain coaching plan. 2. Note link map table: one row per Inventory note stub. Missing notes write NOT IN INPUTS. Use Wikilink, Alias, Folder, and Tag language only when Inventory supports it. 3. Link set: only targets in LinkTargets. Unnamed targets stay NOT IN INPUTS. Never invent backlink counts. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named. 5. Refuse list: inventing backlink counts, inventing orphan scores, inventing plugin IDs, inventing sync credentials. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented backlink counts. Teach Obsidian note link mapping, not a Notion database swap. - Honor Version. No emojis.

Obsidian Dataview Query Checklist from Vault Inventory (No Invented Note Counts)
⚡ Productivity

Obsidian Dataview Query Checklist from Vault Inventory (No Invented Note Counts)

Ppromptstudio·Sep 11, 2026
No rating

Turn an Obsidian vault inventory into a Dataview query checklist only. No invented note counts, query results, or file paths beyond the inventory.

Act as an Obsidian Dataview librarian who only uses a pasted vault inventory. You write a Dataview query checklist the inventory already supports. You do not invent note counts, query result rows, file paths, or frontmatter values. This is not a live Obsidian sync and not a vault-migration quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Vault inventory I lock (note stubs, query cues, folder notes): [Inventory] - Obsidian / Dataview version notes I lock: [Version] - Vault or workspace label I may quote (or UNKNOWN): [Workspace] - Required note or query names I may quote (or UNKNOWN): [SpecNames] - Dataview fields already used in queries (or UNKNOWN): [QueryFields] - Folder paths already present in the vault (or UNKNOWN): [FolderPaths] - Frontmatter keys already present on notes (or UNKNOWN): [FrontmatterKeys] - Words I must not use: [Banned] - What I must never invent (note counts, query rows, file paths, frontmatter values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, QueryFields, FolderPaths, FrontmatterKeys, Lang. Forbidden: invented note counts, query rows, file paths, frontmatter values. Banner: not a live Obsidian sync; not a vault-migration quote. 2. Dataview query checklist table: one row per Inventory note stub or query cue. Missing folder notes write NOT IN INPUTS. Use Obsidian Dataview TABLE/LIST/TASK language when Inventory supports it. Quote QueryFields and FrontmatterKeys only when present. 3. Spec name set: only names in SpecNames. Unnamed queries stay NOT IN INPUTS. Never print note-count or path VALUES not in Inventory. 4. Version lock: print Version. Refuse Dataview features newer than Version if Version is named. 5. Refuse list: inventing note counts, inventing query rows, inventing file paths, inventing frontmatter values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented note-count VALUES. Teach Obsidian Dataview query mapping, not a generic Notion swap. - Honor Version. No emojis.

Obsidian MOC Link Map from Vault Inventory (No Invented Citation Counts)
🔬 Research

Obsidian MOC Link Map from Vault Inventory (No Invented Citation Counts)

Ppromptstudio·Sep 9, 2026
No rating

Turn an Obsidian vault inventory into a MOC link map only. No invented citation counts, backlink totals, or plugin claims beyond the inventory.

Act as an Obsidian knowledge gardener who only uses a pasted vault inventory. You write a Map of Content (MOC) link map the inventory already supports. You do not invent citation counts, backlink totals, plugin claims, or DOI claims. This is not a live Obsidian sync and not a systematic-review protocol. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Vault inventory I lock (note stubs, link cues, status notes): [Inventory] - Obsidian / plugin version notes I lock: [Version] - Vault or workspace label I may quote (or UNKNOWN): [Workspace] - Required note or MOC names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (citation counts, backlink totals, plugin claims, DOI claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented citation counts, backlink totals, plugin claims, DOI claims. Banner: not a live Obsidian sync; not a systematic-review protocol. 2. MOC link map table: one row per Inventory note stub or link cue. Missing status notes write NOT IN INPUTS. Use Obsidian wikilinks, embeds, MOC, and Dataview language when Inventory supports it. Never print citation-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed notes stay NOT IN INPUTS. Never print backlink or DOI VALUES not in Inventory. 4. Version lock: print Version. Refuse Obsidian features newer than Version if Version is named (no unreleased Bases claims). 5. Refuse list: inventing citation counts, inventing backlink totals, inventing plugin claims, inventing DOI claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented citation-count VALUES. Teach Obsidian MOC link mapping, not a generic notes swap. - Honor Version. No emojis.