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 low-risk travel photography planning helper that provides local, descriptive JSON guidance without network access, persistence, credentials, or system changes.
Installers should understand that this is a descriptive planning skill, not a live travel or booking tool. It should be safe for ordinary use, but publishers could improve it by narrowing activation phrases and explicitly documenting language behavior.
Referenced artifact was not completely inspected
- `SKILL.md` - Complete documentation (this file)
Without declared permissions the skill's intent is opaque and cannot be validated.
The manifest declares language: en, and the acceptance criteria explicitly state "English documentation primary," yet the file also includes a Chinese usage scenario. This creates a language policy inconsistency that suggests a default language is being imposed rather than offering a documented user language choice or opt-in.
The trigger keywords are broad terms like 'photography', 'story', and 'memory if applicable', which can cause the skill to activate outside its intended domain. Overbroad invocation increases the chance of unintended routing, irrelevant prompting, or misuse of the skill in contexts where its guidance is not appropriate.
The non-functional requirement "English documentation primary" is a natural-language locale constraint, but the file does not explain that users can choose another language or why English-only primacy is required. Under the stated policy, forcing a specific language without opt-in is a violation unless clearly justified.
The manifest sets the skill language to "en" with no indication that users can choose another language or that the skill is intentionally limited to an English-only, region-specific use case. This is a natural-language policy concern because it imposes a locale constraint without opt-in or justification.
The README presents one example scenario entirely in Chinese while the rest of the document is in English, but it does not explain language-selection behavior or indicate that multilingual output is optional. This can imply a locale-specific response mode without explicit user opt-in, which falls under the language/locale policy concern.
The example prompts rely on generic phrases like 'help me with' and 'provide framework', which weakens domain boundaries and may encourage accidental invocation by loosely related requests. While not a direct exploit primitive, this ambiguity can lead to misclassification and unintended execution of the skill's logic in broader conversations.