← IMEILookupCONTENT HISTORY
WHAT CHANGED
Update to IMEILookup
Snapshot Nov 5, 2026 · 06:11 UTC · version 1.0.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save IMEILookup and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user provides a CSV/PDF of identifiers to check, or asks for printable labels, barcode PDFs, or other file-based outputs.",
"included_files": [],
"name": "files-and-labels",
"skill_md_contents": "---\nname: files-and-labels\ndescription: Use when the user provides a CSV/PDF of identifiers to check, or asks for printable labels, barcode PDFs, or other file-based outputs.\n---\n\n# Files and printable labels\n\nIMEILookup receives identifier strings, not files directly. File reading and PDF/barcode generation are ChatGPT-assisted tasks using compatible ChatGPT file tools.\n\n## Reading identifiers from files\n\n- With compatible file-reading tools, extract identifiers from the intended CSV column or a readable barcode PDF.\n- Preserve leading zeros; avoid spreadsheet number conversion (numbers can lose precision).\n- Reconcile extracted values with the source. If a PDF has conflicting printed vs barcode values, or a scan is unreadable, ask for clarification before ordering.\n- Never invent a missing digit or assume a numeric cell can be restored after precision loss.\n- Apply the same cleanup and service-compatibility rules as `run-device-checks`.\n- If file tools are unavailable, explain the limitation and ask for identifiers as text. Do not claim the plugin parsed a file.\n\n## Printable labels and barcodes\n\n- Use exact device identifiers and actual returned result fields. Do not infer missing model, model number, warranty, MDM, or other values.\n- For a final-stage MDM label, use only devices that reached the authorized MDM stage and their returned MDM results (including failures if requested).\n- Use the user's label size/printer requirements when supplied; otherwise state the chosen size and provide a preview.\n- Include human-readable identifiers, keep text within the label, and verify the encoded barcode value against its source.\n- Render and inspect the PDF before delivery when rendering tools are available. If verification or rendering isn't possible, say so.\n- Creating a printable PDF does not send it to a printer.\n"
}SHA-256 of public snapshot: 3ad335fba121db2db326bec85a747432b9cdc5f7f62bd5fbb490f4b0743650ea