Cette page est affichée en anglais. Une traduction française est en cours.
分析Oct 6, 2026·6 min de lecture

Equipment Warranty Renewal Watch Table Prompt

An original prompt that turns a raw serial-number and warranty-date list into a renewal-watch table, leaving unknown fields blank for human review.

Prêt pour agents

Installation agent prête

Cet actif peut être installé après choix du runtime, vérification du plan et exécution de la commande adaptée.

Native · 96/100Policy : autoriser
Surface agent
Tout agent MCP/CLI
Type
Prompt
Installation
Single
Confiance
Confiance : Established
Point d'entrée
PROMPT.md
Commande d'installation directe
npx -y tokrepo@latest install 274cbb67-28ff-4e20-bc08-d502fd868d52 --target codex

À exécuter après confirmation du plan en dry-run.

Start here

This is a reusable prompt for ordinary AI chat tools that accept pasted text. No terminal or API setup is needed.

What to paste: the prompt text below, plus your raw warranty list in the MY INPUT slot. Include a reference date (for example reference date 2025-01-10) if you want urgency tiers filled in.

Where to paste: into the message box of a general AI chat. Paste the prompt first, then your raw list in the same message.

How to check the output:

  • The first line must state the reference date used, or say NONE supplied.
  • The table must have exactly these columns: Item, Serial number, Warranty end, Vendor/location, Urgency tier, Flags.
  • Every serial number and date should come from your text or be blank — nothing invented.
  • "Needs human verification" should list only flagged rows.
  • The Counts block should match the table.

Introduction

Maintaining a warranty watch list by hand is slow and error-prone. This prompt converts a messy list of serial numbers and expiry dates into a structured Markdown table, flags gaps and ambiguities, and assigns an urgency tier against a reference date you supply.

Prerequisites and permissions

  • A general AI chat that accepts pasted text.
  • Your raw list, and a reference date if you want tiers.
  • No login to any vendor system, no file uploads required. Do not paste confidential serials unless your tool and policy allow it. The prompt cannot contact vendors, file claims, schedule renewals, or update systems.

Limitations

  • Only works on the text you paste; it will not search the web or your files.
  • Dates are normalised only when unambiguous; month-only or relative dates keep the original wording and get a Flag.
  • Urgency tiers stay blank when no reference date is supplied.
  • Output is a draft for human verification, not legal, insurance, or purchasing advice.
  • Source reviewed; runtime not tested.

FAQ

Do I need a reference date? No. Without one, urgency tiers stay blank and the tool says so at the top. With one, tiers follow the four bands (Expired, 90 days, 91–180 days, later than 180 days).

What if my list is garbled? Fields that cannot be assigned confidently stay blank and are explained in Flags. Duplicate serials and possible duplicates are kept as separate rows and flagged.

Attribution

Original TokRepo prompt, CC BY 4.0. Reference: ChatGPT release notes.

Complete reusable prompt

You are helping me maintain an equipment warranty renewal watch list. I will paste raw text containing equipment serial numbers and warranty end dates. Work only from the text I provide. Do not invent serial numbers, product names, vendors, purchase dates, owners, dates, or coverage terms.

MY INPUT (paste below): [Paste the raw list. It may be inconsistent. Entries might look like: "SN 44-A19B, warranty ends 2025-03-14", "pump model XR2 serial 88120 - covered until March 2025", or "item 7B: expiry unknown".]

YOUR TASK

  1. Extract every distinct piece of equipment into one row.
  2. For each row, capture only what is stated: item label or description, serial number, warranty end date, and any stated vendor or location. If a field is not stated, leave it blank rather than guessing.
  3. Normalise dates to YYYY-MM-DD only when the stated date is unambiguous. If a date is partial or unclear (for example "March 2025" or "next quarter"), keep the original wording in the date field and add a note in the Flags column.
  4. Assign an urgency tier based only on the warranty end date relative to the reference date I give you. If I do not give a reference date, leave the urgency tier blank and say so at the top.
    • Expired: end date is before the reference date
    • Due within 90 days
    • Due within 91-180 days
    • Later than 180 days
  5. Flag any row where a serial number or warranty end date is missing, duplicate, or ambiguous.

OUTPUT FORMAT Start with one line: "Reference date used: [date], or NONE supplied." Then a Markdown table with these columns: | Item | Serial number | Warranty end | Vendor/location | Urgency tier | Flags | After the table, add a short section titled "Needs human verification" listing only the rows whose Flags column is non-empty, with a one-line reason for each. Finally, add a "Counts" block: total rows, rows missing a serial number, rows missing an end date, rows with an ambiguous date, and rows with duplicate serial numbers.

UNCERTAINTY AND MISSING INPUT HANDLING

  • Never fabricate a value to fill an empty cell.
  • If two entries appear to describe the same item but the serial numbers differ, keep them as separate rows and flag a possible duplicate.
  • If the same serial number appears twice, keep both rows and flag the duplicate.
  • If the raw text is too garbled to assign a field confidently, leave the field blank and explain in Flags.
  • If there is no date information at all for an item, mark the Warranty end cell as blank and flag it.

REVIEW CHECKS (state pass or fail for each, tied to my pasted input)

  • Check 1: Every row's Serial number and Warranty end cells are either taken verbatim from my input or blank. Pass only if no value was invented.
  • Check 2: Every urgent-tier value matches the reference date rule, with blank if no reference date was supplied.
  • Check 3: Every non-empty Flags cell corresponds to a real gap, duplicate, or ambiguity in my input, not a guess.
  • Check 4: The Counts block matches the actual table rows.

BOUNDARIES

  • You are preparing a draft tracking table only. You are not contacting vendors, filing warranty claims, scheduling renewals, or updating any system. A person must verify flagged rows before any of that happens.
  • Do not give legal, insurance, or purchasing advice.
  • Do not add rows for equipment I did not mention.

FICTIONAL EXAMPLE (for shape only) Input: "SN 44-A19B, warranty ends 2025-03-14; pump model XR2 serial 88120 - covered until March 2025; item 7B: expiry unknown" with reference date 2025-01-10. Illustrative output shape: Reference date used: 2025-01-10. | Item | Serial number | Warranty end | Vendor/location | Urgency tier | Flags | | 44-A19B | 44-A19B | 2025-03-14 | | Due within 90 days | | | pump model XR2 | 88120 | March 2025 | | Due within 90 days | Ambiguous date: month only | | item 7B | | | | | Missing serial number and end date | Needs human verification: pump model XR2 (ambiguous month-only date), item 7B (missing serial and date). Counts: total 3, missing serial 1, missing end date 1, ambiguous date 1, duplicate serials 0. Example pass/fail checks: Check 1 pass if no date or serial was added that was not in the input; Check 2 pass if tiers follow the reference date; Check 3 pass if flags describe only real gaps; Check 4 pass if counts match the table.

References and reuse

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires