New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Smart Screenshot Capture

by sillsdev in sillsdev/FieldWorks

Capture high-quality screenshots with MCP tools. An agent skill from sillsdev/FieldWorks.

MITAuto-check passedProductivity & Automation

Install Smart Screenshot Capture

skills CLI
$ npx skills add sillsdev/FieldWorks --skill smart-screenshot-capture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sillsdev/FieldWorks smart-screenshot-capture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sillsdev/FieldWorks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/smart-screenshot-capture .claude/skills/smart-screenshot-capture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
smart-screenshot-capture
GitHub stars
110
Token cost
~1.7k tokens
SKILL.md length
781 words
Files
1
Skills in repo
29
Repo updated
First seen
Licence
MIT

At a glance

Capture high-quality screenshots with MCP tools. An agent skill from sillsdev/FieldWorks.

  • Works in 5 steps: FieldWorks or another WinForms desktop… → A visible Windows app where WinForms MCP… → Browser content controlled by the… → …
  • The user asks to take a screenshot
  • SKILL.md covers Core Rules, Target Selection, Output Paths and Naming, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Smart Screenshot Capture is an agent skill from sillsdev/FieldWorks. Capture high-quality screenshots with MCP tools. Use when the user asks to take a screenshot, show the screen, capture a window, document UI evidence, collect before/after images, inspect browser output, or verify a desktop app visually with WinForms MCP, WinApp MCP, browser screenshots, image previews, annotations, or screenshot diffs.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Windows-first adaptation for VS Code agents with WinForms MCP, WinApp MCP, browser page tools, and image preview tools. Inspired by brennacodes' screenshotr…

It sits in Productivity & Automation, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: FieldWorks is a suite of software tools for language and cultural data, with support for complex scripts. The licence is MIT.

When your agent uses it

  • The user asks to take a screenshot
  • Show the screen
  • Capture a window
  • Document UI evidence

Example prompts

  • “/smart-screenshot-capture”

Requirements

  • Compatibility (from SKILL.md): Windows-first adaptation for VS Code agents with WinForms MCP, WinApp MCP, browser page tools, and image preview tools. Inspired by brennacodes' screenshotr skill, but adapted away from macOS screencapture/sips commands.

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. FieldWorks or another WinForms desktop app: capture by process id or window
  2. A visible Windows app where WinForms MCP cannot attach: use WinApp MCP and a
  3. Browser content controlled by the integrated browser: use screenshot_page
  4. A UI element that needs visual callouts: capture the app window, then use
  5. Whole desktop: use only when the user asks for desktop context or no focused

What it can do on your machine

Read from SKILL.md and the folder at commit bd0608d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Windows-first adaptation for VS Code agents with WinForms MCP, WinApp MCP, browser page tools, and image preview tools. Inspired by brennacodes' screenshotr skill, but adapted away from macOS screencapture/sips commands.

    From compatibility in the SKILL.md frontmatter.

Context cost

Smart Screenshot Capture loads about 1.7k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 781 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sillsdev/FieldWorks at commit bd0608d, republished under its MIT licence (© sillsdev). 781 words, ~1,692 tokens.

Download SKILL.mdSave it as .claude/skills/smart-screenshot-capture/SKILL.md (or your agent's skills folder).
name
smart-screenshot-capture
description
Capture high-quality screenshots with MCP tools. Use when the user asks to take a screenshot, show the screen, capture a window, document UI evidence, collect before/after images, inspect browser output, or verify a desktop app visually with WinForms MCP, WinApp MCP, browser screenshots, image previews, annotations, or screenshot diffs.
compatibility
Windows-first adaptation for VS Code agents with WinForms MCP, WinApp MCP, browser page tools, and image preview tools. Inspired by brennacodes' screenshotr skill, but adapted away from macOS screencapture/sips commands.
license
MIT
metadata.author
FieldWorks team
metadata.version
1.0
metadata.upstream
https://mcpmarket.com/tools/skills/smart-screenshot-capture

Smart Screenshot Capture

Use this skill to capture clear, reviewable screenshots without making the user manually crop, upload, or explain the screen. Prefer focused captures of the target app, window, browser page, or element over whole-desktop images.

Core Rules

  • Infer the target from the conversation when it is obvious, such as the active FieldWorks dialog, a named app, a browser page, or a before/after UI state.
  • Ask one short question only when the target is ambiguous enough that a wrong capture is likely.
  • Save screenshots to a deterministic path before reporting them.
  • Generate concise kebab-case filenames from the target and state.
  • Display or inspect the saved image after capture with view_image or the appropriate image preview tool.
  • Retake the screenshot when it is blank, the wrong app, overlapped by another window, too small to read, or missing the state the user asked to document.
  • Prefer non-mutating inspection and capture tools. Do not change project data just to make a screenshot easier.

Target Selection

Choose the narrowest useful target:

  1. FieldWorks or another WinForms desktop app: capture by process id or window handle when the MCP tool supports it.
  2. A visible Windows app where WinForms MCP cannot attach: use WinApp MCP and a specific appId or windowHandle.
  3. Browser content controlled by the integrated browser: use screenshot_page for the whole viewport or an element-specific capture.
  4. A UI element that needs visual callouts: capture the app window, then use annotation tools when available.
  5. Whole desktop: use only when the user asks for desktop context or no focused capture path exists.

When capturing a desktop app, inspect the UI tree or window list first if there is any risk of targeting the wrong window.

Output Paths

For this repository, FieldWorks evidence folders (transient vs committed vs parity bundles) are defined in ../fieldworks-winapp/navigation/screenshot-evidence.md — use those. Otherwise:

  • ad hoc screenshots: Output/ManualEvidence/screenshots/

Create the folder if needed. Do not put scratch screenshots in committed evidence folders unless the user asks for review-ready evidence.

Naming

Use sorted, descriptive names:

  • single capture: <target>-<state>.png
  • before/after: 01-before-<state>.png, 02-after-<state>.png
  • parity bundles: use the canonical names from ../fieldworks-winforms-to-avalonia-migration/references/parity-evidence.md §6 (visual.legacy.png, visual.avalonia.png, visual.diff.png, ...) under openspec/changes/<change-id>/evidence/parity/{scenarioId}/{bundleId}/; manual captures use a bundleId like manual-YYYYMMDD
  • sequence: step-01-<state>.png, step-02-<state>.png
  • app tour: <app>-<window-or-dialog>.png
  • temporary fallback: screenshot-YYYY-MM-DD-HHMMSS.png

Keep generated names short, lowercase, and kebab-case. Prefer 2-5 meaningful words over timestamps unless ordering or uniqueness requires a timestamp.

Tool Preference

Use the best available tool for the current target:

  • FieldWorks/WinForms on the visible desktop via WinForms MCP: winforms_take_screenshot (PrintWindow capture; no foregrounding needed).
  • WinApp visible desktop: mcp_winapp_take_screenshot_optimized when image size matters, otherwise mcp_winapp_take_screenshot.
  • UI callouts: mcp_winapp_annotate_screenshot.
  • Visual comparison: mcp_winapp_screenshot_diff.
  • Browser pages: screenshot_page.
  • Saved image review: view_image.

Prefer MCP screenshot tools over shell commands. Do not use the upstream macOS-specific screencapture, sips, or AppleScript workflow on Windows.

Show full SKILL.md (322 more words)Show less

Capture Workflow

  1. Identify the target and output path.
  2. Inspect the app/page/window when needed to confirm the target is visible.
  3. Capture to a deterministic filename.
  4. Inspect the saved image.
  5. Retake or annotate if the first capture does not communicate the requested state clearly.
  6. Report the saved path and any useful capture metadata, such as dimensions or diff percentage.

For before/after work, capture the before state first whenever it is available. If the before state is unavailable in the current worktree, say so and capture the fixed or current state with a clear filename.

Multi-Screenshot Workflows

Use multiple captures when one image cannot tell the story:

  • before/after: two captures with matching framing;
  • step sequence: one capture per user-visible step;
  • app tour: each relevant dialog, pane, or tab;
  • redraw/focus/modal timing: a short ordered sequence rather than a single screenshot;
  • comparison: capture both images, then run a screenshot diff when available.

For migration parity bundles, keep framing, DPI, zoom, and window size matched across WinForms and Avalonia captures whenever density, wrapping, or spacing is under review.

For a parity bundle, pair the visual captures with the matching semantic snapshot and workflow/accessibility evidence for the same scenarioId (folder layout and file names per ../fieldworks-winforms-to-avalonia-migration/references/parity-evidence.md §6); a screenshot pair alone is not a full parity claim.

For sequences, keep the same target, window size, and framing across captures unless the task is specifically about responsive or layout behavior.

Quality Checklist

Before considering the screenshot done, verify:

  • the image exists at the reported path;
  • the target app, page, or element is visible;
  • text needed for review is readable;
  • modal dialogs, focus state, selected tabs, and highlighted controls match the requested state;
  • no unrelated foreground window covers the target;
  • committed evidence contains only review-worthy images.

If a screenshot tool produces a cropped, blank, or wrong-window capture, switch drivers in this order: focused WinForms capture, WinApp optimized capture, browser capture, then whole-window or whole-desktop fallback.

© sillsdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/smart-screenshot-capture of sillsdev/FieldWorks.

Open the folder on GitHubat commit bd0608d

Compare with similar skills

Smart Screenshot Capture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Smart Screenshot Capture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Smart Screenshot Capture this skillsillsdev/FieldWorks110—~1.7kAutomated safety check: PassMIT
Piece Builderactivepieces/activepieces25k—~3.1kAutomated safety check: NotesCustom licence
Profile App Cpuactivepieces/activepieces25k—~1.9kAutomated safety check: PassCustom licence
Profile Worker Memoryactivepieces/activepieces25k—~1.7kAutomated safety check: PassCustom licence
Isolated Linux Agent Workspaceagent-sh/agent-workspace-linux186—~2.1kAutomated safety check: PassMIT
Xiaohongshu Content Researchjumodada/Drissionpage-MCP-Server487—~768Automated safety check: PassCustom licence

Similar skills

  • Piece Builder

    activepieces/activepieces

    Build and edit Activepieces pieces (integrations) — creating new pieces, adding actions or triggers, or fixing bugs in existing ones.

    25k GitHub stars~3.1k tokensUpdated today
    Productivity & AutomationAuto-check: notes

  • Profile App Cpu

    activepieces/activepieces

    Find what is burning CPU in a live app container without restarting it: separate the JS thread from GC and libuv, open the V8 inspector in place with SIGUSR1, take a CPU profile over CDP, and…

    25k GitHub stars~1.9k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Profile Worker Memory

    activepieces/activepieces

    Diagnose a worker that is growing memory or being OOM-killed: separate a JS-heap leak from native growth, take a V8 heap snapshot of a live worker in place (never uploading it), and walk the…

    25k GitHub stars~1.7k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Isolated Linux Agent Workspace

    agent-sh/agent-workspace-linux

    Drives a hidden, agent-owned Linux desktop and browser over MCP for GUI testing and web automation without touching the user's real desktop.

    186 GitHub stars~2.1k tokensUpdated 5 days ago
    Productivity & AutomationAuto-check passed

  • Xiaohongshu Content Research

    jumodada/Drissionpage-MCP-Server

    A skill your agent uses for authorized, read-only research on public Xiaohongshu content or the local Xiaohongshu-like playground fixture.

    487 GitHub stars~768 tokensUpdated 25 days ago
    Productivity & AutomationAuto-check passed

  • Build Audit Logs

    activepieces/activepieces

    Build or review audit trails in TypeScript/JavaScript apps using evlog (pipelines, typed actions, denials, retention, compliance-style reviews).

    25k GitHub starsUsed in 1 repo~5.9k tokens
    Productivity & AutomationAuto-check passed

More from sillsdev/FieldWorks

All 29 skills in this repo

  • Atlassian Readonly Skills

    sillsdev/FieldWorks

    Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.

    110 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Atlassian Skills

    sillsdev/FieldWorks

    Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.

    110 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Fieldworks Winapp

    sillsdev/FieldWorks

    Control and document the FieldWorks desktop application with WinForms MCP or WinApp MCP.

    110 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Convert Slice

    sillsdev/FieldWorks

    Drive the conversion of one legacy slice type to the Avalonia detail view through analysis, developer alignment, integration-test planning, route/exemplar mapping, design, and scaffold/implement.

    110 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Dependabot Consolidation

    sillsdev/FieldWorks

    Combine several open Dependabot pull requests into a single branch and PR: enumerate the open Dependabot PRs, cherry-pick them onto fresh main, rewrite commit messages to satisfy…

    110 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Fieldworks Semantic Render Parity

    sillsdev/FieldWorks

    Capture or review FieldWorks parity evidence: semantic snapshots, render/visual baselines, layout parity, failure artifacts, XML view definitions, and the Avalonia presentation IR.

    110 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Smart Screenshot Capture

What does Smart Screenshot Capture do?

Capture high-quality screenshots with MCP tools. An agent skill from sillsdev/FieldWorks. Smart Screenshot Capture is an agent skill from sillsdev/FieldWorks. Capture high-quality screenshots with MCP tools.

When should I use Smart Screenshot Capture?

Smart Screenshot Capture fits situations like: the user asks to take a screenshot; show the screen; capture a window; document UI evidence.

How do I install Smart Screenshot Capture in Claude Code?

Run `npx skills add sillsdev/FieldWorks --skill smart-screenshot-capture -a claude-code`. Or copy the skill folder (.claude/skills/smart-screenshot-capture in sillsdev/FieldWorks) into .claude/skills/smart-screenshot-capture in your project. Claude Code loads it when a task matches its description.

How do I install Smart Screenshot Capture in Codex?

Run `npx skills add sillsdev/FieldWorks --skill smart-screenshot-capture -a codex`. Or copy the skill folder (.claude/skills/smart-screenshot-capture in sillsdev/FieldWorks) into .agents/skills/smart-screenshot-capture in your project. Codex loads it when a task matches its description.

Can I use Smart Screenshot Capture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sillsdev/FieldWorks --skill smart-screenshot-capture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/smart-screenshot-capture, .gemini/skills/smart-screenshot-capture, .github/skills/smart-screenshot-capture and .opencode/skills/smart-screenshot-capture in your project.

What does Smart Screenshot Capture need to run?

SKILL.md names no scripts, command-line tools or credentials: Smart Screenshot Capture is instructions for the agent only. Compatibility (from SKILL.md): Windows-first adaptation for VS Code agents with WinForms MCP, WinApp MCP, browser page tools, and image preview tools. Inspired by brennacodes' screenshotr skill, but adapted away from macOS screencapture/sips commands. .

Does Smart Screenshot Capture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Smart Screenshot Capture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Smart Screenshot Capture use?

Smart Screenshot Capture is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Smart Screenshot Capture use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Smart Screenshot Capture?

Skills that share tags, products or a category with Smart Screenshot Capture: Piece Builder (activepieces/activepieces, 25k stars), Profile App Cpu (activepieces/activepieces, 25k stars), Profile Worker Memory (activepieces/activepieces, 25k stars) and Isolated Linux Agent Workspace (agent-sh/agent-workspace-linux, 186 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Smart Screenshot Capture?

sillsdev (a GitHub organization) maintains it in sillsdev/FieldWorks, which has 110 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 8, 2026.

Source: sillsdev/FieldWorks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.