Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - `SKILL.md` - Complete documentation (this file)
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a simple business-travel wellness planner that generates informational JSON and does not show hidden execution, network access, persistence, or credential handling.
Installers should treat this as informational wellness planning, not medical or employment advice. The main caveat is scope: it may activate for broad travel-wellness prompts, so users should verify health recommendations with appropriate professionals and official sources.
Referenced artifact was not completely inspected
- `SKILL.md` - Complete documentation (this file)
The first example scenario is entirely in Chinese and presents the response in Chinese without any indication that language is optional or user-selectable. This can violate language/locale policy expectations because the skill appears to prescribe a specific language style for at least some interactions without documenting opt-in or choice.
Without declared permissions the skill's intent is opaque and cannot be validated.
The trigger criteria are broad and include generic travel and wellness phrases, which can cause the skill to activate outside its intended niche. Overbroad activation increases the chance of prompt interception, unintended routing, or the skill influencing unrelated user requests with domain-specific guidance the user did not explicitly request.
The example prompts are phrased broadly enough to overlap with ordinary travel-planning requests, making accidental invocation more likely across unrelated contexts. In agent ecosystems, this can create prompt-squatting behavior where a loosely scoped skill captures traffic intended for more appropriate skills.
The manifest metadata declares language: en, and later requirements state "English documentation primary" while the document also contains a Chinese usage scenario. This creates a natural-language policy concern because the skill appears to impose an English-default locale rather than explicitly offering language choice to users.
The module documentation presents the skill as merely descriptive, which suggests static informational output. In practice, the handler inspects user input for destination, timeframe, budget, business, and routine cues and dynamically constructs recommendations and frameworks based on that analysis.
The manifest sets the skill language to "en" with no indication that users can opt into another language or that the skill is intentionally limited to English for a stated regional or compliance reason. This is a natural-language policy concern because it imposes a locale choice by default.