Obsidian Bases
Required companion skill for keeping Obsidian knowledge-base navigation healthy: Bases-compatible metadata, MOCs, indexes, capture logs, recent-note sections, and dashboard surfaces. Use when new or updated notes should appear in Obsidian navigation views.
Install
$ agentstack add skill-lionellau-capture-concept-obsidian-bases ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lionellau-capture-concept-obsidian-bases) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Obsidian Bases
Use this skill when a capture should update navigation surfaces in an Obsidian vault.
Goal
New notes should not become isolated files. They should appear in at least one navigation surface:
- domain
_index.md - project or domain MOC
capture-log.mdorwiki-log.md- session MOC for multi-note captures
- Obsidian Bases/dashboard files when the vault already uses them
Metadata For Views
Keep frontmatter consistent so Bases or Dataview-like views can filter notes:
type: concept
domain: software-engineering
depth: working
scenario: S5
confidence: high
provenance: extracted
created: "2026-06-11"
updated: "2026-06-11"
tags:
- domain/software-engineering
- status/active
- topic/debuggingIndex Updates
If a domain _index.md exists, add one row:
| [[note-slug]] | concept | high | What this note teaches |The description should explain the value of the note, not repeat tags.
MOC Updates
If a relevant MOC exists, add a wikilink under the most specific heading. If no heading fits, add to "Recent Notes" or "Open Gaps".
Do not create many new MOCs unless the capture creates a new stable domain or a session with 3+ concepts.
Session MOCs
Create a session MOC when 3+ concepts are captured together. It should include:
- concepts captured
- depth/type per concept
- connections discovered
- stub candidates
For domain onboarding, the domain learning map is the session MOC.
Bases Compatibility
If the vault already contains Obsidian Bases files or dashboard conventions, preserve and update them. Do not invent a Bases schema for users who do not have one.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lionellau
- Source: lionellau/capture-concept
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.