readme-screenshots
Skill1 starsChanged 56 days agoNo licenceView on GitHub
Use when a project's README (or docs page) needs real screenshots of the running app — "README에 스크린샷 넣어줘", "화면 캡처해서 문서에 붙여줘", "라이트/다크 모드 캡처", "스크린샷 갱신해줘". Boots the app, captures the agreed screens at fixed viewports and themes with Chrome DevTools MCP, writes them to docs/ under stable filenames, and inserts or updates the README screenshot section. Also re-captures existing shots in place when the UI changed instead of appending a second set.
In this repository11 other files it gives its agents.
- aws-helperSkill
- blog-postSkill
- dev-startSkill
- mentor-mode-teachingSkill
- merge-safeSkill
- particle-stageSkill
- postman-collection-from-codeSkill
- qa-checkSkill
- save-learning-logSkill
- session-to-skillSkill
- travel-itinerary-plannerSkill
The file
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.