ClawHub

Sync Obsidian

Security checks across malware telemetry and agentic risk

Overview

This skill does what it says: saves Claude Code plans and reports into a user-configured Obsidian vault, with local persistence users should understand.

Install only if you want plans, file paths, design decisions, and session summaries saved into your Obsidian vault. Review notes before syncing sensitive work, avoid including secrets, and enable the optional CLAUDE.md auto-sync only if you want future sessions to perform this automatically.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (5)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill is explicitly designed to write session-derived content into a user-configured Obsidian vault, but it does not prominently warn that this can persist potentially sensitive plan or report data outside the immediate session. Because invocation is framed as automatic and zero-config, users may not realize that internal project details, filenames, or conversation-derived content will be copied into long-lived notes.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The report-generation instructions require inclusion of implementation details such as changed files, design decisions, and follow-up work, yet they omit any warning that these details may expose sensitive repository structure or confidential engineering context when synced to external notes. This increases the chance of unintentional data disclosure, especially if the Obsidian vault is synced to cloud storage or shared devices.

Ssd 3

Medium
Confidence
95% confidence
Finding
The instruction to preserve and sync full plan content encourages wholesale copying of session-derived material into persistent storage without any filtering for secrets, credentials, internal URLs, or other sensitive user-provided content. Since plans may contain copied snippets from conversations or project context, this creates a direct data leakage path from the session into the vault.

Ssd 3

Medium
Confidence
96% confidence
Finding
The plan template explicitly mandates preserving the original plan content in full, which institutionalizes copying raw session material into a durable external note. That is dangerous because users often include sensitive technical details in planning discussions, and the template gives no opportunity for minimization or redaction.

Ssd 3

Medium
Confidence
95% confidence
Finding
The report workflow instructs the agent to summarize the current session and include detailed file changes and design rationale, which can reveal sensitive implementation details, internal architecture, or proprietary work in an external vault. In this context, the skill's purpose is data export, so the danger is not code execution but unauthorized persistence and disclosure of confidential session context.

VirusTotal

61/61 vendors flagged this skill as clean.

View on VirusTotal