Security audit

Work Productivity Ontology Typed Workflow Helper

Security checks for vulnerabilities and agentic risk

Overview

This is a low-risk documentation-only workflow helper, though its automatic trigger wording is broader than ideal.

This skill is reasonable to install if you want structured workflow help, but expect it may be invoked too often because its triggers include broad terms like knowledge, graph, memory, creating, and bug fix. Consider narrowing or disabling implicit invocation if precise routing matters.

A.I.G

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

SkillSpector

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

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The skill description and usage guidance are scoped to very broad concepts like work-productivity, ontology, knowledge, graph, workflow, artifact, checklist, analysis, and implementation support. In an auto-routing or trigger-based skill system, this can cause the skill to activate for many unrelated user requests, leading to misrouting, over-collection of context, or bypass of more appropriate specialized skills.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The keyword trigger list contains highly generic terms such as "typed," "knowledge," "graph," "structured," "memory," "creating," and "bug fix," which are common across many benign requests. If used for automatic invocation, these triggers can cause frequent false matches and unintended skill execution, reducing reliability and potentially exposing user context to an irrelevant workflow.
Content: No source excerpt is available for this finding.

Vague Triggers

High

Category: Not specified by scanner
Confidence: 98% confidence
Finding: The trigger sentence begins with a very generic phrase ('Help me') and then embeds broad requirement text, which can cause the skill to activate for many unrelated user requests. In an agent ecosystem, overbroad activation can route conversations into the wrong skill, leading to inappropriate guidance, confused task execution, or unsafe workflow substitution when the user did not intend to invoke this capability.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 97% confidence
Finding: The trigger sentences are generic and semantically broad, so the skill may activate for loosely related requests rather than clear user intent. In an agent ecosystem, unintended invocation can route user data or task execution into the wrong workflow, causing confusing behavior, unnecessary actions, or unsafe automation chaining.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 84% confidence
Finding: This file presents the user-facing documentation entirely in Chinese, while the skill audience description includes broad international users and does not state that the skill is China-specific. Under the policy, forcing a specific language without user opt-in or justification is a natural-language locale violation.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The trigger phrases are broad, generic, and closely match normal user requests for help, workflows, bug fixes, or implementation support. This can cause the skill to activate in unintended contexts, increasing the chance of prompt/skill hijacking, incorrect routing, or over-application of the skill beyond its intended ontology/work-productivity scope.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The trigger keyword list includes very generic terms such as "typed", "knowledge", "graph", "structured", "memory", and "creating", which can match many unrelated user requests. This can cause unintended skill activation, leading the agent to apply the wrong workflow or expose users to irrelevant or unsafe guidance in contexts where this skill was not intended.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The example trigger phrases are written in broad natural language and can match ordinary requests that merely mention help, workflows, bug fixing, or hardening, without clearly requiring this specific ontology-oriented skill. This increases the chance of accidental invocation and incorrect routing, which can degrade reliability and produce inappropriate outputs for unrelated tasks.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The default prompt is broad, truncated, and not tightly scoped to a specific user intent, which can cause the platform to invoke this skill in situations only loosely related to the requested task. In a security context, ambiguous invocation text increases the chance of unintended delegation, confusing task routing, or use of the skill with inputs it was not designed to handle safely.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: Enabling implicit invocation without clear trigger constraints allows the system to auto-select this skill for loosely matching requests, which can lead to overbroad activation and unintended handling of user data or workflow actions. Because the skill describes a wide range of support activities, the lack of constraints makes misrouting and unsafe autonomous use more likely.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The phrase 'I need a practical workflow for ... fixing bugs, hardening' is still broad enough to match many common software-assistance requests without confirming that the user wants this specific ontology-typed workflow helper. Because the skill is positioned to provide implementation support, ambiguous triggering increases the chance of accidental invocation and misapplication in contexts with different security, reliability, or domain requirements.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 76% confidence
Finding: The README states that English and Chinese variants of the skill instructions and guides exist, but it does not tell the user how language selection is determined or offer an explicit choice. For organizational language/locale policy, skills should make language selection user-driven or clearly documented.
Content: No source excerpt is available for this finding.