Skins. Codes. Clear answers.

Guides/Market & inventory

Market & inventory

Create a dated item record for comparison

Record the exact item name, game, reference and attributes you observed. Download a text card to compare a listing or explain a mismatch without treating notes as verification.

3 min read
Published Revised

THE QUICK ANSWER

This tool formats your observations into a dated record. It does not inspect an item, decode an inspect link or verify ownership, attributes, price or availability.

01

Enter what you actually observed

Choose CS2, Rust or TF2, copy the item’s exact visible name and enter the date you observed it. Add an asset or listing reference if you have one; leave that field empty if you do not.

Use the attributes field for labelled observations such as exterior, wear, seed, quality, sticker layout or style. Copy values from the actual record you checked. A field left unknown is more useful than a guessed property.

STRIKEPOT / EXPLAINED

Four fields make the observation traceable

  1. Item identity

    Game and exact visible name.

  2. Reference

    The optional asset or listing reference you supplied.

  3. Observed date

    When the source was checked.

  4. Attribute notes

    Only the properties actually seen.

Original record structure; it does not assert that any entered property is verified.

Original explanation · not an account screenshot

Try it with your own details.

This tool keeps your input in this page. It does not upload it, add it to the address or save it. Downloads happen only when you choose them. Reset the form when you finish.

02

Keep the reference and the item name together

A full item name can identify a product variant without identifying a particular copy. An asset or listing reference can help you keep two similar items separate, but the form does not resolve that reference or check that it still points to the same available item.

Use the observation date to show when the notes were made. A changed listing or later item modification can explain a difference between old notes and a current offer; the record is not a live inventory snapshot.

What each field contributes
Game and exact nameThe item description you mean to compare.
Optional referenceYour supplied asset or listing identifier, with no lookup.
Observed dateWhen you read the source details.
Observed attributesLabelled notes copied from the source, with unknowns left explicit.

03

Compare the actual item at the next stage

Build the item record, then check each line against the listing or offer you are reviewing. For a CS2 craft, a matching base name alone does not establish the same finish and attachments; for TF2, keep quality and modifiers explicit.

The generated text is labelled as entered by the reader and states that it does not verify ownership, authenticity, current price or availability. Retain the original inspect view or source record when a disputed detail matters.

STRIKEPOT / EXPLAINED

Carry the notes to a real comparison

  1. Observe

    Read the actual item or listing.

  2. Record

    Build and download the dated text card.

  3. Compare again

    Match the current offer against the same source details.

The card preserves your notes; the comparison still depends on inspecting the real offered item.

Original explanation · not an account screenshot

04

Download the text card when you need a copy

Choose item-record.txt to save the game, exact name, reference, observed date and attribute notes. It is plain text, not a screenshot, certificate, price appraisal or automatically compared inventory report.

The tool does not save or upload your input. Use Reset this form when finished. Before sharing the file, remove unrelated account identifiers or private references that the intended recipient does not need; nothing is sent to support from this page.

BEFORE YOU CONTINUE

Quick checklist

  • Copy the exact visible name and select the correct game.
  • Record the date of the actual observation.
  • Label attributes and leave unknown values unknown.
  • Compare the generated notes with the real listing or offer.
  • Review the text file before sharing.

Official sources

Tool behaviour was checked against StrikePot’s form and browser implementation on 26 October 2026 (America/Toronto). The external references below explain the relevant formats and source records.

Implementation inspected: item-card form, gtItemCard and its text-download handler. The form validates required name/date and formats supplied strings; it does not parse or verify attributes or references. Steam’s current indexed offer-history documentation supplies context; no live item, inspect link, ownership state or listing was retrieved. No sample record is presented as a tested or personally owned item.

KEEP READING

A useful next read.

All guides

Skins & trading · 2 min read

Inspect before buying

Open the actual listing’s inspect view, compare the complete variant and check wear, pattern and stickers before reviewing the final offer.

Read guide

Steam & trades · 2 min read

Review a trade offer

Check the recipient, every item and the final Steam confirmation before accepting. If an offer changes or is replaced, review it from the start.

Read guide

Support · 2 min read

Share evidence, keep secrets

Show the error, affected item and useful reference. Hide passwords, codes, payment details and unrelated personal information before sharing.

Read guide