T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned Global Installation of a Third-Party CLI
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent tennis travel planner, but it asks users to install an unpinned global CLI and includes unsafe shared temporary-file handling.
Install only if you trust the flyai CLI publisher and are comfortable sending travel details to flyai. Prefer a pinned, project-local CLI install and avoid running the bundled script on shared machines unless its output directory is changed to a private per-run location.
SKILL.md:19Unpinned Global Installation of a Third-Party CLI
scripts/plan-trip.sh:22Predictable Shared Temporary Directory Allows Symlink Attacks and Result Tampering
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
6. Practical tips (visa, weather, transport, etiquette)
7. Source attribution: "Based on fly.ai real-time results"
## Output rules
- All output in valid Markdown
- Hotel images: ``
The skill directs the agent to collect travel details such as departure city and trip dates, then transmit them to external flyai APIs, but it provides no instruction to disclose that sharing to the user or obtain consent first. This creates a privacy and transparency issue because sensitive itinerary information may be sent off-platform without the user understanding where their data is going.
This markdown template forces a specific language/locale in its user-facing content, including headings and itinerary text, with no indication that users can opt into another language. That is a natural-language policy concern under the locale-choice rule because the file appears intended for end-user output.
Several parameter descriptions require city names in Chinese, and the examples throughout the file are exclusively Chinese-language inputs. This creates a locale/language constraint in the skill documentation without offering a user choice or explaining why the restriction is required.
The reference data includes flyai dest-name values in Chinese, which imposes a specific language representation in a shared data file. Because the file does not state that Chinese output is optional, user-selected, or required for a region-specific integration, this creates a natural-language locale policy concern.
The POI category labels are written in Chinese in a general-purpose reference markdown file, which can force a specific language/locale on downstream skill behavior. No nearby text explains that Chinese is required by an external API or that the user can choose another language.
This destination-name field is encoded in Chinese in a file otherwise written in English, signaling a forced locale without opt-in. The absence of justification or alternative locale handling makes this a policy-style natural-language issue.
These category values are presented only in Chinese even though the rest of the file is English, which can constrain downstream outputs or API requests to a single locale. There is no documented user opt-in or regional requirement to justify the language restriction.
The flyai dest-name value is supplied only in Chinese, which is a language-specific policy choice in an otherwise English document. Without explanation or opt-in, this may cause the skill to force a language the user did not request.
The recommended category tokens are provided solely in Chinese and could be propagated into generated responses or searches. The file does not indicate that Chinese is mandatory for an external system or that users can choose a different language.
This field uses a Chinese city name inside a broadly applicable English reference file, which constitutes a language-specific constraint. Because no locale rationale or user choice is provided, it may violate language/locale policy expectations.
The category names are specified only in Chinese, which can steer downstream behavior toward a fixed locale. The markdown does not justify this as a region-specific requirement or offer any opt-in/out mechanism.
The skill is scoped to tennis event travel planning, but it also performs a visa-related search using the user's destination country. This is a scope expansion beyond the stated purpose and can cause the agent to collect or infer immigration-related information the user did not request, increasing privacy and data-minimization risk. In a travel-planning context this is somewhat plausible, but because the skill description explicitly says it is for Grand Slam itinerary generation rather than general travel/immigration assistance, the extra query is unjustified.
The document repeatedly frames guidance specifically for 'Chinese passport holders' and uses Chinese-language search queries, which signals a fixed locale/audience assumption rather than a user-selected preference. Because this is natural-language guidance in a markdown file and no opt-in or audience limitation is stated, it can be interpreted as a locale-specific policy choice without user choice.