T09 · Insecure Skill Coding Practices
- Location
SKILL.md:101- Finding
Shell Command Injection Through Unvalidated Packaging Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a coherent UI-cloning purpose, but its packaging and file-writing instructions are under-scoped enough that users should review it before installing.
Install only if you are comfortable with a skill that creates persistent UI-cloning artifacts. Use it only on UI screenshots you own or are authorized to reproduce, keep output project-local, avoid global installation, and sanitize product names and output paths before running the packaging step.
SKILL.md:101Shell Command Injection Through Unvalidated Packaging Arguments
SKILL.md:55Unconstrained Filesystem Writes Through User-Controlled Names and Output Paths
The skill is explicitly designed to generate a reusable .skill package that persists extracted UI design-system information for later reuse. If screenshots contain proprietary or confidential product designs, the agent may transform them into a durable artifact and optionally place it in a global skills directory, increasing the risk of unintended retention and reuse of sensitive intellectual property.
---
name: ui-cloner
description: "Analyzes UI screenshots and generates a reusable .skill file that captures the product's complete design system. Triggers when the user provides UI screenshots (single or multiple pages of the same product) and wants to clone, reproduce, or extract a design system from them. Input: one or more image file paths or a directory. Output: a ready-to-install .skill file encapsulating design tokens, component specs, layout structure, visual style, and interaction patterns. The generated skill can then be used (optionally invoking ui-ux-pro-max) to recreate the UI in any target tech stack."
---
# UI Cloner
The listed triggers include generic phrases like "clone this UI," "copy this design," and "reproduce this page," which can plausibly appear in ordinary design discussions and may cause unintended invocation. The file does not provide negative examples or clear exclusion conditions to distinguish this skill from other UI analysis or implementation skills.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
**Output location**: Determine the save path for the generated skill:
- If the user is currently in a project directory (i.e., the working directory has source files, a package.json, or similar), save the skill **inside the project** at `.claude/skills/{product-name}-ui/` and package the `.skill` file there as well.
- Only fall back to the global skills directory (`~/.claude/skills/`) if there is no identifiable project directory.
- Always tell the user where the skill will be saved before proceeding.
### Step 2 — Analyze Screenshots