screenshots
Skill0 starsChanged 5 days agoMITView on GitHub
Share screenshots from the project's screenshots folder with Claude for analysis and discussion
18 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- yicheng47/runnertheir own version, first seen Nov 8, 2026
- solo-ist/prosetheir own version, first seen Nov 8, 2026
- artsy/eigentheir own version, first seen Nov 2, 2026
- bloknayrb/tandemtheir own version, first seen Oct 29, 2026
- petecurran/sortedtheir own version, first seen Oct 17, 2026
Used with
Projects with it also use release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 4 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- tabler/tabler★ 42ksame name
- artsy/eigen★ 3.8ksame name
- d4rken-org/permission-pilot★ 694same name
- pablopunk/SwiftShift★ 664same name
- yicheng47/runner★ 519same name
- bloknayrb/tandem★ 28same name
- xfstudio/skills★ 9same name
- solo-ist/prose★ 8same name
- keinstn/drover★ 5same name
- moasq/ios-dev-agent★ 4same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- content-writerSkill
- full-stack-mvp-builderSkill
- lucidreactor-uiSkill
- social-cardsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 13 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Search for the screenshots folder in the current project using these common locations (in order of priority):
- Distinctive: line 37
Use the Glob tool to check which folder exists:
- Very specific: line 42
If no screenshots folder is found, inform the user and suggest creating one at ./screenshots/.
- Very specific: line 49
Use Glob to find all image files: screenshots/*.{png,jpg,jpeg,gif,webp}
- Very specific: line 50
Use Bash ls -t to sort by modification time
- Distinctive: line 63
Use Glob with the provided pattern
- Distinctive: line 67
Check if file exists in screenshots folder
- Distinctive: line 68
Read that specific file
- Distinctive: line 73
Use the Read tool to view the image (Read tool supports images)
- Distinctive: line 79
After displaying the screenshots:
- Distinctive: line 81
Ask the user what they'd like to discuss or analyze
- Distinctive: line 92
Image Support: Use the Read tool to view images directly (Claude Code supports image viewing)
- Distinctive: line 94
Performance: If more than 10 screenshots match, warn the user and ask if they want to proceed
- Distinctive: line 95
Relative Paths: Always use paths relative to the current working directory
- Distinctive: line 96
Error Handling: If no screenshots found, provide helpful guidance
- Distinctive: line 150
After completing the task, you can optionally mention:
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Screenshots Skill
You are helping the user share and analyze screenshots from their project.
Task
The user has invoked the screenshots skill to view and discuss screenshots from the current project.
Arguments Handling
The skill accepts optional arguments in this format:
/screenshots- Show latest screenshot only (default)/screenshots N- Show latest N screenshots (e.g.,/screenshots 3)/screenshots all- Show all screenshots in the folder/screenshots pattern "glob"- Show screenshots matching a pattern (e.g.,/screenshots pattern "login*.png")/screenshots specific "filename"- Show a specific screenshot
Parse the arguments if provided, otherwise default to showing the latest screenshot.
Steps to Execute
1. Locate Screenshots Folder
Search for the screenshots folder in the current project using these common locations (in order of priority):
./screenshots/./docs/screenshots/./.screenshots/./assets/screenshots/./public/screenshots/
Use the Glob tool to check which folder exists:
pattern: "**/screenshots"If no screenshots folder is found, inform the user and suggest creating one at ./screenshots/.
2. Find Relevant Screenshots
Based on the arguments:
Default (no args) - Latest screenshot:
- Use Glob to find all image files:
screenshots/*.{png,jpg,jpeg,gif,webp} - Use Bash
ls -tto sort by modification time - Select the most recent one
Number (e.g., "3") - Latest N screenshots:
- Find all image files
- Sort by modification time (newest first)
- Select the first N screenshots
"all" - All screenshots:
- Find all image files in screenshots folder
- Include all of them (warn if more than 10)
"pattern" - Pattern matching:
- Use Glob with the provided pattern
- Example:
screenshots/login*.png
"specific" - Specific file:
- Check if file exists in screenshots folder
- Read that specific file
3. Read and Display Screenshots
For each screenshot found:
- Use the Read tool to view the image (Read tool supports images)
- Include the filename and timestamp in your response
- Provide context about what you observe in each screenshot
4. Analyze and Discuss
After displaying the screenshots:
- Describe what you see in each screenshot
- Ask the user what they'd like to discuss or analyze
- Offer to help with:
- UI/UX feedback
- Bug identification
- Design suggestions
- Documentation
- Comparison between screenshots
- Creating tickets or tasks based on what's shown
Important Notes
- Image Support: Use the Read tool to view images directly (Claude Code supports image viewing)
- File Formats: Support common formats: PNG, JPG, JPEG, GIF, WebP
- Performance: If more than 10 screenshots match, warn the user and ask if they want to proceed
- Relative Paths: Always use paths relative to the current working directory
- Error Handling: If no screenshots found, provide helpful guidance
Example Workflow
- User runs
/screenshots 3 - You locate
./screenshots/folder - You find 15 total screenshots
- You use Bash to get the 3 most recent:
ls -t screenshots/*.{png,jpg} | head -3 - You read each of the 3 screenshots with the Read tool
- You display them with context: "Here are the 3 most recent screenshots from your project..."
- You analyze what you see and ask how you can help
Response Format
Structure your response like this:
I found [N] screenshot(s) in `./screenshots/`.
Showing [description of which ones]:
---
**Screenshot 1**: `filename.png` (Modified: YYYY-MM-DD HH:MM)
[Display the image using Read tool]
[Your analysis of what you see]
---
**Screenshot 2**: `filename2.png` (Modified: YYYY-MM-DD HH:MM)
[Display the image using Read tool]
[Your analysis of what you see]
---
How can I help you with these screenshots? I can:
- Provide UI/UX feedback
- Identify potential issues
- Suggest improvements
- Help document features shown
- Compare different versionsEdge Cases
- No screenshots folder: "I don't see a screenshots folder. Would you like me to help you create one at
./screenshots/?" - Empty folder: "The screenshots folder exists but is empty. Add some screenshots and try again!"
- Too many matches: "Found 47 screenshots. That's a lot! Did you want to narrow it down? Try
/screenshots 5or/screenshots pattern 'feature-name*.png'" - Invalid pattern: "I couldn't find any screenshots matching that pattern. Here are all available screenshots: [list]"
Tips for Users
After completing the task, you can optionally mention:
- "Tip: Organize screenshots with descriptive names like
feature-login-success.pngfor easier filtering" - "Tip: Use
/screenshots patternto focus on specific features or dates" - "Tip: Keep screenshots in
./screenshots/for consistency across your projects"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

