How do I install the Screenshot skill?

Run npx skillmds@latest add kiku-jw/screenshot in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Screenshot safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Screenshot?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Screenshot free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Screenshot?

kiku-jw (@kiku-jw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Screenshot by kiku-jw — Agent Skill

Name: Screenshot
Author: kiku-jw

Screenshot

Capture desktop or system screenshots with the bundled OS helpers when the user explicitly asks for a screenshot or when tool-specific capture cannot reach the target. Supports full screen, app/window, active window, and region capture.

kiku-jw 35d410b 11 files · 45.5 KB Updated Sep 17, 2026

File contents

Screenshot Capture

Metadata

Trigger when: the user wants an OS-level screenshot or a better-integrated tool cannot capture the target surface.
Do not use when: a tool-specific screenshot path already solves the task more directly and faithfully.

Skill Purpose

Use the bundled helpers to capture desktop, app, window, or region screenshots predictably across platforms without re-deriving OS-specific commands every time.

Instructions

Choose the save-location rule first: user path if provided, OS default if the user just wants a screenshot, or temp storage when Codex needs the image for its own inspection. On macOS, run ~/.codex/skills/screenshot/scripts/ensure_macos_permissions.sh before app/window capture when possible.
Use the exact helper that matches the OS: ~/.codex/skills/screenshot/scripts/take_screenshot.py for macOS/Linux and ~/.codex/skills/screenshot/scripts/take_screenshot.ps1 for Windows. Prefer helper flags such as --mode temp, --app, --window-name, --active-window, --window-id, or --region instead of improvising raw OS commands. Fall back to native commands only if the helper path is unavailable.
If the capture is for Codex inspection, view the saved temp image(s) in order and only manipulate them if needed. If permissions or prerequisites fail, report the missing piece clearly and stop instead of pretending a capture exists.

Non-Negotiable Acceptance Criteria

Prefer tool-specific capture first when it is clearly better for the target.
Do not guess app names, window ids, or captured content.
Each generated image path must be reported explicitly, especially when multiple windows or displays are captured.
If OS permissions or dependencies block capture, say that directly.

Output

The saved screenshot path or paths.
The capture mode used: full screen, app/window, active window, or region.
If relevant, the next inspection step, such as opening/viewing the image or retrying after permission setup.

---name: screenshotdescription: Capture desktop or system screenshots with the bundled OS helpers when the user explicitly asks for a screenshot or when tool-specific capture cannot reach the target. Supports full screen, app/window, active window, and region capture.---# Screenshot Capture## Metadata- Trigger when: the user wants an OS-level screenshot or a better-integrated tool cannot capture the target surface.- Do not use when: a tool-specific screenshot path already solves the task more directly and faithfully.## Skill PurposeUse the bundled helpers to capture desktop, app, window, or region screenshots predictably across platforms without re-deriving OS-specific commands every time.## Instructions1. Choose the save-location rule first: user path if provided, OS default if the user just wants a screenshot, or temp storage when Codex needs the image for its own inspection. On macOS, run `~/.codex/skills/screenshot/scripts/ensure_macos_permissions.sh` before app/window capture when possible.2. Use the exact helper that matches the OS: `~/.codex/skills/screenshot/scripts/take_screenshot.py` for macOS/Linux and `~/.codex/skills/screenshot/scripts/take_screenshot.ps1` for Windows. Prefer helper flags such as `--mode temp`, `--app`, `--window-name`, `--active-window`, `--window-id`, or `--region` instead of improvising raw OS commands. Fall back to native commands only if the helper path is unavailable.3. If the capture is for Codex inspection, view the saved temp image(s) in order and only manipulate them if needed. If permissions or prerequisites fail, report the missing piece clearly and stop instead of pretending a capture exists.## Non-Negotiable Acceptance Criteria- Prefer tool-specific capture first when it is clearly better for the target.- Do not guess app names, window ids, or captured content.- Each generated image path must be reported explicitly, especially when multiple windows or displays are captured.- If OS permissions or dependencies block capture, say that directly.## Output- The saved screenshot path or paths.- The capture mode used: full screen, app/window, active window, or region.- If relevant, the next inspection step, such as opening/viewing the image or retrying after permission setup.

Frequently asked questions