app-demo-ui-screenshot

Generate README screenshots of the Agento desktop app using a synthetic Claude Code session corpus.

31|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/shaharia-lab/agento --skill app-demo-ui-screenshot-shaharia-lab
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: app-demo-ui-screenshot
Source: https://github.com/shaharia-lab/agento/tree/main/.claude/skills/app-demo-ui-screenshot
Command: npx skills add https://github.com/shaharia-lab/agento --skill app-demo-ui-screenshot-shaharia-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes scripts (resource) components.

What problem does it solve? Marketing and README screenshots of a desktop app go stale after every UI change, and retaking them against real user data risks leaking private sessions, tokens, and file paths. This Skill regenerates the full docs/screenshots set from a fully synthetic, anonymised dataset without ever touching the real ~/.agento or ~/.claude directories. ## Core Features & Use Cases - Synthetic corpus generation: gen_corpus.py deterministically writes ~300 Claude Code session JSONL files across 10 invented projects, including sub-agent transcripts, token usage, and a scripted hero session for detail shots. - Isolated app launch: launch.sh runs the Tauri dev build against a fake HOME (~/.agento-demo) under XWayland so the window can be sized to the README frame, while seed_api.py and seed_db.py populate agents, integrations, scheduled tasks, chats, and job history. - Deterministic screenshot capture: shoot.sh drives the real webview through the ui-verify helper, waiting for settle predicates before each capture so React re-renders never race the snapshot. - Use Case: After a UI redesign makes docs/screenshots stale, run the five-step pipeline (corpus, launch, seed, shoot, clean) to regenerate every light-theme PNG in docs/screenshots/light with consistent, anonymised data. ## Quick Start Ask the agent to regenerate the README screenshots with demo data, and it will build the synthetic corpus, launch the isolated app, seed it, and shoot the full screenshot set into docs/screenshots/light.

Frequently Asked Questions about app-demo-ui-screenshot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I regenerate the Agento README screenshots?ā–¼

Run the five-step pipeline: gen_corpus.py to build the synthetic session corpus, make_dirs.sh for the project directories, launch.sh to start the isolated app, seed_api.py and seed_db.py to populate data, then shoot.sh docs/screenshots/light to capture every view.

Does the screenshot skill touch my real Claude Code data?ā–¼

No. The app launches with a fake HOME (~/.agento-demo), so the data dir and scanner only see the synthetic corpus. Nothing reads or writes the real ~/.agento or ~/.claude, and make_dirs.sh --clean removes the temporary ~/Projects stubs afterwards.

Why is the Insights screenshot empty or all zeros?ā–¼

The session_insights table is filled by a background worker that sweeps at boot and every five minutes. After relaunching the app, wait about a minute and verify row counts with sqlite3 before shooting, otherwise the page shows zeros that look like a rendering bug.

Why does a synthetic project decode to the wrong path?ā–¼

decode_project_path resolves greedily against existing directories, so a project name sharing a prefix with a real ~/Projects entry decodes incorrectly. Choose names that do not collide and let make_dirs.sh create the empty stubs it needs.

Can the app window be resized on Wayland for screenshots?ā–¼

No. Window sizing requires X11, so launch.sh exports GDK_BACKEND=x11 to run under XWayland. On Wayland nothing outside the app can resize it, and window-state may restore it maximised, which is why the workflow uses wmctrl and xdotool.