AI Screenshot to SOP

Overview

AI Screenshot to SOP helps a user convert screenshots of a repeated digital task into a clear standard operating procedure. It uses only screenshots, notes, and descriptions the user provides in the conversation. It does not access the filesystem, browse folders, inspect apps, log into accounts, or infer hidden data.

The goal is to make a repeated task teachable: identify the sequence, name each action, add quality checks, clarify roles and inputs, and produce a handoff-ready SOP.

When to Use

Use this skill when the user says they have screenshots of a repeated task and wants to turn them into:

• A standard operating procedure
• A repeatable checklist
• Training documentation for a teammate
• A task handoff guide
• A documented workflow from UI screenshots

Trigger phrases: "turn these screenshots into an SOP", "document this process", "make a workflow from screenshots", "write steps from this UI", "create a handoff guide".

Inputs to Request

Ask the user to provide:

• Screenshots in the order they believe the task happens, if available
• A short description of the task goal
• The system, tool, or website name if it is safe to share
• Who performs the task and who receives the result
• Required inputs, such as links, records, account names, files, or form fields
• What a correct final result looks like
• Known exceptions, approval points, or risky steps
• Any private details that should be redacted or generalized

If screenshots are missing, ask for a text walkthrough. If the order is uncertain, label the sequence as provisional.

Workflow

Step 1 - Confirm Scope and Evidence

State that the SOP will be based only on the screenshots and descriptions supplied by the user. Do not claim to have opened files, inspected a folder, accessed an app, or verified a live UI.

Capture:

• Process name
• Purpose
• Audience
• Role performing the work
• Trigger for starting the task
• Expected output
• Source material provided

Step 2 - Inventory the Screenshots

Create a screenshot inventory:

• Screenshot label or number
• Visible screen or page name
• Main UI elements visible
• Apparent action suggested by the screenshot
• Data shown that should be redacted in the final SOP
• Unclear or ambiguous elements

Do not invent screen names or button labels. If text is not readable, mark it as unreadable.

Step 3 - Infer the Sequence

Arrange the screenshots into a likely task sequence using only visible evidence and user notes.

For each step, include:

• Step number
• Action name
• Screenshot reference
• What the user appears to do
• Required input
• Expected result
• Confidence: high, medium, or low

If a transition between screenshots is unclear, write "Unconfirmed transition" and ask the user to verify it.

Step 4 - Name the Actions

Turn UI observations into clear action verbs, such as:

• Open record
• Review details
• Select option
• Enter value
• Upload document
• Submit request
• Check confirmation
• Notify owner

Avoid vague labels such as "do this screen". Keep actions specific enough for a new teammate.

Step 5 - Add Checks and Decision Points

Add practical checks to prevent mistakes:

• Required fields completed
• Correct record or customer selected
• Dates, amounts, names, or IDs match source material
• Attachments or links open correctly
• Confirmation message or status appears
• Approval is received before submission
• Sensitive data is redacted before sharing

Add decision points when the user described exceptions or when the screenshots show branching options. Do not invent business rules.

Step 6 - Build the SOP

Produce a complete SOP with these sections:

1. Purpose
2. Scope
3. Roles and responsibilities
4. Inputs needed
5. Tools or systems named by the user
6. Step-by-step procedure
7. Quality checks
8. Exception handling
9. Handoff notes
10. Open questions and uncertain UI steps

Step 7 - Handoff Notes

Add a compact handoff section that tells the next person:

• When to start
• What to have ready
• What to double-check
• When to stop and ask
• What to send or record when finished
• Who receives the output

Step 8 - Export for Use

Offer the SOP in a format the user can copy into a doc, wiki, checklist, onboarding guide, or ticket template. Keep screenshot references in the procedure so the user can attach images later.

Output Template

# SOP: [Process Name]

**Scope note:** Built only from user-provided screenshots and descriptions. Uncertain UI steps are flagged for verification.

## 1. Purpose
...

## 2. Roles and Responsibilities
- **Performer:** ...
- **Reviewer or approver:** ...
- **Recipient:** ...

## 3. Inputs Needed
- ...

## 4. Step-by-Step Procedure
| Step | Screenshot | Action | Required input | Expected result | Check | Confidence |
|---|---|---|---|---|---|---|
| 1 | Screenshot 1 | ... | ... | ... | ... | High / Medium / Low |

## 5. Quality Checks
- ...

## 6. Exceptions and Stop Points
- ...

## 7. Handoff Notes
- ...

## 8. Open Questions
- ...

Avoid markdown tables if the delivery channel does not render them well; use bullets instead.

Safety and Compliance

• Uses only screenshots, notes, and descriptions supplied by the user
• Does not access the filesystem, local folders, accounts, apps, browser history, or external websites
• Does not invent hidden UI steps, button labels, permissions, policies, or business rules
• Flags unreadable, uncertain, missing, or ambiguous steps instead of filling them in as fact
• Recommends redaction of private or sensitive information visible in screenshots
• Requires user review before the SOP is used for training, operations, compliance, or customer work
• This is a prompt-only skill with zero code execution, zero network calls, and zero credential requirements

Example Prompts

1. "I took 5 screenshots of our customer refund process. Can you turn these into an SOP?"
2. "Here are screenshots of how I update the weekly report. I need a handoff guide for my teammate."
3. "I have UI screenshots from our booking tool. Turn them into a step-by-step procedure with quality checks."

Acceptance Criteria

1. The output states that it is based only on user-provided screenshots and descriptions.
2. Screenshots are inventoried or referenced in the resulting sequence.
3. The SOP includes roles, inputs, step-by-step actions, checks, and handoff notes.
4. Uncertain UI steps are explicitly flagged rather than invented.
5. Sensitive information visible in screenshots is marked for redaction or generalization.
6. The final SOP is copy-ready and usable for training or handoff after user review.