ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Screenshots

v1.0.1

Create professional App Store and Google Play screenshots with automatic sizing, device frames, marketing copy, and iterative visual learning.

⭐ 3· 704·4 current·4 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (app-store screenshots, templates, iterative learning) match the instructions and files. The SKILL.md and supporting docs only describe image sizing, templates, workflows and storing templates/preferences — nothing requests unrelated platform access or credentials.
ℹ
Instruction Scope
Instructions tell the agent to read/write files under ~/screenshots (memory.md, learnings.md, project config, versioned exports) and to use a vision model to verify screenshots. These file operations are coherent with the skill's purpose but grant the skill persistent access to a folder in the user's home directory; the skill also references optional local commands (e.g., xcrun simctl) as recommendations even though binaries are not declared as required.
✓
Install Mechanism
No install spec or code is provided — this is instruction-only, so nothing is written to disk by an installer and no external packages/URLs are pulled. That minimizes install-time risk.
ℹ
Credentials
The skill requires no environment variables, binaries, or external credentials (proportional). However it persists per-user learnings and preferences in the home folder which may include user-identifying notes; users should avoid storing secrets in those files.
ℹ
Persistence & Privilege
The skill explicitly creates and uses persistent storage at ~/screenshots (memory.md, learnings.md, versioned exports and symlinks). always:false and it does not modify other skills. Persistent storage is reasonable for this workflow but is a persistent presence in the user's home directory and may accumulate personal data over time.
Assessment
This skill is internally consistent and does what it says: it will create a ~/screenshots folder, read/write memory.md and learnings.md, and keep versioned exports. It does not request API keys or install software. Before installing: (1) confirm you’re comfortable with a skill writing persistent files under ~/screenshots and avoid putting secrets or sensitive screenshots there; (2) review the created files after first run and set filesystem permissions if desired; (3) if you don't want the agent to act autonomously with this persistent data, keep autonomous invocation disabled at the agent/platform level. If you need more assurance, ask the skill author for a minimal manifest that restricts paths or for an option to store data in a temporary/project-only folder.

Like a lobster shell, security has layers — review code before you run it.

latestvk973zv0fh8s2k38xq15mbj4r1x817jyf

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📱 Clawdis
OSLinux · macOS · Windows

SKILL.md

Quick Reference

ContextFile
Store dimensions and specsspecs.md
Marketing text overlaystext-style.md
Visual templates by categorytemplates.md
Full creation workflowworkflow.md
Learning from feedbackfeedback.md

Memory Storage

User preferences stored at ~/screenshots/memory.md. Read on activation.

Format:

# Screenshots Memory

## Style Preferences
- style: dominant-color | gradient | minimal | dark | light
- fonts: preferred headline fonts
- frames: with-frame | frameless | floating
- tone: punchy | descriptive | minimal

## Learned Patterns
- templates that converted well
- font/size combinations that worked

Create folder on first use: mkdir -p ~/screenshots

Workspace Structure

~/screenshots/
├── memory.md              # Style preferences (persistent)
├── {app-slug}/
│   ├── config.md          # Brand: colors, fonts, style
│   ├── raw/               # Raw simulator/device captures
│   ├── v1/, v2/           # Version exports
│   └── latest -> v2/      # Symlink to current
└── templates/             # Reusable visual templates

Core Workflow

  1. Intake — Get raw screenshots + app icon + brand colors
  2. Size — Generate all required dimensions per specs.md
  3. Style — Apply backgrounds, device frames, text overlays
  4. Review — Use vision to verify quality before sending
  5. Iterate — Adjust based on user feedback
  6. Export — Organize by store/device/language

Quality Checklist

Use vision model to verify EVERY screenshot set:

  • Text readable at thumbnail size?
  • No text in unsafe zones (corners, notch area)?
  • Consistent style across all screenshots?
  • Device frames match the target size?
  • Colors harmonious with app branding?

If ANY check fails → fix before presenting to user.

Versioning Rules

  • Never overwrite — each batch goes in v{n}/
  • Symlink latest to current approved version
  • config.md stores brand decisions for regeneration
  • Compare versions when user says "go back to the old style"

Files

6 total
Select a file
Select a file to preview.

Comments

Loading comments…