ClawHub

Obsidian Tasknotes

Security checks across malware telemetry and agentic risk

Overview

This skill coherently manages Obsidian TaskNotes through a local API, but users should enable API authentication and be careful with updates or deletes.

Install only if you want an agent to manage your Obsidian TaskNotes. Enable a TaskNotes API token, keep the .env file private, ensure the API is only reachable on localhost, and require explicit confirmation before deleting or bulk-updating tasks.

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 (2)

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill exposes a delete operation for task files without any warning, confirmation, or guidance to verify user intent before destructive actions. Because it targets user notes/tasks in Obsidian, accidental or prompt-induced deletion could irreversibly remove personal work data.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The documentation explicitly allows running the TaskNotes HTTP API with no authentication and does not warn about the security or privacy consequences. Even though the API is described as localhost-based, unauthenticated local services are exposed to abuse by other local processes, browser-based localhost access patterns, or misconfiguration that binds beyond loopback, enabling unauthorized reading or modification of task data.

VirusTotal

46/46 vendors flagged this skill as clean.

View on VirusTotal