Obsidian Vault Curator

AdvisoryAudited by Static analysis on May 12, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

You have less external context about the publisher or upstream source.

Why it was flagged

The package has no external homepage or source repository listed, so users have limited independent provenance information even though the included scripts are visible.

Skill content
Source: unknown; Homepage: none
Recommendation

Install only if you trust the registry copy and review the included files; no hidden remote dependency is shown.

What this means

If you approve edits, the agent may change your vault files; mistakes could affect organization or links.

Why it was flagged

The workflow allows the agent to make persistent note changes, but only after approval and with diff/link/frontmatter verification.

Skill content
After approval, and before changing files: ... change one slice ... inspect the diff ... verify links
Recommendation

Review each proposed write slice, keep backups or version control, and avoid approving broad moves or rewrites at once.

What this means

Private note contents may be loaded into the agent's context during analysis, and paths to suspected sensitive notes may be reported.

Why it was flagged

The inventory helper reads note bodies from the selected target and flags possible sensitive content by path, without printing the suspected secret value.

Skill content
with open(path, "r", encoding="utf-8") as handle:
            text = handle.read()
...
        if looks_sensitive_unverified(text):
            sensitive_candidates.append(rel)
Recommendation

Run it only on intended vault slices and avoid including folders with secrets unless you want them reviewed.

What this means

For large vaults, selected note context may be shared across multiple agent work streams.

Why it was flagged

The skill supports subagent use for larger vaults, but it explicitly bounds each subagent to one slice and keeps writes in the main agent by default.

Skill content
read-only subagents inspect in parallel if helpful ... main agent merges findings ... give each subagent one bounded slice only
Recommendation

Use subagents only for bounded, non-sensitive slices unless you explicitly want broader review.