Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/using-screenshots
Use this to capture screen context.
Passed 12 of 18 test cases with the skill, and 7 of 18 without it.
and 5 more in the full report
6 fixed9 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am taking a screenshot from a terminal session where the current working directory is `~/projects/app`. Should the screenshot file path supplied to the Read tool be relative or absolute?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies using an absolute path starting with /tmp/. | Missed | Passed |
The instructions your model reads when the skill loads.
You CAN take screenshots by combining the Bash tool with platform-specific screenshot commands. Screenshots are saved as image files, then loaded into your context using the Read tool for visual analysis.
Use this skill when I ask you to:
| Platform | Command | Interactive Selection |
|---|---|---|
| macOS | screencapture | -i flag (area selection) |
| Linux | gnome-screenshot, scrot, or import | -a or -s flag |
Standard workflow:
uname -s/tmp/screenshot_$(date +%s).pnguname -s
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.