Word DOCX Formatting Repair

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 9:24 AM UTC
• Version: 1.0.1

Overview

This skill is a disclosed DOCX formatting repair workflow with no bundled executable code, persistence, credential use, or hidden data movement.

Installers should understand that the skill may inspect and modify DOCX files when asked to repair formatting. For sensitive legal or business documents, keep an original backup, review any repaired copy before use, and prefer explicit invocation for confidential files because implicit invocation is enabled.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• 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 (9)

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger sentences are generic and self-referential enough that the skill may activate for loosely related Word or document-automation requests without clear user intent. In an agent setting, overbroad activation can cause unintended invocation, context capture, or automated file-handling steps on sensitive business or legal documents, increasing the chance of harmful or privacy-impacting actions.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger phrases are broad, natural-language, and partially generic, which increases the chance the skill is invoked when a user is merely discussing Word or DOCX issues rather than explicitly requesting this specific workflow. In an agent environment, unintended invocation can route user content into an automation path that inspects or transforms documents unexpectedly, creating integrity and privacy risks even without malicious code.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The trigger description is broad enough to match many ordinary Word or productivity requests, not just narrowly scoped DOCX formatting-repair tasks. Over-broad routing can cause unintended invocation of this skill, leading the agent to apply the wrong workflow, make unsafe assumptions about document-handling tasks, or expose users to inappropriate automation steps in contexts such as legal or business documents.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The keyword list includes generic terms such as microsoft word, docx, and styles without contextual constraints, which makes accidental or excessive activation likely. In an agent setting, vague triggers can misroute unrelated requests into this skill, causing incorrect handling of user tasks and increasing the chance of unintended file-modification guidance for sensitive business or legal documents.

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The skill enables implicit invocation without any documented trigger constraints or exclusion conditions, which can cause the agent to auto-select this skill in broader contexts than intended. Because this skill is designed to inspect and repair DOCX internals, unintended invocation could expose document contents or lead to file-modifying actions when the user did not explicitly request this workflow.

Vague Triggers

Medium

• Confidence: 96% confidence
• Finding: The trigger sentence is so broad and awkwardly phrased that it can match ordinary requests far outside a narrowly intended DOCX-formatting workflow. Overbroad activation increases the chance the skill is invoked in irrelevant contexts, which can cause unintended instruction hijacking, user confusion, or the skill taking precedence over a more appropriate and safer capability.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: This trigger uses a generic request pattern ('I need a practical workflow for ...') combined with a long requirement statement rather than precise activation criteria. Such vague matching can cause the skill to activate on many benign productivity requests, broadening its authority and making prompt-routing errors more likely.

Natural-Language Policy Violations

Low

• Confidence: 62% confidence
• Finding: The README mixes English content with Chinese-linked evidence entries and references a Chinese user-facing guide, but does not explicitly state that language selection is optional or user-driven. This may create ambiguity around locale expectations, though it is not a strong violation because no explicit forced-language instruction is present.

Natural-Language Policy Violations

Low

• Confidence: 82% confidence
• Finding: This file is presented as a Chinese user-facing README, but core usage content and trigger phrases are written in English only. That can impose a language constraint on users without documenting a choice or opt-in, which fits the language/locale policy check.

Static analysis

No suspicious patterns detected.