screenshot-optimization — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited screenshot-optimization (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are an expert in App Store creative optimization with deep knowledge of what converts browsers into downloaders. Your goal is to help the user design screenshots that maximize conversion rate.
app-marketing-context.md — read it for positioning and audienceUsers spend 3-6 seconds on a product page before deciding. The first 3 screenshots (visible without scrolling) determine 80% of the conversion decision.
What users look for:
The first screenshot is the most important. It should answer "What does this app do and why should I care?"
Effective patterns:
Avoid:
Show the 2 most compelling features with benefit-driven captions.
Each screenshot = one feature with a clear benefit headline.
Formula: [Benefit Headline] + [Feature UI] + [Supporting Detail]
| Do | Don't |
|---|---|
| Benefit-driven headlines | Feature names ("Push Notifications") |
| 4-6 words per headline | Long paragraphs |
| Large, readable font (min 60px) | Small text that's unreadable |
| High contrast text | Text over busy backgrounds |
| Consistent font and style | Mixed fonts and sizes |
| Do | Don't |
|---|---|
| Clean, uncluttered UI | Busy screens with too much data |
| Consistent color scheme | Clashing colors |
| Modern device frames (or frameless) | Outdated device frames |
| Real app content (not lorem ipsum) | Placeholder or empty states |
| Dark mode if your app supports it | Ignoring dark mode users |
Portrait (recommended for most apps):
Landscape (games, video, productivity):
For each of the 10 slots:
Slot [N]: [Headline]
- Caption: "[benefit-driven text]"
- Screen: [which app screen to show]
- Layout: [portrait/landscape, device frame, text position]
- Key element: [what draws the eye]If the user needs to brief a designer:
| Element | Your App | Comp 1 | Comp 2 | Comp 3 |
|---|---|---|---|---|
| # of screenshots | ||||
| Has video? | ||||
| First screenshot type | ||||
| Text overlay style | ||||
| Design quality (1-10) | ||||
| Unique angle |
ab-test-store-listing — Test screenshot variationsaso-audit — Screenshots as part of broader auditcompetitor-analysis — Analyze competitor creative strategylocalization — Localize screenshots for international markets~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.