obsidian-cli — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited obsidian-cli (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Always use the CLI over direct .md file edits — it runs through Obsidian's runtime so move updates links, create applies templates, property:set writes valid frontmatter.
Run obsidian help to discover commands. Run obsidian help <command> for params.
`file=<n>` resolves like a wikilink — no path or extension needed. `path=<path>` requires exact path from vault root.
Organize vaults using PARA:
Vault/
├── Projects/ # active work with a defined end state
├── Areas/ # ongoing responsibilities, no end date
├── Resources/ # reference material, things learned
├── Archive/ # completed or dead projects
├── Daily Notes/
├── Templates/
└── Attachments/Projects vs Areas: Projects have a finish line and move to Archive when done. Areas are permanent responsibilities that never "end".
Meeting notes live inside the relevant project folder, not a global folder.
Path: Projects/<Project>/<Project>.md
---
project: <name>
status: active
updated: <YYYY-MM-DD>
tags: [project]
---
# <Project Name>
## What & Why
What this is and why it exists.
## Current Status
Where things are right now.
## Decisions & Tradeoffs
- **<decision>** — why, and what was rejected
## Gotchas & Lessons
- Things that bit you or future-you needs to know
## Open Questions
- Unresolved thingsAppend tasks and quick references rather than creating new notes for small things:
obsidian daily:append content="- [ ] Task here"
obsidian daily:append content="- [[Project]] — note for references section"Wikilink liberally. Any time a known project, person, or concept appears in a note, link it: [[Project Name]], [[Person]].
Check before creating. A note may already exist:
obsidian search query="<topic>" limit=5Shallow structure. No nesting beyond Projects/<Project>/ except a Meeting Notes/ subfolder per project if needed.
Small tag set. Stick to: project, area, resource, decision, gotcha, question. Don't invent tags without a clear reason.
Archiving. Move don't delete:
obsidian move file="<Project>" to="Archive/"
obsidian property:set name=status value=done file="<Project>"obsidian daily:appendProjects/<Project>/Meeting Notes/<date> <topic>.mdResources/<topic>.mdupdated frontmatter with today's date~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.