Back to skill

Security audit

Ui Cloner

Security checks for vulnerabilities and agentic risk

Overview

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.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)

T09 · Insecure Skill Coding Practices

Error
Location
SKILL.md:101
Finding

Shell Command Injection Through Unvalidated Packaging Arguments

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:55
Finding

Unconstrained Filesystem Writes Through User-Controlled Names and Output Paths

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Session Persistence

Medium
Category
Rogue Agent
Confidence
88% confidence
Finding

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.

Content

Scanner excerpt · SKILL.md (reported line 3)May include surrounding context.

md
---
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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Skill Enumeration

Medium
Category
Agent Snooping
Confidence
85% confidence
Finding

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.

Content

Scanner excerpt · SKILL.md (reported line 29)May include surrounding context.

md
**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