← Back to Skills Marketplace
twworks-org

AppScreenshotStudio

by TW Works · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ⚠ suspicious
112
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install appscreenshotstudio
Description
Generate production-ready App Store and Play Store screenshots from your codebase. Reads your app's colors, screens, and copy — then creates a finished scree...
README (SKILL.md)

Generate finished App Store / Play Store screenshots directly from your terminal.

Setup

Requires APPSCREENSHOTSTUDIO_API_KEY in your environment. Get a key at https://appscreenshotstudio.com/settings (requires an account with credits).

When to use this skill

Use when the user says: "generate screenshots", "App Store screenshots", "Play Store screenshots", "store listing", "marketing screenshots", or wants to ship a new app.

Workflow

Step 1 — Research the codebase

Before calling the API, gather context from the project. This context directly improves the generated layouts, colors, and headlines.

Find and read:

  • README.md — app name, purpose, main features
  • package.json / pubspec.yaml / Cargo.toml / build.gradle — app name, tech stack
  • Brand colors: tailwind.config.* (theme.extend.colors), SwiftUI Color(, Flutter ThemeData
  • Key screens: Next.js app/ routes, SwiftUI NavigationView/TabView, Flutter GoRouter
  • App Store metadata: Info.plist, fastlane metadata/, AndroidManifest.xml

Build this context:

app_name, readme_summary, key_screens[], color_tokens{}, target_audience,
app_category (fitness|finance|social|productivity|food|travel|health|education|other),
competitive_edge, ui_style, primary_user_flow

Step 2 — Confirm with the user

Show what you found and ask:

  • "I found these main features: [X, Y, Z]. Which 3-5 should I highlight?"
  • "Your brand color appears to be [#hex]. Should I use it?"
  • "Mood? Options: minimal, bold, playful, professional, dark, warm, energetic"
  • "Device? iphone-6.9 (default), ipad-13, android-phone, android-tablet-10"
  • "How many screenshots? (3–8, default 5)"

Step 3 — Create project and generate

3a. Create a project:

curl -s -X POST https://appscreenshotstudio.com/api/v1/projects \
  -H "Authorization: Bearer $APPSCREENSHOTSTUDIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "device_id": "iphone-6.9",
    "name": "\x3Capp_name> Screenshots",
    "codebase_context": {
      "readme_summary": "...",
      "key_screens": ["..."],
      "color_tokens": {"primary": "#hex"},
      "target_audience": "...",
      "app_category": "...",
      "competitive_edge": "...",
      "ui_style": "...",
      "primary_user_flow": "..."
    }
  }'

Save data.id as PROJECT_ID.

3b. Generate the screenshot set via chat:

curl -s -X POST "https://appscreenshotstudio.com/api/v1/projects/$PROJECT_ID/chat" \
  -H "Authorization: Bearer $APPSCREENSHOTSTUDIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Create a 5-card screenshot set. Highlight: [feature1], [feature2], [feature3]. Mood: minimal. Use brand color #hex."
  }'

On success, data.canvas_state contains the generated layout. The response also includes data.message (Claude's description of what was created) and credits_remaining.

If data.operations is empty, Claude asked a clarifying question — no credits were deducted. Answer the question and call chat again.

Step 4 — Iterate if needed

If the user wants changes, call chat again on the same PROJECT_ID:

curl -s -X POST "https://appscreenshotstudio.com/api/v1/projects/$PROJECT_ID/chat" \
  -H "Authorization: Bearer $APPSCREENSHOTSTUDIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message": "Make the first card more playful. Change the headline to something punchier."}'

Step 5 — Render and export

Render the final PNGs at exact App Store dimensions (free, no credits):

curl -s -X POST "https://appscreenshotstudio.com/api/v1/projects/$PROJECT_ID/render" \
  -H "Authorization: Bearer $APPSCREENSHOTSTUDIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Returns data.images[] — array of CDN URLs. Download them or share the project URL: https://appscreenshotstudio.com/builder/\x3CPROJECT_ID>

Credit costs

  • Project creation: free
  • Chat (screenshot generation): 5 credits per message
  • Render: free
  • Clarifying questions (no operations generated): refunded automatically

Headline quality rules

When reviewing or suggesting headlines, enforce:

  • 3–5 words per line, readable at thumbnail size
  • Three styles: paint a moment ("Morning runs handled"), state an outcome ("Never miss a workout"), eliminate a pain ("Ditch the spreadsheet")
  • Never: feature lists, "and"-joined clauses, starting with "The", vague aspirational phrases

Error codes

  • NO_CREDITS (402) — user needs to top up at https://appscreenshotstudio.com/billing
  • PROJECT_LIMIT_REACHED (403) — plan limit hit
  • UNAUTHORIZED (401) — invalid or missing API key
  • NOT_FOUND (404) — project ID doesn't exist
Usage Guidance
This skill appears to do what it says (extract app info and call appscreenshotstudio.com), but be aware it will read many files from your repository (code, manifests, colors, copy) and send that context to a third-party API. Before installing or enabling it: 1) Confirm you trust appscreenshotstudio.com and review their privacy/billing policies; 2) Create an API key with minimal scope or use a throwaway/scrubbed project when testing; 3) Remove or sanitize any secrets or proprietary assets from the repo or provide a reduced context payload instead of raw files; 4) Ask the skill author/registry maintainer to update the registry metadata to declare APPSCREENSHOTSTUDIO_API_KEY so the credential requirement is explicit; 5) If you cannot sanitize data, avoid using this skill on sensitive codebases. Additional info (registry metadata, privacy promises from the service) would raise confidence if provided.
Capability Analysis
Type: OpenClaw Skill Name: appscreenshotstudio Version: 1.0.1 The skill is designed to automate the creation of App Store and Play Store screenshots by analyzing project metadata and source code (e.g., README.md, package.json, and UI components) to extract branding and feature context. It interacts with a legitimate-appearing external API (appscreenshotstudio.com) via curl to process this data and generate image assets. The file access and network activity are explicitly documented and strictly aligned with the stated purpose of the tool, with no evidence of unauthorized data access, persistence mechanisms, or malicious execution.
Capability Assessment
Purpose & Capability
The name/description (generate App Store / Play Store screenshots) aligns with the runtime instructions and the use of an external screenshots API. However, the registry metadata (Requirements section) says no required env vars while the SKILL.md clearly requires APPSCREENSHOTSTUDIO_API_KEY — this mismatch is unexplained and should have been declared in the skill metadata.
Instruction Scope
The SKILL.md explicitly instructs the agent to read many project files (README.md, package.json, Info.plist, AndroidManifest.xml, theme/colors, key screens, etc.) to build a detailed codebase context and then POST that context to the service's API. That scope is coherent for generating store screenshots, but it will transmit potentially sensitive or proprietary project content to a third-party endpoint and the instructions do not warn about sanitization or privacy considerations.
Install Mechanism
Instruction-only skill with no install spec or downloaded code — low risk from install/injection mechanics.
Credentials
The SKILL.md requires a single API key (APPSCREENSHOTSTUDIO_API_KEY), which is proportionate to the described external API usage. However, the registry metadata failed to declare this required environment variable (Requirements lists none). That mismatch reduces transparency and could mislead users about what credentials will be needed.
Persistence & Privilege
The skill does not request always: true, does not install anything, and does not modify other skills or system-wide settings. Default autonomous invocation is allowed (normal) but not combined with other elevated privileges here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install appscreenshotstudio
  3. After installation, invoke the skill by name or use /appscreenshotstudio
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Updated homepage URL from /claude-code-skill to /openclaw in metadata. - No functional or workflow changes.
v1.0.0
- Initial release of AppScreenshotStudio skill. - Generate production-ready App Store and Play Store screenshots from your codebase. - Automatically reads app colors, screens, and copy to create finished screenshots in the correct store dimensions. - Guides you through context gathering, user confirmation, and screenshot set generation. - Supports iterative editing and renders final PNGs for export. - Highlights credit costs and provides error code details for troubleshooting.
Metadata
Slug appscreenshotstudio
Version 1.0.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is AppScreenshotStudio?

Generate production-ready App Store and Play Store screenshots from your codebase. Reads your app's colors, screens, and copy — then creates a finished scree... It is an AI Agent Skill for Claude Code / OpenClaw, with 112 downloads so far.

How do I install AppScreenshotStudio?

Run "/install appscreenshotstudio" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is AppScreenshotStudio free?

Yes, AppScreenshotStudio is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does AppScreenshotStudio support?

AppScreenshotStudio is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created AppScreenshotStudio?

It is built and maintained by TW Works (@twworks-org); the current version is v1.0.1.

💬 Comments