T09 · Insecure Skill Coding Practices
- Location
SKILL.md:76- Finding
API Key May Be Disclosed Through Configuration Validation Commands
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a video-analysis integration, but its instructions include unsafe API-key handling and unclear disclosure about sending video content to a third-party service.
Review before installing. Use it only for videos you are allowed to send to DashScope, avoid sensitive or private media unless your organization approves that processing, and do not run the documented API-key grep command because it may print the secret. Prefer a pinned dependency version and a secret-presence check that never displays the key.
SKILL.md:76API Key May Be Disclosed Through Configuration Validation Commands
SKILL.md:68DashScope Dependency Is Installed Without Version or Integrity Pinning
At L010 the description says 'Use when 需要视频处理、音频编辑、媒体转换、配音生成时使用', implying the skill is suitable for audio editing, media conversion, and dubbing generation. But the rest of the document describes only video analysis and explicitly excludes editing/transcoding at L044 and L154, so the description actively contradicts the stated functionality.
The trigger language is overly broad and overlaps with common media-related requests such as video processing, audio editing, media conversion, and dubbing generation, even though the skill is actually for video analysis. In an agent ecosystem, vague activation criteria can cause the skill to run unexpectedly on unrelated user requests, leading to unintended file access, remote URL handling, or third-party API submission.
The description explicitly states "支持中文交互" in a way that frames Chinese as the expected interaction mode, and the document does not offer an opt-in or alternative language choice. For a general-purpose skill, this can violate language/locale policy by effectively forcing a specific language without user selection.
The description does not define clear trigger boundaries and uses ambiguous conditions for when the skill should be invoked. In practice, ambiguous routing can cause accidental execution with local files or remote URLs that the user did not intend to send through this skill, increasing exposure of sensitive media and unnecessary API usage.
The skill supports analyzing remote video URLs through a third-party multimodal API but does not clearly warn that the video content or fetched media may be transmitted to an external service. This creates a meaningful privacy and data-governance risk because users may supply internal, sensitive, or copyrighted video links without informed consent about external processing.
The skill gives inconsistent secret-handling guidance: earlier sections instruct reading the DashScope API key from local JSON files, while the security section claims keys should be provided via environment variables. Conflicting instructions increase the chance that implementers mishandle credentials, store them in unintended locations, or build unsafe workarounds when the documented method does not match the stated security model.
The feature callouts repeat that the skill covers "中文交互" but do not present this as an optional capability or justified regional limitation. Reiterating a single-language mode in prominent natural-language guidance can steer agents toward a fixed locale even when the user has not requested it.
No suspicious patterns detected.