When asked to update, accept, or refresh screenshot baselines from CI — or when the Screenshot Tests GitHub Action has failed with screenshot differences — follow this procedure to download the CI-generated screenshots and commit them as the new baselines.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionupdate-screenshotsExecute the skills CLI command in your project's root directory to begin installation:
Fetches update-screenshots from microsoft/vscode and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate update-screenshots. Access via /update-screenshots in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
183.5K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
183.5K
stars
When asked to update, accept, or refresh screenshot baselines from CI — or when the Screenshot Tests GitHub Action has failed with screenshot differences — follow this procedure to download the CI-generated screenshots and commit them as the new baselines.
Screenshots captured locally may differ from CI due to platform differences (fonts, rendering, DPI). The CI (Linux, ubuntu-latest) is the source of truth. This skill downloads the CI-produced screenshots and commits them as baselines.
gh CLI must be authenticated (gh auth status).Screenshot Tests GitHub Action must have run and produced a screenshot-diff artifact.If the user provides a specific run ID or PR number, use that. Otherwise, find the latest run:
# For a specific PR:
gh run list --workflow screenshot-test.yml --branch <branch> --limit 5 --json databaseId,status,conclusion,headBranch
# For the current branch:
gh run list --workflow screenshot-test.yml --branch $(git branch --show-current) --limit 5 --json databaseId,status,conclusion
Pick the most recent run that has a screenshot-diff artifact (runs where screenshots matched won't have one).
gh run download <run-id> --name screenshot-diff --dir .tmp/screenshot-diff
The artifact is uploaded from two paths (test/componentFixtures/.screenshots/current/ and test/componentFixtures/.screenshots/report/), but GitHub Actions strips the common prefix. So the downloaded structure is:
current/ — the CI-captured screenshots (e.g. current/baseUI/Buttons/Dark.png)report/report.json — structured diff reportreport/report.md — human-readable diff reportShow the user what changed by reading the markdown report:
cat .tmp/screenshot-diff/report/report.md
# Remove old baselines and replace with CI screenshots
rm -rf test/componentFixtures/.screenshots/baseline/
cp -r .tmp/screenshot-diff/current/ test/componentFixtures/.screenshots/baseline/
rm -rf .tmp/screenshot-diff
git add test/componentFixtures/.screenshots/baseline/
git commit -m "update screenshot baselines from CI"
Screenshot baselines are stored in Git LFS. The git lfs pre-push hook is not active in this repo (husky overwrites it), so LFS objects are NOT automatically uploaded on git push. You must push them manually before pushing the branch, otherwise the push will fail with GH008: Your push referenced unknown Git LFS objects.
git lfs push --all origin <branch-name>
git push
Confirm the baselines are updated by listing the files:
git diff --stat HEAD~1
screenshot-diff artifact exists, the screenshots already match the baselines — no update needed.--filter option on the CLI can be used to selectively accept only some fixtures if needed.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
update-screenshots is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
update-screenshots fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
update-screenshots reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend update-screenshots for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: update-screenshots is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added update-screenshots from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in update-screenshots — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added update-screenshots from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: update-screenshots is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for update-screenshots matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 43