- Home
- Skills
- Technical Documentation
- Realshot: user manuals from your real app
More screenshots
Works with the AI Agents you already use
Realshot: user manuals from your real app
Turn your real app into a user manual, demo or deck. Real screens, fake data, nothing left behind.
$19
Realshot: user manuals from your real app
Example session with this skill installed
Make an admin user manual with real screenshots of our helpdesk app (Laravel + Postgres). Use demo data, not our real tickets, and don't touch the main repo.
- Read your context and instructions
- Compiled the realshot
Admin manual: 7 steps captured from the real app, environment restored.
1. Flow mapped from latest main
Pulled main, read routes/web.php and the role guards. No step was written from memory.
| # | Screen | Route | Annotation |
|---|---|---|---|
| 1 | Sign in | /login | Email and password fields |
| 2 | Overview | /dashboard | Open, overdue and SLA cards |
| 3 | Project dashboard | /i/acme | Open dashboard link |
| 4 | Ticket queue | /i/acme/tickets | Filters, SLA bar, assignee |
| 5 | Ticket detail | /i/acme/tickets/{id} | State change, reply box |
| 6 | Knowledge base | /i/acme/faqs | Add FAQ button |
| 7 | Sign out | menu | User menu |
2. Isolation and demo data
- Throwaway Postgres container on a spare port; the real database was never connected.
- Seeded "Acme Support": 24 fictional tickets across every state, 3 agents. Names checked against a deny-list.
- Mail driver set to
log, so no capture step can send a real email.
3. Capture
- Production build on a loopback port, clock frozen to the publish date, reduced motion on.
- Playwright logged in as the admin test account, desktop 1440x900 at
deviceScaleFactor: 2. - Red boxes and numbered badges placed from
boundingBox(), so they line up with the real elements. - Steps live in
steps.mjs; the next release is a one-command rerun.
4. Deliverable
helpdesk-admin-manual.pdf: cover, contents, 7 annotated steps, FAQ. Every page was rendered to an image and read.
5. QA and restore
- No localhost URLs, old product names or real people on screen
- Dates match the publish date
- Container removed, env reverted, server stopped
Next steps
- Have someone who runs the helpdesk check the step list against how the team works.
- Want a per-role version for agents too? Same script, second test account.
Connects securely to your tools. The creator never sees your data.
About this skill
Every release breaks your user manual. Ask your agent for "an admin manual with screenshots" and Realshot drives your actual app: it seeds safe demo data, logs in as each role, captures every step at 2x, annotates it, and builds the PDF, demo or deck. Then it puts your database and settings back exactly as they were.
Why it's different
- Real screens, never mockups: every step comes from the latest code and a real capture.
- Safe by default: throwaway database, fictional data checked against real company names, mail switched off so no capture sends a real email.
- One command next release: steps live in a file, so the manual reruns when the UI changes.
- Built from real projects: 18 pitfalls that actually happened, each with its guard.
What it does
- Automated capture uses Playwright to log in across multiple user roles and capture @2x retina screenshots of real application flows.
- Environment isolation operates in detached worktrees and disposable databases to ensure your production environment remains untouched.
- Smart annotation measures DOM element rectangles to place perfectly aligned red boxes, badges, and callouts automatically.
- Asset generation produces annotated PDF manuals, interactive click-through demos with hotspots, pitch decks, and marketing posters.
- Data seeding populates your app with consistent, fictional data that handles pagination and state across multi-step wizards.
How it works
- Mapping identifies application routes, role guards, and navigation steps from the latest main branch code.
- Isolation spins up a disposable loopback server and seeds a temporary database with safe, non-PII demo data.
- Execution runs Playwright scripts to capture every step of the user journey, freezing the system clock for visual consistency.
- Assembly builds the final deliverable (PDF, PPTX, or interactive demo) and audits for localhost URLs or stray brand names.
Frameworks & tools
Works with any web app you can build and run locally. Uses Playwright for capture, Pillow for annotation, Chromium for PDF rendering and pptxgenjs for slides; seeds data with your framework seeders or SQL (Supabase, Postgres, MySQL and others).
Use cases
- Generating per-role user manuals that update automatically with every new release.
- Creating interactive click-through demos for sales teams without using production data.
- Building investor pitch decks that show real, functional UI instead of static mockups.
- Exporting retina-quality mobile screenshots for App Store and marketing poster assets.
Known limitations
Requires a functional local build and seedable database schema. It cannot design new UI elements or safely handle live production user data.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean today
- Passed all security checks, Safe to install
Requires