Intake cleanup

Turns a messy customer asset list (an email, a spreadsheet paste, a photo of a manifest) into a clean, serial-level intake table with data-bearing and battery flags, a list of mismatches to resolve, and questions to send back, then saves the cleanup rules so every list gets the same treatment. Use when someone in recycling, ITAD or receiving retypes customer equipment lists before a pickup.

Run it as a prompt

Paste this into any AI agent, or fetch it: curl -s https://uplift.page/api/v1/prompts/intake-cleanup/raw

prompt.md

# Intake cleanup

Every customer sends their equipment list differently. Turn this one into a clean intake record, show me what doesn't add up, and give me the questions to send back.

## Before you start

Ask me to paste the list (an email, rows copied from a spreadsheet, or a photo of a manifest), then stop and wait. If I say **"use the sample"**, use the made-up list at the end of this prompt. Remind me in one line to replace customer names and site addresses with placeholders before pasting a real list.

## Steps

1. **Read every line.** Split lines that hold several items ("2x Dell 7420 laptops"). Keep the customer's original wording in a column so nothing gets lost.
2. **Build the intake table** with these columns: line, quantity, category (laptop, desktop, server, network, storage, phone or tablet, monitor, battery, other), make, model, serial, asset tag, data-bearing (yes, no or unknown), battery (yes, no or unknown), and notes.
   - Data-bearing means it may hold drives, SSDs or flash storage. If you're not sure, say unknown, not no.
   - Never invent a serial, model or count. A blank stays blank.
3. **List the mismatches,** in this order:
   - a stated total that doesn't match the lines;
   - duplicate serials or asset tags;
   - items with no serial;
   - vague items ("misc cables", "box of drives");
   - anything that could be hazardous (swollen batteries, CRTs, UPS units).
4. **Write the questions back to the customer:** short, numbered and polite, one per mismatch. Mark it DRAFT. Never send it.
5. **Give me a CSV version** of the table in a code block, ready to import.
6. **Save the rules.** End with a short "My intake rules" block listing the decisions you made (for example "count each drive in a box separately", "unknown storage means data-bearing") so I can paste it next time and get the same result.

## Rules

- Nothing invented. Unknown is a valid answer.
- When in doubt, mark it data-bearing and flag it for a person.
- Drafts only. Nothing goes to the customer from here.

## Sample (made up, for practice)

"Hi, attached is what we have for pickup Thursday, about 40 items total: 12 Dell Latitude 7420 (asset tags LT-1001 thru LT-1012), 2x HP Z2 towers S/N 2UA1234XYZ and 2UA1235XYZ, Cisco 2960 switch, misc cables (2 boxes), box of old hard drives maybe 15?, 6 iPads (one cracked), APC UPS 1500 (battery swollen I think), Dell R640 server SN 7HJK2L3 and another R640 SN 7HJK2L3, 3 monitors."

Install it as a skill

Agents that support the Agent Skills standard load it automatically when it applies.

download

curl -fsSL https://uplift.page/p/intake-cleanup/SKILL.md --create-dirs -o .agents/skills/intake-cleanup/SKILL.md

or from any MCP client

MCP server: https://uplift.page/mcp
Tool: pull_skill  {"slug": "intake-cleanup"}

The full skill

Every customer sends their equipment list differently. Turn this one into a clean intake record, show me what doesn't add up, and give me the questions to send back.

Before you start

Ask me to paste the list (an email, rows copied from a spreadsheet, or a photo of a manifest), then stop and wait. If I say "use the sample", use the made-up list at the end of this prompt. Remind me in one line to replace customer names and site addresses with placeholders before pasting a real list.

Steps

Read every line. Split lines that hold several items ("2x Dell 7420 laptops"). Keep the customer's original wording in a column so nothing gets lost.
Build the intake table with these columns: line, quantity, category (laptop, desktop, server, network, storage, phone or tablet, monitor, battery, other), make, model, serial, asset tag, data-bearing (yes, no or unknown), battery (yes, no or unknown), and notes.
- Data-bearing means it may hold drives, SSDs or flash storage. If you're not sure, say unknown, not no.
- Never invent a serial, model or count. A blank stays blank.
List the mismatches, in this order:
- a stated total that doesn't match the lines;
- duplicate serials or asset tags;
- items with no serial;
- vague items ("misc cables", "box of drives");
- anything that could be hazardous (swollen batteries, CRTs, UPS units).
Write the questions back to the customer: short, numbered and polite, one per mismatch. Mark it DRAFT. Never send it.
Give me a CSV version of the table in a code block, ready to import.
Save the rules. End with a short "My intake rules" block listing the decisions you made (for example "count each drive in a box separately", "unknown storage means data-bearing") so I can paste it next time and get the same result.

Rules

Nothing invented. Unknown is a valid answer.
When in doubt, mark it data-bearing and flag it for a person.
Drafts only. Nothing goes to the customer from here.

Sample (made up, for practice)

"Hi, attached is what we have for pickup Thursday, about 40 items total: 12 Dell Latitude 7420 (asset tags LT-1001 thru LT-1012), 2x HP Z2 towers S/N 2UA1234XYZ and 2UA1235XYZ, Cisco 2960 switch, misc cables (2 boxes), box of old hard drives maybe 15?, 6 iPads (one cracked), APC UPS 1500 (battery swollen I think), Dell R640 server SN 7HJK2L3 and another R640 SN 7HJK2L3, 3 monitors."

Served from the uplift.page library and refreshed within 5 minutes of every update.