How do I install the Proofshot skill?

Run npx skillmds@latest add tomevault-io/proofshot in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Proofshot safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Proofshot?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Proofshot free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Proofshot?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Proofshot by tomevault-io — Agent Skill

Name: Proofshot
Author: tomevault-io

File contents

ProofShot — Visual Verification Workflow

When to use

Use ProofShot after:

Building a new UI feature or page
Modifying existing UI components
Fixing a visual bug
Any change that affects what the user sees

The workflow (always follow these 3 steps)

Step 1: Start the session

proofshot start --description "what you are about to verify"

This starts the dev server, opens a headless browser, and begins recording. The description appears in the proof report for the human.

Step 2: Drive the browser and test

Use proofshot exec to navigate, interact, and verify:

proofshot exec snapshot -i                                    # See interactive elements
proofshot exec open http://localhost:PORT/page                # Navigate to a page
proofshot exec click @e3                                      # Click a button
proofshot exec fill @e2 "test@example.com"                    # Fill a form field
proofshot exec screenshot step-NAME.png                       # Capture key moments

Take screenshots at important moments — these become the visual proof. Verify what you expect to see by reading the snapshot output.

Step 3: Stop and bundle the proof

proofshot stop

This stops recording, collects console + server errors, and generates a SUMMARY.md with video, screenshots, and error report.

Step 4 (optional): Post proof to the PR

proofshot pr              # Auto-detect PR from current branch
proofshot pr 42           # Target a specific PR number

This uploads screenshots and video to GitHub and posts a formatted comment on the PR. By default it uses the official GitHub contents API on a proofshot-artifacts branch. Use --upload-provider github-web-attachments if you specifically want GitHub attachment URLs.

Tips

Always include a meaningful --description so the human knows what was tested
Take screenshots before AND after key actions (e.g., before form submit, after redirect)
If you find errors during verification, fix them and re-run the workflow
Use proofshot pr after stopping to attach proof directly to the pull request

Source: AmElmo/proofshot — distributed by TomeVault.

---name: proofshotdescription: Visual verification of UI features. Use after building or modifying any Use when this capability is needed.---# ProofShot — Visual Verification Workflow## When to useUse ProofShot after:- Building a new UI feature or page- Modifying existing UI components- Fixing a visual bug- Any change that affects what the user sees## The workflow (always follow these 3 steps)### Step 1: Start the session```bashproofshot start --description "what you are about to verify"```This starts the dev server, opens a headless browser, and begins recording.The description appears in the proof report for the human.### Step 2: Drive the browser and testUse proofshot exec to navigate, interact, and verify:```bashproofshot exec snapshot -i # See interactive elementsproofshot exec open http://localhost:PORT/page # Navigate to a pageproofshot exec click @e3 # Click a buttonproofshot exec fill @e2 "test@example.com" # Fill a form fieldproofshot exec screenshot step-NAME.png # Capture key moments```Take screenshots at important moments — these become the visual proof.Verify what you expect to see by reading the snapshot output.### Step 3: Stop and bundle the proof```bashproofshot stop```This stops recording, collects console + server errors, and generatesa SUMMARY.md with video, screenshots, and error report.### Step 4 (optional): Post proof to the PR```bashproofshot pr # Auto-detect PR from current branchproofshot pr 42 # Target a specific PR number```This uploads screenshots and video to GitHub and posts a formatted comment on the PR. By default it uses the official GitHub contents API on a `proofshot-artifacts` branch. Use `--upload-provider github-web-attachments` if you specifically want GitHub attachment URLs.## Tips- Always include a meaningful --description so the human knows what was tested- Take screenshots before AND after key actions (e.g., before form submit, after redirect)- If you find errors during verification, fix them and re-run the workflow- Use `proofshot pr` after stopping to attach proof directly to the pull request---> Source: [AmElmo/proofshot](https://github.com/AmElmo/proofshot) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Proofshot