Work Productivity Obsidian Vaults Workflow Helper

• Outcome: Pass
• Latest audit: Jun 20, 2026 at 3:31 PM UTC
• Version:
  0.1.0

Overview

This is a documentation-only workflow helper with overly broad activation wording but no evidence of hidden execution, credential access, persistence, or data exfiltration.

Install only if you want a broad Obsidian/workflow planning helper. Be aware it may trigger on generic productivity or note-taking requests, so prefer explicit invocation or tighten the trigger wording if your environment supports editing skill metadata.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (10)

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The trigger sentences are broad and partially generic, so the skill may be invoked for loosely related requests rather than clear user intent. In an agent ecosystem, unintended invocation can cause workflow hijacking, irrelevant actions, or accidental use of this skill in contexts where another tool should have been selected.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger phrases are broad enough to match ordinary productivity or note-taking requests, which can cause the skill to activate outside its intended scope. In an agent ecosystem, overbroad activation increases the chance of unintended workflow takeover, misleading outputs, or accidental invocation in contexts involving sensitive work artifacts.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger keywords include very broad terms such as "work," "plain," and "via," which are common in ordinary conversation and can cause the skill to activate outside its intended scope. Overbroad activation increases the chance of prompt-routing mistakes, unintended tool usage, or interference with more appropriate skills, especially in multi-skill agent environments.

Vague Triggers

High

• Confidence: 93% confidence
• Finding: The description says to use the skill when a user asks for broad categories like "work-productivity," "work," or needs almost any "workflow, artifact, checklist, analysis, or implementation support," which creates weak boundaries around invocation. In an agent system, this can lead to accidental selection for unrelated tasks, reducing reliability and potentially exposing users to incorrect or overly privileged workflow execution paths.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The example trigger sentences are vague, repetitive, and unrealistic, so they do not meaningfully constrain when the skill should be invoked. Poor examples can train maintainers or routers to match on generic wording, reinforcing accidental activations caused by the already broad scope.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger list includes very generic words such as "work", "plain", "markdown", and "notes", which are common in ordinary user requests and can cause the skill to activate unintentionally. Over-broad activation increases the chance that the agent applies this workflow in irrelevant contexts, leading to misrouting, prompt interference, or inappropriate access to user context intended for another skill.

Vague Triggers

Medium

• Confidence: 86% confidence
• Finding: The description says to use the skill when users ask for broad categories like work-productivity, obsidian, work, vaults, or plain, which does not clearly bound when invocation is appropriate. This ambiguity can cause accidental selection of the skill for loosely related requests, reducing reliability and potentially exposing unrelated tasks to this skill's instructions.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The default_prompt is vague and broadly phrased, and the skill also allows implicit invocation. That combination can cause the platform to activate this skill on loosely related user requests, increasing the chance of unintended behavior, prompt-context pollution, or accidental disclosure/modification within workflows the user did not explicitly choose.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger phrase is broad enough to match ordinary user language and can cause unintended skill activation outside the intended Obsidian/workflow context. In an agent ecosystem, overbroad routing can misapply this skill to unrelated prompts, leading to incorrect actions, confused outputs, or accidental exposure of user context to an irrelevant workflow.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: This activation pattern lacks clear scope boundaries and encourages invocation from generic requests for a 'practical workflow,' which is common across many domains. Such ambiguous routing increases the chance of prompt hijacking at the orchestration layer, where the wrong skill is selected and produces misleading or unsafe guidance for tasks it was not designed to handle.

VirusTotal

63/63 vendors flagged this skill as clean.