cuozg/screenshot
skills/screenshot/SKILL.md
Use this skill when the user explicitly asks for a desktop or system screenshot — full screen, a specific app or window, or a pixel region. Also use when tool-specific capture capabilities are unavailable and an OS-level capture is needed. Supports macOS (screencapture), Linux (scrot/gnome-screenshot), and Windows (PowerShell). Do not use for in-app screenshots or Unity scene captures — those have dedicated tools.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills screenshotInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 1:05 PM124.3s13 files scanned
SKILL.md
- name:
- screenshot
- description:
- >
Screenshot Capture
Save-Location Rules
- User specifies a path → save there.
- User asks without a path → save to the OS default screenshot location.
- Codex needs a screenshot for its own inspection → save to the temp directory.
Always report the saved file path in the response.
Tool Priority
- Prefer tool-specific capabilities when available (Figma MCP for Figma, Playwright/agent-browser for web/Electron apps).
- Use this skill when explicitly asked, for whole-system desktop captures, or when no better-integrated tool exists.
Platform Helpers
macOS — take_screenshot.py + ensure_macos_permissions.sh
Run permission preflight before any window/app capture, then capture with the Python helper.
See → references/macos-guide.md
Quick start:
bash <path-to-skill>/scripts/ensure_macos_permissions.sh && \
python3 <path-to-skill>/scripts/take_screenshot.py --app "<App>" --mode temp
Linux — take_screenshot.py
Requires scrot, gnome-screenshot, or ImageMagick import (auto-selected).
See → references/linux-guide.md
Quick start:
python3 <path-to-skill>/scripts/take_screenshot.py --mode temp
Windows — take_screenshot.ps1
PowerShell helper covers all modes (default, temp, explicit path, region, active window, handle).
See → references/windows-guide.md
Quick start:
powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1 -Mode temp
Output Behavior
Script prints one path per capture. Multiple matching windows/displays → multiple paths, suffixed -w<windowId> or -d<display>. View each path sequentially.
Error Handling Summary
- macOS permissions: run
ensure_macos_permissions.shfirst; if sandbox errors persist, rerun with escalated permissions. - macOS no match: run
--list-windows --app "AppName", retry with--window-id, ensure app is visible. - Linux tool missing: install
scrot/gnome-screenshot/imagemagick; check withcommand -v scrot. - Sandbox save failure: rerun with escalated permissions.
References
| File | Content |
|------|---------|
| references/macos-guide.md | Permission preflight, Python helper patterns, workflow examples, multi-display, direct OS commands |
| references/linux-guide.md | Prerequisites, selection logic, Python helper patterns, multi-display, direct OS commands |
| references/windows-guide.md | PowerShell helper patterns, multi-display behavior |
Related Skills
cuozg/unity-image-gen
tools
VerifiedTrustedCommunity
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
4SKILL.mdUpdated May 29, 2026
cuozg/unity-technical
tools
VerifiedTrustedCommunity
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
4SKILL.mdUpdated May 26, 2026
cuozg/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
4SKILL.mdUpdated May 21, 2026
cuozg/goal-todo
development
VerifiedTrustedCommunity
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.
4SKILL.mdUpdated May 21, 2026