Have an AI work with your vault’s files and structure
Obsidian Skills
Notes, Canvases and Data Views
Steph Ango’s six skills cover Obsidian notes, Canvas, Bases, application commands, web extraction and template-based batch generation. Give a file-capable assistant real material and a target, then choose the capability that produces the notes or records you need.
Agents and working material
- Claude Code / Codex / OpenCode
- Local vault files
- CLI operations require the Obsidian app
- GitHub stars
- 50,392
- Version
- 1.0.1
- Checked
- Categories
- Content & KnowledgeWriting & Research
Choose one folder and finish one kind of cleanup.
Start with properties and links in three notes. Add Canvas when you need to see relationships, or Bases when you need to filter by status. Add extraction, templates or application commands once a repeated job is clear. Each step should leave a result you can open and compare with its sources.
Pick a task and get started
Run the installation command in the project or vault working directory used by your assistant, then choose the client and members needed for this task. The examples name skills in natural language. Configure an external tool only when the selected task needs it.
Start with a few reliable notes and add consistent properties, internal links and an index.
Install the members you need
Run the author’s HTTPS command in a local terminal and choose your client and members. Select obsidian-markdown for the first note task and the corresponding member for other tasks. This installs skill instructions; prepare external tools separately when needed.
Read the installation guidenpx skills add https://github.com/kepano/obsidian-skillsConfirm the directory, then the tool
Have the assistant identify loaded skills, the target vault and permitted paths. File tasks can start with sample notes. For CLI tasks, enable the interface using official instructions and check obsidian help. Do not assume the assistant’s working directory is the active Obsidian vault.
Set up Obsidian CLIGive your AI this first task
These editorial task examples follow the author’s documentation. Replace paths and material before use; expected deliverables are not outputs from an Atlasnote test run.
Use obsidian-markdown to organize the three project notes I provide. Read the actual files first, identify the vault root and confirm the permitted Projects/Pilot scope. Preserve facts, quotations, filenames and existing properties. Propose consistent project, status and source properties; leave missing information empty and list it. Link only to existing notes and create Projects/Pilot/index.md, separating established facts from open questions. Deliver a file-by-file change list. Check property syntax and the existence of links and embeds. Check reading view if Obsidian is available; otherwise mark application rendering as unverified.
Check what you receive
- Updated .md notes, a project index and a file-by-file change record.
- Preserved facts and quotations, consistent property types and links to real files.
- Separate records for file checks and Obsidian reading-view checks; unperformed checks remain pending.
More about this skill
This is a collection of instructions for an AI assistant. The current directory contains six members: obsidian-markdown, obsidian-bases, json-canvas, obsidian-cli, defuddle and knap. Each explains a file format or tool workflow. You still need to supply real material, a working directory and a task after installation.
The first three work with files. Markdown stores text, properties and links. Canvas arranges material using positions, groups and edges. Bases stores filters, formulas and view definitions while the underlying data remains in notes and their properties. These formats can reference the same notes without duplicating their text for each new view.
The remaining members use specific tools. Obsidian CLI interacts with the desktop application; Defuddle extracts page content; Knap renders structured data through templates and can format extraction results as notes. Each has its own setup conditions. Skill discovery is separate from a successful tool connection.
This suits people with an existing Obsidian vault who want to organize material or reduce repeated data entry. Define the scope and preservation requirements, then inspect a few examples before expanding. Valid file syntax still needs checks for working links, meaningful properties, reading view and canvas layout. Atlasnote reviewed documentation and format contracts, without running these skills against a private vault.
Sources and verification
Sources checked
Reviewed the README, all six SKILL files, the plugin manifest and current CLI help. No external tools were installed, no private vault was read and editorial examples are not presented as tested output.