obsidian — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited obsidian (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.
Tool-specific mechanics for working with Obsidian vaults.
A directory is an Obsidian vault if it contains .obsidian/ folder.
Syntax: [[Note Title]] or [[path/Note Title]]
[[Note Title|display text]]Obsidian stores settings in .obsidian/ at vault root:
| File | Purpose |
|---|---|
daily-notes.json | Daily note folder and template |
templates.json | Templates folder location |
zk-prefixer.json | Zettelkasten/inbox settings |
app.json | General settings (new file location, attachments) |
plugins/ | Installed plugin data |
// daily-notes.json
{
"folder": "Fleeting",
"template": "Templates/daily"
}
// templates.json
{"folder": "Templates"}
// zk-prefixer.json
{
"folder": "📫 Inbox",
"template": "Templates/frontmatter"
}
// app.json
{
"newFileFolderPath": "📫 Inbox",
"attachmentFolderPath": "🖇 Attachments"
}Finding today's note:
.obsidian/daily-notes.json for folderYYYY-MM-DD.md (Obsidian default){folder}/{YYYY-MM-DD}.mdTemplate application:
daily-notes.jsonIf Glossary.md exists at vault root:
Vaults should have a CLAUDE.md at root describing:
See templates/vault-claude-md.md for template.
When a vault has areas with semantic overlap (e.g., "tool sharpening" vs "software engineering"), the vault CLAUDE.md can include ### Disambiguation: sections that guide routing decisions.
The routing algorithm checks for:
See references/routing.md for the full disambiguation format and how to build custom rules.
For methodology (tool-agnostic):
references/para.md - PARA organizational systemreferences/zettelkasten.md - Naming conventionsreferences/note-patterns.md - Note templatesreferences/routing.md - Routing algorithm with disambiguation supportreferences/daily-linking.md - Linking captured notes to daily notereferences/pipeline.md - Processing pipeline stages and status flowreferences/routing-memory.md - Routing correction and learning loop~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.