screenshot-walkthrough

Yes, you can capture screenshots of web apps and browser-based processes for debugging. The skill captures deterministic, labeled screenshots of each workflow step to document processes, bugs, or tutorials in a reproducible document.

When documenting a tutorial, screenshot files are named using a deterministic format. The specific naming convention used is step-{number}-{description}.png, ensuring artifacts are organized and easily referenced within the generated markdown walkthrough.

Yes, you can generate a markdown walkthrough structure alongside captured screenshots. The skill creates a ready-to-share markdown template that reviews actions and outcomes, saving artifacts and referencing the workflow in a single, reproducible document.

Yes, you need to specify a starting URL to automate screenshot capture for training materials. The quick start process requires clarifying the workflow and starting URL first, then running the walkthrough to capture and save step-by-step screenshots.

The best way to document browser-based workflows with reproducible artifacts is to use a filesystem-write workflow. This approach saves deterministic labeled screenshots and generates a markdown walkthrough template to review actions and outcomes in a single document.