Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md | `SKILL.md` | Full design document (this file) |
Security audit
Security checks for vulnerabilities and agentic risk
This is a China-focused restaurant review analysis skill with a local sample-data CLI and no evidence of hidden execution, credential access, persistence, or data exfiltration.
Before installing, treat it as a China/Dianping-oriented helper and note that the documentation's future scraping/cache language should be clarified if used with real public review data. The current packaged script is local and sample-data based, with no credential use or write actions found.
Referenced artifact was not completely inspected
| `SKILL.md` | Full design document (this file) |
The skill states that scraped review data is 'never stored beyond session', but elsewhere documents caching data for 1 hour and using cached data when scraping is blocked. This is a real data-handling inconsistency: operators or users may rely on stricter privacy guarantees than the implementation actually provides, leading to undisclosed retention of scraped content and metadata.
This code file contains extensive hard-coded Chinese phrases, keywords, sample data, and CLI defaults tailored to Chinese-language input and Shanghai-specific output. Because the skill does not provide a documented language or locale choice, it effectively forces a specific language/locale behavior, which matches the policy-violation category for language or locale constraints without user opt-in.
The document consistently uses Chinese inputs, Chinese output examples, and Chinese keyword-based sentiment logic, but it does not explicitly state that users may choose their preferred language or that Chinese is required for a justified region-specific reason. This can be read as forcing a specific language/locale without opt-in.
The sample prompts and first-success path show many natural-language ways to invoke the skill, but the document does not define a bounded trigger set or clarify when these phrases should or should not activate the skill. This can make activation scope ambiguous because common recommendation-style requests could overlap with ordinary conversation in a broader assistant context.
This JSON file includes a hard-coded list of generic phrases entirely in Chinese, which suggests the skill's fake-review heuristics are tailored to a specific language without documenting user opt-in or regional scope. Under the natural-language policy rules, forcing a specific language/locale without choice or justification is a policy concern.
This manifest-like JSON schema includes natural-language descriptions that assume a Chinese locale, using only Chinese location examples and CNY as the budget unit. Because the file does not document that the skill is region-specific or offer any locale choice, it can be read as imposing a specific language/locale by default.
This JSON schema file includes natural-language enum values for meals that are fixed to English only. Because SQP-3 applies to all file types, this can be considered a locale/language policy concern when the skill otherwise appears tied to a Dianping restaurant context and the schema provides no user opt-in or documented locale rationale.
The skill is framed around Dianping and its example commands require Chinese text such as '川菜' and '老王川菜', which indicates a fixed language/locale expectation. The file does not state that the skill is China-specific by design or offer any language choice, so this appears to be an implicit locale restriction in natural-language content.
No suspicious patterns detected.