Back to skill

Security audit

Work Productivity Obsidian Vaults Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only workflow helper with overbroad activation wording but no evidence of malicious behavior, credential access, persistence, or hidden execution.

This skill appears safe to install from a security standpoint, but users should expect possible accidental activation on broad productivity or markdown-related prompts. Prefer invoking it explicitly for Obsidian or vault workflow tasks, and publishers should narrow the trigger wording before relying on implicit invocation.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (11)

Vague Triggers

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger phrases are broad, generic, and include common productivity terms such as "work," "plain," and "I need a practical workflow," which can cause the skill to activate for many ordinary requests unrelated to the intended Obsidian-vault use case. Over-broad activation increases the chance of incorrect tool routing, unintended instruction injection into unrelated conversations, and user confusion about why this skill was invoked.

Content

No source excerpt is available for this finding.

Vague Triggers

High
Category
Not specified by scanner
Confidence
94% confidence
Finding

The invocation description uses broad phrases like 'work-productivity', 'work', and 'practical workflow' without clear scope boundaries, making it easy for unrelated user requests to match. This creates prompt-routing ambiguity and increases the chance of unintended activation, which can misdirect the agent and expose users to irrelevant or lower-priority instructions.

Content

No source excerpt is available for this finding.

Vague Triggers

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger keyword list is overly broad and includes common terms like 'work', 'plain', and 'via', which can cause the skill to activate for many unrelated requests. In an agent system, this can lead to incorrect routing, unneeded context injection, and accidental use of the skill in situations where it was not intended, reducing reliability and potentially interfering with safer or more appropriate skills.

Content

No source excerpt is available for this finding.

Vague Triggers

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger keyword list includes very broad everyday terms such as "work", "plain", "markdown", "notes", and "automate", which can match many unrelated user requests and cause the skill to activate unintentionally. Over-broad activation can route users into the wrong workflow, override more appropriate skills, and increase exposure to prompt-scope confusion in multi-skill environments.

Content

No source excerpt is available for this finding.

Vague Triggers

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger sentences start with generic phrases like "Help me" and "I need," which are common in ordinary user requests and can cause the skill to activate when the user did not specifically intend to invoke it. In an agent ecosystem, overbroad invocation patterns can route unrelated conversations into this skill, causing mis-execution, confusion, and potential policy or workflow bypass if the skill takes actions or shapes outputs unexpectedly.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrases are broad enough to match common productivity and note-taking requests, which can cause the skill to activate in situations far beyond its intended scope. In an agent ecosystem, overbroad routing can override more appropriate skills, cause unintended file/workflow actions, and increase the attack surface for prompt or workflow misuse.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The example trigger sentences are highly generic and mostly repeat broad marketing language rather than concrete user intents. This encourages loose matching behavior and gives downstream systems little guidance on what should or should not activate the skill, increasing accidental invocation risk.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The skill description says it should be used when users mention broad terms like work-productivity, work, vaults, or plain, or whenever they need practical workflow or implementation support for the requirement. This creates unclear boundaries for invocation, making the skill eligible for many unrelated requests and increasing the chance of accidental or competing activation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The example trigger phrases use generic help-seeking language like "Help me" and "I need a practical workflow," which are common across many benign requests. When paired with the already broad scope, these examples reinforce permissive matching behavior and make unintended activation more likely.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill enables implicit invocation without any visible trigger constraints, which can cause the agent to auto-select this skill in situations broader than intended. That increases the chance of inappropriate activation, prompt-scope confusion, and unintended exposure of user context to a skill that was not explicitly requested.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

This file is a Chinese-language README, and within the file there is no user-facing note offering language selection or opt-in for locale. Because language-policy findings apply to natural-language content, presenting instructions in a fixed locale without an explicit choice can be a policy concern unless clearly justified.

Content

No source excerpt is available for this finding.