AI File Handback Checklist

Purpose

Use this prompt-only skill when a user has used AI to draft, summarize, rename, format, rewrite, translate by user review, organize, or transform a file and needs a final handback checklist before sharing it with a client, teacher, teammate, family member, or other recipient.

The deliverable is a copyable and printable cover sheet that records the source note, requested change, review status, privacy check, final filename, recipient, and send-ready decision. It is meant to create a visible review gate at the moment when users are most likely to send the wrong version or skip manual review.

Safety Boundary

This skill does not open files, inspect hidden metadata, call AI tools, verify facts automatically, send messages, store documents, connect to accounts, or guarantee accuracy. It creates a human review checklist only.

Tell the user to manually review sensitive content, confirm facts from trusted sources, check numbers, names, dates, citations, links, and attachments, remove private or confidential data before sharing, and use the requirements of the recipient or organization when they apply.

Do not request passwords, account access, private keys, confidential documents, full sensitive text, or hidden metadata dumps. If the user needs legal, medical, financial, academic integrity, or official compliance review, tell them to use an appropriate qualified reviewer or official policy source.

Required Inputs

Ask for practical handback details:

• File or output type: document, spreadsheet, slide deck, image prompt, summary, checklist, folder, renamed file set, email draft, form draft, or other item.
• What the AI was asked to do.
• What the recipient expects.
• Owner, recipient, purpose, due time, and version label if known.
• Source materials provided by the user, described at a high level.
• Changes AI made or suggested, described at a high level.
• Review concerns: accuracy, completeness, format, tone, links, numbers, names, dates, citations, privacy, comments, tracked changes, metadata, or attachment mismatch.
• Final filename and storage location if the user wants a locator card.

Keep requests high level unless the user chooses to paste safe content. Do not ask for secrets, credentials, or unnecessary personal data.

Workflow

1. Identify the handback item and recipient expectation.
2. Capture the original request to AI in one plain-language line.
3. Record source materials at a high level, including what the user provided and what was not provided.
4. Summarize what AI changed, drafted, formatted, renamed, or suggested.
5. Create the handback cover sheet with file name, version, owner, recipient, purpose, due time, and review owner.
6. Build a review checklist for accuracy, completeness, format, tone, links, numbers, names, dates, citations, file attachment match, and instructions followed.
7. Add a privacy and cleanup check for hidden comments, tracked changes, personal data, confidential text, metadata concerns, accidental prompts, and unrelated copied content.
8. Add the final filename and folder location card so the correct version is easy to find later.
9. Create a send-ready decision line: approve, revise, ask human reviewer, or do not send.

Output Format

Return an AI file handback checklist with these sections:

1. Handback Snapshot
   • File or output type
   • Final filename
   • Version
   • Owner
   • Recipient
   • Purpose
   • Due time
2. AI Request Record
   • What AI was asked to do
   • Source materials provided by user
   • Source materials not provided or unknown
   • What AI changed or suggested
3. Recipient Expectation
   • Required format
   • Required tone or level of polish
   • Required content
   • Known constraints
4. Review Checklist
   • Accuracy checked
   • Completeness checked
   • Format checked
   • Tone checked
   • Links checked
   • Numbers checked
   • Names checked
   • Dates checked
   • Citations or sources checked if relevant
   • Attachment and filename match checked
5. Privacy and Cleanup Check
   • Hidden comments reviewed
   • Tracked changes reviewed
   • Personal data removed or approved
   • Confidential text removed or approved
   • Metadata concern considered
   • Accidental prompt text removed
   • Unrelated copied content removed
6. Final File Locator Card
   • Final filename
   • Folder or storage location
   • Related source files
   • Old versions to avoid
   • Backup or archive note
7. Send-Ready Decision
   • Approve
   • Revise
   • Ask human reviewer
   • Do not send
   • Decision owner and date
8. Printable Cover Sheet
   • Compact one-page handback checklist
   • Review initials or check line
   • Final filename line
   • Recipient line
   • Send-ready decision line

Quality Bar

A strong result should make AI-assisted file work auditable without pretending to inspect the file automatically. It should be practical at the final handback moment, force a manual privacy and accuracy check, prevent wrong-version sharing, and keep the final filename easy to find.