T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is aimed at recipe extraction, but it needs review because it automatically downloads and analyzes reel media, installs an unpinned Python tool, and uses unsafe shared temporary files.
Install only if you are comfortable with the agent downloading public Instagram reels, transcribing audio locally, and sending extracted frames to the active vision model when captions are incomplete. Prefer a revised version that asks before audio/video analysis, uses pinned or isolated dependencies, and stores temporary media in a private per-run directory that is cleaned up afterward.
SKILL.md:5Unpinned Third-Party Dependency Installation
SKILL.md:34Predictable Shared Temporary Files Allow Collisions and File Clobbering
The README claims the skill can perform audio transcription, frame analysis, and smart inference, which materially expands the apparent behavior beyond the stated caption-extraction scope. Scope mismatch is dangerous because reviewers and users may grant the skill trust or permissions appropriate for a simple parser while it actually implies broader media acquisition and analysis behavior.
Advertising a wishlist capability inside a recipe-extraction skill suggests stateful data handling and cross-skill interactions that are not justified by the core purpose. Even if benign, unexplained data retention or integration features can expand attack surface and create confusion about what user data is stored or shared.
The documented workflow says the skill automatically escalates from caption parsing to audio transcription and then video frame analysis. That hidden fallback chain increases processing scope and risk, especially because it implies downloading and inspecting external media content without clearly surfacing that expanded behavior in the skill's declared purpose.
The manifest describes a caption-extraction skill, but the body expands behavior to downloading reels, transcribing audio, and analyzing frames with a vision model. This scope mismatch can defeat user and platform expectations about what content will be processed, reducing informed consent and making review or policy enforcement harder.
The skill mandates automatic video download, audio extraction, and transcription without a user-facing warning or consent step. Even for public reels, this is a meaningful expansion of processing that may surprise users and can capture spoken content they did not intend to have transcribed.
The skill includes writing recipe data to local storage but does not clearly warn users that data may be persisted to disk. Silent persistence can create privacy and retention issues, especially when storing source URLs, creator identifiers, dates, and user preference data.
Frame-based vision analysis materially expands the capability from caption parsing to full visual inspection of video content, which is not justified by the manifest's stated purpose. This broader access can expose additional on-screen personal or sensitive information and creates unnecessary collection beyond the minimum needed for the task.
The README describes automatic processing of Instagram reels, including implied downloading and analysis of external media, without warning users about that behavior. This matters because external media handling can trigger network access, large downloads, unexpected local tool execution, and privacy or policy concerns that users may not anticipate from a recipe-extraction skill.
The integration section describes saving recipes, planner suggestions, and tracking tried recipes. Those are downstream organizational features not necessary to extract a recipe from a reel caption, making them unjustified given the manifest's narrow extraction purpose.
The skill documents optional persistence to local files and cross-skill handoffs, but that behavior is not reflected in the manifest. Hidden storage and data-sharing behavior increases the chance that recipe URLs, creator handles, or user preferences are retained or propagated without clear user awareness.
No suspicious patterns detected.