/screenshot-capture
Capture desktop screenshots with OS-aware save-location rules, app/window/region support, and bundled helpers.
$ npx -y skills add CoWork-OS/CoWork-OS --skill screenshot-capture --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/screenshot-capture
Context preview
The summary Claude sees to decide when to auto-load this skill.
Capture desktop screenshots with OS-aware save-location rules, app/window/region support, and bundled helpers.
SKILL.md
screenshot-capture.SKILL.mdname: screenshot-capture
description: "Capture desktop screenshots with OS-aware save-location rules, app/window/region support, and bundled helpers."
Screenshot Capture
Purpose
Capture screenshots of the desktop, an app, a window, or a region with the right save location.
Routing
- Use when: Use when the user explicitly asks for a screenshot, for whole-system desktop captures, or when a tool-specific capture cannot get what you need.
- Do not use when: Do not use when a better-integrated screenshot tool is available for the requested surface, or when the request is unrelated to visual capture.
- Outputs: Saved screenshot path(s) plus a brief capture note when needed.
- Success criteria: Returns the saved screenshot path(s), uses the requested save location, and follows the platform-specific capture workflow without inventing unavailable tools.
Trigger Examples
Positive
- Take a screenshot of this app window.
- Capture the full desktop and save it to a file.
- Take a screenshot of Codex and put it in temp.
- Use Screenshot Capture for this desktop capture.
Negative
- Summarize this text without taking a screenshot.
- Write a plan for a capture workflow.
- This is a browser-only automation task with a better tool available.
- This request does not involve any visual capture.
Runtime Prompt
- Current runtime prompt length: defined directly in `../screenshot-capture.json`.
- Detailed save-location rules and command patterns live in `references/full-guidance.md`.
Read more
name: screenshot-capture description: "Capture desktop screenshots with OS-aware save-location rules, app/window/region support, and bundled helpers."
Screenshot Capture
Purpose
Capture screenshots of the desktop, an app, a window, or a region with the right save location.
Routing
- Use when: Use when the user explicitly asks for a screenshot, for whole-system desktop captures, or when a tool-specific capture cannot get what you need.
- Do not use when: Do not use when a better-integrated screenshot tool is available for the requested surface, or when the request is unrelated to visual capture.
- Outputs: Saved screenshot path(s) plus a brief capture note when needed.
- Success criteria: Returns the saved screenshot path(s), uses the requested save location, and follows the platform-specific capture workflow without inventing unavailable tools.
Trigger Examples
Positive
- Take a screenshot of this app window.
- Capture the full desktop and save it to a file.
- Take a screenshot of Codex and put it in temp.
- Use Screenshot Capture for this desktop capture.
Negative
- Summarize this text without taking a screenshot.
- Write a plan for a capture workflow.
- This is a browser-only automation task with a better tool available.
- This request does not involve any visual capture.
Runtime Prompt
- Current runtime prompt length: defined directly in `../screenshot-capture.json`.
- Detailed save-location rules and command patterns live in `references/full-guidance.md`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill