Workflow Progress Screenshots
Show the user real screenshots of the work as it progresses, without being asked. Capture the start, the key moment and the result of every visual change, send them as files with captions as soon as each is ready, and look at every image before sending it. Use on any task with a visible result (UI, pages, games, 3D, charts, motion), when the user says "show me", "screenshots", "keep giving me screenshots" or "where are the screenshots?", and before any report that claims a visual change works.
Install
npx skills add MengTo/Skills --skill workflow-progress-screenshotsgit clone --depth 1 https://github.com/MengTo/Skills.git /tmp/Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Skills/agent-skills/workflow/workflow-progress-screenshots ~/.claude/skills/workflow-progress-screenshotsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Workflow: progress screenshots The user judges visual work by looking at it, and asks for screenshots in almost every thread: - "keep giving me screenshots" - "send screenshots every pass" - "can you give me screenshots of those?" - "I still don't see the screenshots. Where are they?" Describing a change is not showing it. **A screenshot mentioned but not sent doesn't count.** ## Rules 1. **Send, don't describe.** Use the host's file-sending tool (`SendUserFile`, or an inline image in the report) so the picture is in front of the user. A path in a sentence is not enough. 2. **Unasked, and as you go.** Send a picture after each meaningful pass, so the user can redirect early: - the first working version; - each big fix; - each round of a scoring loop. Don't hold them all for the final report. Don't flood them either: one small batch per pass, not every save. 3. **Start, key moment, result.** For any change with a before and after, capture all three with the same framing: the state before, the interaction (hovering, aiming, mid-animation, the panel opening), and the outcome. For fixes, show the bug, then the fix. 4. **Real renders only.** Capture the actual page, game or app, not a mockup or an idea of it. Set up the state with a review fixture, a URL flag or a debug hook, rather than describing it. 5. **Look at every image before sending.** Things that mean recapture: - stray toasts or hover pins; - half-loaded art or missing fonts;
Details
- Skill name
workflow-progress-screenshots- Repository
- MengTo/Skills
- Path
agent-skills/workflow/workflow-progress-screenshots/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
FAQ
What does the Workflow Progress Screenshots skill do?
Show the user real screenshots of the work as it progresses, without being asked. Capture the start, the key moment and the result of every visual change, send them as files with captions as soon as each is ready, and look at every image before sending it. Use on any task with a visible result (UI, pages, games, 3D, charts, motion), when the user says "show me", "screenshots", "keep giving me screenshots" or "where are the screenshots?", and before any report that claims a visual change works.
How do I install the Workflow Progress Screenshots skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add MengTo/Skills --skill workflow-progress-screenshots. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Workflow Progress Screenshots popular?
It lives in MengTo/Skills, which has 7,717 GitHub stars and 885 forks.
Related skills
3d Cloth Material
7.7kMengTo/Skills
Build convincing woven cloth in Three.js, with a thread-level weave normal map, sheen and anisotropic highlights, folds that never stretch the texture, hems with thickness, stitches, seams, frayed edges, fold occlusion, dye and wear variation, and light passing through thin fabric. Use for linen, silk, wool, canvas, curtains, banners, cloaks, tablecloths, tapestries or any 3D drape that currently looks like a plastic sheet, a stretched texture, or a flat coloured plane.
3d Falling Leaves
7.7kMengTo/Skills
Build recognizable falling leaves in world space using instanced geometry, independent tumble, coupled sideways drift, shared wind, scene occlusion, and camera-aware recycling. Use for 3D autumn leaves or drifting foliage in Three.js and similar scenes; use falling-leaves for a 2D canvas overlay.
3d Four Seasons
7.7kMengTo/Skills
Add coordinated spring, summer, fall, and winter states to a 3D scene, blending foliage, sunlight, sky, ground materials, snow, and particles without rebuilding the world. Use for seasonal controls, architectural walkthroughs, and outdoor scenes with four-season transitions.
Workflow Score to Target
7.7kMengTo/Skills
Score work out of 10 against a clear rubric, then improve it round by round until every item reaches the target score the user named (for example "get it to 8 out of 10", "bring everything under 6 up to 6+"). Covers anchored rubrics, measurable criteria, independent or blind judging, before/after scorecards, and honest reporting of anything still short. Use whenever the user asks to score, rate, grade or judge something out of 10, names a target score, or asks "what would make this a 9?".
Nx Workspace
7.2ktech-leads-club/agent-skills
Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT use for running tasks (use nx-run-tasks) or code generation with generators (use nx-generate).
Workflow Ship Change
7.7kMengTo/Skills
Ship every change the way the user requires, with the guardrails. Take screenshots of the start, the key moment and the result; give the change its own changelog version with pictures; verify with tests; commit only your own files; merge with the latest main and push as a fast-forward; publish that exact main live; confirm each step; and report measured sizes, asking before any upload over 50 MB. Use at the end of every change (feature, fix, tweak, art, balance, polish) and whenever the user says "ship it", "commit", "push", "merge", "publish", "deploy", "go live" or "update the changelog". Pr
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.