Agent skill · civitai
feature-walkthrough
Capture a finished feature as live screenshots and assemble them into a shareable walkthrough page for review. Use when someone needs to see a feature working but a live demo isn't possible — a reviewer in another timezone, a stakeholder who wants to look before a rollout, a PR whose value doesn't survive a diff. Produces a published artifact, not a slide deck.
What it needs
About 7k tokens when loaded.
What this skill does
Feature walkthrough Drive a feature through every state that matters, screenshot each one from the real app, and assemble them into one page a reviewer can read start to finish. The output is a published Artifact — a private URL the author can share. This is a demo substitute, not a test report. If the question is "does it work", run the tests. If the question is "is this the right product", this is the shape that answers it, because the reviewer sees the screens rather than a description of them. ⚠️ Dev database only — never production Every step below writes: seeding a scenario needs contributor rows, invites, lapsed flags and half-finished states that no real account should ever be put into, and the restore at the end deletes rows. Doing that against production would corrupt real users' data. Before the first write: 1. Confirm the app you are driving points at a dev database, and that the query tool you seed with points at the same one. Check the connection your .env actually resolves to — do not trust a log line that says which database it is. 2. Re-check after any long gap. The postgres-query skill's target can be re-pointed between sessions, and a "dev" fingerprint taken an hour ago is not evidence about the query you are about to run. 3. Never pass a writable flag to a production target. If you cannot tell which target you have, stop and ask. Also assume the screenshots are going to be shared. Anything on screen — usernames, avatars, collection names, item thumbnails — leaves with the report. Prefer dev accounts whose content is unremarkable, and read the captures before publishing rather than after. Setup Copy .env.example to .env in this directory and adjust if your ports differ. It is gitignored; every developer supplies their own. Nothing in it is secret. Screenshots default to a temp directory, outside the repo. If you point SHOTSDIR somewhere else, keep it outside the checkout — the captures show dev accounts and their content, and this repo is public. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills civitai/feature-walkthrough