Security audit
Security checks for vulnerabilities and agentic risk
This skill is a documentation-only workflow for improving error messages, with no evidence of hidden execution, data access, persistence, or destructive behavior.
Safe to install from a security standpoint. Be aware that its broad trigger wording may make it appear for general debugging or support prompts, so invoke it explicitly when you want help rewriting or structuring error messages.
The trigger sentence is so generic that it can match ordinary user requests about help, workflows, support, or error messages, causing the skill to activate outside its intended scope. In an agent system, overly broad activation can route unrelated prompts through this skill, creating prompt hijacking opportunities, incorrect tool selection, or unintended influence over responses.
The trigger sentence is phrased as a very broad natural-language request ('Help me ...'), which increases the chance that the skill activates unintentionally during ordinary conversation. In an agent system, unintended activation can route user input into the wrong workflow, causing confusion, context hijacking, or undesired handling of data even without explicitly malicious content.
This trigger uses a generic request form ('I need a practical workflow for ...') without strong boundaries, so many unrelated support or productivity queries could accidentally match. In multi-skill environments, such broad matching can cause misrouting, unexpected execution of skill instructions, and reduced operator control over when the skill is invoked.
The trigger phrases are very broad and map to common, everyday requests such as debugging, support, and productivity help. In an agent-routing system, this can cause the skill to activate outside its intended scope, potentially intercepting unrelated user requests and influencing downstream behavior or outputs in ways the user did not explicitly ask for.
The manifest description uses very broad invocation terms like work-productivity, debugging, user feedback, and support, which are common across many unrelated requests. This can cause unintended skill activation and routing collisions, leading the agent to apply this skill outside its narrow purpose of improving error messages and troubleshooting artifacts.
The trigger keywords include broad, high-frequency terms such as debugging, support, troubleshooting, and user feedback without contextual constraints. In an agentic environment, ambiguous triggers can over-match ordinary conversations and invoke the skill when it is not relevant, increasing the chance of misrouting and inappropriate task handling.
The example trigger starts with 'Help me', which is an extremely common conversational phrase and is not meaningfully tied to this skill's specialized function. This raises the likelihood of accidental invocation from normal user dialogue, causing prompt-selection errors and potentially suppressing better-matched skills.
The description defines the skill's usage boundary too broadly, covering general work-productivity, debugging, support, and implementation help rather than a tightly scoped error-message-improvement task. This ambiguity can lead to accidental routing of sensitive or unrelated tasks into this skill, expanding its effective authority and making misuse or overreach more likely.
The trigger section uses very broad generic keywords such as 'debugging', 'support', and 'user feedback', which can match many unrelated requests and cause the skill to be invoked outside its intended scope. Over-broad invocation increases the chance of prompt hijacking-by-selection, user confusion, or the model applying this workflow when a more appropriate or safer skill should handle the task.
The skill enables implicit invocation, but the trigger conditions are broad and underspecified. That can cause the agent to invoke this skill in contexts involving debugging, support, or productivity requests where the user did not explicitly request it, increasing the chance of unintended prompt routing, surprise behavior, or misuse of the skill in adjacent contexts.
The invocation examples do not set clear boundaries for when the skill should or should not activate, so common phrasing like 'help me' or 'I need a practical workflow' may spur activation on many benign prompts. This increases the risk of accidental skill execution, misrouting, and prompt-surface expansion in multi-skill environments.
The file lists English and Chinese instruction and guide files, but does not state how language selection is determined or whether the user's preferred language is respected. Because locale/language handling is a policy-sensitive area, documentation should explicitly indicate user choice or opt-in rather than implying a fixed or automatic language behavior.
Natural-language policy review applies to all file types. In a zh-CN README, the operational guidance and trigger phrases are presented in English only, which effectively forces a specific language for key interaction steps without stating that users may choose their preferred language.
No suspicious patterns detected.
