Screenshot
Capture desktop, window, or region screenshots for store assets, design critique, and reproducible bug visuals.
Overview
screenshot is an agent skill most often used in Launch (also Build, Ship) that captures desktop, window, or region images for marketing, design review, and bug documentation.
Install
npx skills add https://github.com/nexu-io/open-design --skill screenshotWhat is this skill?
- Desktop, application window, and pixel-region capture across OS platforms
- Open Design catalogue entry with upstream bundle at github.com/openai/skills
- Trigger phrases: screenshot, capture screen, window screenshot, pixel region capture
- Oriented to marketing screenshots, design reviews, and bug reports
- Install upstream skills bundle locally before running full workflow assets
Adoption & trust: 811 installs on skills.sh; 61.4k GitHub stars.
What problem does it solve?
You need consistent, agent-invokable screen captures for distribution or review instead of manual OS shortcuts and unnamed attachments.
Who is it for?
Solo builders preparing launch visuals, sharing UI state in reviews, or filing visual bug evidence through the agent.
Skip if: Automated visual regression CI, video recording, or teams that already standardized on a dedicated capture MCP with no Open Design routing.
When should I use this skill?
User says screenshot, capture screen, window screenshot, or pixel region capture.
What do I get? / Deliverables
You get platform-aware screenshot capture invoked by skill name or triggers, with a clear path to install the upstream OpenAI skills bundle for the full workflow.
- Image file or artifact from desktop, window, or region capture
- Documented install path to upstream screenshot skill
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch distribution is the canonical shelf because marketing and release collateral are the headline trigger, even though the same captures support design and QA. Distribution subphase covers outward-facing visuals—store shots, social crops, and campaign-ready frames—not just internal UI polish.
Where it fits
Crop hero and feature slides for a Product Hunt or app-store submission.
Capture a component window for async design review before merging UI changes.
Attach a pixel-perfect region capture to reproduce a layout bug in a ticket.
How it compares
Catalogue pointer plus upstream workflow—not a built-in OS screenshot API or generative image model.
Common Questions / FAQ
Who is screenshot for?
Solo and indie builders using Open Design–aware agents who need repeatable screen capture for marketing, design, or support workflows.
When should I use screenshot?
Use it in Launch for marketing and store assets, in Build for design reviews and spec alignment, and in Ship when documenting bugs with window or region captures.
Is screenshot safe to install?
Treat screen capture as sensitive (windows may expose secrets); review the Security Audits panel on this page and inspect the upstream github.com/openai/skills bundle before installing.
SKILL.md
READMESKILL.md - Screenshot
# screenshot > Curated from OpenAI's skills repository. ## What it does Capture desktop, app windows, or pixel regions across OS platforms. Useful for marketing screenshots, design reviews, and bug reports. ## Source - Upstream: https://github.com/openai/skills - Category: `screenshots` ## How to use This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory: ```bash # Inspect the upstream README for exact paths open https://github.com/openai/skills ``` Then ask the agent to invoke this skill by name (`screenshot`) or with one of the trigger phrases listed in this skill's frontmatter.