store-screenshots
Skill3 starsChanged 9 days agoLicence not identifiedView on GitHub
Plans, writes and designs App Store and Google Play screenshots that explain what an app does and don't look AI-generated - from the app's real screens. It extracts the app's visual DNA (palette, fonts, signature elements), develops three app-specific concepts, composes every shot freely as a scene (layers, not templates) with checks that the real UI is never altered and every claim is on screen, and exports pixel-exact PNGs plus editable SVGs for every store size. Includes a classified library of 1,700+ real top-chart screenshots with searchable headlines and verdicts, category playbooks, copy rules, store-spec checks and a peer test. Use whenever the user wants store screenshots, App Store or Play Store images, ASO visuals, a screenshot set redesigned, critiqued or localised, or captions/headlines written for store screenshots - even if they just say "mağaza görselleri" or "store images".
- Installs packages
4 other projects use a version of this.
Adopted by
Most recently taken up by
- getpaseo/paseotheir own version, first seen Nov 1, 2026
- saif-o99/app-launch-skillstheir own version, first seen Oct 13, 2026
- vishal-mandhane/divinitytheir own version, first seen Sep 25, 2026
- LeeHueeng/store-screenshotstheir own version, first seen Aug 23, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- getpaseo/paseo★ 23ksame name
- LeeHueeng/store-screenshots★ 74same name
- vishal-mandhane/divinity★ 3same name
- saif-o99/app-launch-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 12 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.