plugins/obsidian-and-notes/skills/read-notes/SKILL.md
Search and read Obsidian vault notes by topic. Use when needing context from past sessions, project notes, or any stored knowledge.
npx skillsauth add arosenkranz/claude-code-config read-notesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Refer to ~/.claude/skills/obsidian-core/SKILL.md for CLI patterns, preflight checks, and error handling.
If no argument is provided, inform the user they need to pass a topic as an argument.
Primary search — full-text search across the vault:
obsidian search:context query="<topic>" format=json limit=10 2>/dev/null
Folder-scoped search — when the user specifies a context or folder:
obsidian search:context query="<topic>" path="Sessions" format=json limit=10 2>/dev/null
Tag-based search — secondary vector when the topic maps to a known tag:
obsidian tag name="<topic>" verbose 2>/dev/null
Backlinks — for the top result, surface related notes:
obsidian backlinks path="<top-result-path>" 2>/dev/null
99-Meta/) from resultsFor space- or comma-separated topics, run a separate search per term then merge and deduplicate results by note path.
/read-notes terraform - Find notes about Terraform/read-notes docker kubernetes - Find notes about Docker or Kubernetes/read-notes "datadog curriculum" - Find notes about Datadog curriculumtools
Lightweight orchestrator for spec-before-plan workflow. Use when starting a feature with ambiguous requirements. Walks SPEC.md → PLAN.md → execute, delegating to /superpowers:writing-plans and /superpowers:executing-plans. Invoke when asked to "spec this out", "spec-first", "spec and plan for X", or when feature requirements are vague.
tools
Problem Statement Co-Authoring Skill
development
Structure and maintain professional brag documents with clear templates for accomplishments, projects, and growth tracking. Use when documenting achievements, creating brag document entries, formatting accomplishments, or tracking career progress.
development
Analyze technical documentation for clarity, conciseness, and effectiveness using Google Technical Writing principles. Use when reviewing documentation, checking writing quality, improving docs, or providing writing feedback.