Import Mapping Review

    2

    Review pasted source columns against supplied import requirements, with traceable mappings, sample exceptions and unresolved decisions before migration.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Import Mapping Review

    Example session with this skill installed

    Review this authorized fictional inventory mapping in English. Do not import or write a file. S1 headers in order: C1 Item code, C2 Depot, C3 Units, C4 Received on, C5 State, C6 Comment. A1 is an explicit approved mapping decision: C1 -> sku, C2 -> warehouse, C3 -> quantity, C4 -> received_date, C5 -> state; C6 is intentionally excluded. T1 target requirements: sku is a required exact text string, preserving leading zeros; warehouse is required and accepts W1 or W2; quantity is a required integer of zero or more; received_date is required ISO YYYY-MM-DD with no timezone conversion; state is required and accepts available or held. T2: each inventory row's unique key is the exact pair (sku, warehouse); do not aggregate across warehouses. T3: create-only into an empty non-production test table; missing required fields are rejected and source rows must be preserved; no production import is authorized. Samples: R1 = [0012, W1, 7, 2026-10-01, available, synthetic note]; R2 = [0012, W2, 4, 2026-10-02, held, synthetic note]; R3 = [0040, W1, 0, 2026-10-03, available, synthetic note]. There are exactly three pasted sample rows, not the full source file. This exercise uses no real customer data.

    • Read your context and instructions
    • Compiled the import mapping review

    Self-initiated fictional demonstration generated and reviewed by the authoring AI in a local self-test. Not an independent benchmark, customer project, executed import or measured business result.

    Scope And Status

    Review complete for the supplied three-row fictional sample. The explicit mapping A1 accounts for five target fields and six source columns. No exception was observed against T1-T2 in R1-R3. This is not full-file validation or approval to import. No file, account or record has been changed, and no import has been executed. The empty non-production destination is a supplied condition in T3, not an independently inspected fact.

    Mapping Draft

    • Target field: sku

      Source: C1 Item code

      Decision: Explicitly supplied

      Supplied rule: Required exact text; preserve leading zeros

      Sample observation: 0012, 0012 and 0040 remain strings; no rewriting to 12 or 40

      Evidence: A1, T1, R1-R3

    • Target field: warehouse

      Source: C2 Depot

      Decision: Explicitly supplied

      Supplied rule: Required; W1 or W2

      Sample observation: All three values belong to the supplied set

      Evidence: A1, T1, R1-R3

    • Target field: quantity

      Source: C3 Units

      Decision: Explicitly supplied

      Supplied rule: Required integer of zero or more

      Sample observation: 7, 4 and 0 meet the supplied sample rule; zero is not a missing value

      Evidence: A1, T1, R1-R3

    • Target field: received_date

      Source: C4 Received on

      Decision: Explicitly supplied

      Supplied rule: Required ISO YYYY-MM-DD; no timezone conversion

      Sample observation: 2026-10-01, 2026-10-02 and 2026-10-03 are valid calendar dates in the required form

      Evidence: A1, T1, R1-R3

    • Target field: state

      Source: C5 State

      Decision: Explicitly supplied

      Supplied rule: Required; available or held

      Sample observation: available, held and available belong to the supplied set

      Evidence: A1, T1, R1-R3

    Unmapped source column: C6 Comment is intentionally excluded by A1. Its exclusion does not remove a row. No additional target field is invented for it.

    Exceptions And Decisions

    No unresolved mapping decision is apparent in the supplied material. No sample value conversion is proposed or performed.

    The declared exact key is (sku, warehouse), not sku alone (T2). R1 has (0012, W1), R2 has (0012, W2), and R3 has (0040, W1). These are three different sample keys. R1 and R2 are not duplicate inventory records merely because the SKU repeats; do not combine their quantities or remove either row. There is no evidence about keys elsewhere in the unseen file or destination.

    T3 specifies create-only and rejects missing required values. All five required target fields are present in each of the three supplied rows. Production use is not authorized.

    Human Validation Plan

    1. The authorized operator should confirm the intended target version and A1 mapping, then independently confirm that the selected test table is non-production and empty, as T3 assumes. Do not proceed in a production or nonempty table.
    2. Preserve the source and use the platform's native validator on a separate three-row test sample. Configure create-only, the five mappings, C6 exclusion and the exact composite key. Reject missing required values rather than filling them.
    3. After that human-operated test, reconcile exactly three source rows against three destination rows and match each pair by (sku, warehouse). Compare each of the five mapped values, including the leading zeros, R3's zero quantity, the dates and enum strings. Confirm both 0012 warehouse rows survive separately. This plan is not a claim that the test has occurred.
    4. Stop if row counts differ, a required value changes, keys collapse, leading zeros disappear, or any discrepancy lacks an approved explanation. Investigate before considering further validation. Full-file checks and any production authorization require separate work.

    Coverage Check

    • Rows reviewed: 3 of 3 pasted sample rows; 0 rows discarded, merged or modified. The full-file row count is unknown.
    • Target fields reviewed: 5 of 5 supplied fields, all explicitly mapped by A1.
    • Source columns accounted for: 6 of 6; five mapped and one intentionally excluded.
    • Sample required/type/enum/date checks: performed only against T1. Sample key comparison: performed only against T2.
    • Not performed: full-file parsing or validation, destination inspection, cross-file/destination duplicate checks, platform behavior testing or an actual import.

    This is a mapping-review handoff, not a guarantee of migration success or zero data loss.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Review the mapping before an import, without rewriting the source data. Import Mapping Review compares your pasted source columns and small authorized sample with the target requirements you supply.

    TEXT-ONLY DELIVERABLE The result is conversational review text. This skill does not generate a CSV, PDF or other downloadable output file.

    BRING THE RULES Supply ordered source headers, up to 20 fictional or redacted sample rows and target field requirements. Include key, enum, date, blank and create/update rules when known. No credentials, customer list or external account is needed. Links, screenshots and attachments are not opened.

    WHAT YOU GET

    • A source-linked mapping draft covering each target field
    • Explicitly supplied, proposed, unresolved and not-assessable decisions
    • An inventory of unmapped source columns
    • Sample exceptions for supplied rules, with original row references
    • Composite-key handling that does not mistake every repeated SKU for a duplicate
    • Unresolved authority, blank and update decisions kept visible
    • A human validation plan and a coverage check

    REVIEW, NOT A MIGRATION ENGINE It does not clean files, recover lost identifier formatting, invent platform rules, merge records, connect to a CRM or execute an import. The review cannot establish that an unseen full file or destination contains no duplicates. Existing native import validators remain important. A plausible field name is not proof of a correct mapping.

    Use only material authorized for your AI host. If policy or required consent prohibits processing, use a blank template or fictional exercise instead. Free describes the skill price; host charges and data policies still apply. The demonstration is fictional and self-initiated, not customer work or proof of time saved, successful migration or zero data loss.

    A small text review, not a CSV parser, full-file validator, platform certification or migration service. Requires supplied target rules for definitive checks. Cannot inspect attachments, infer missing values, detect destination duplicates or approve an import. Human validation remains necessary.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 28 days ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed28 days ago

    What's inside

    Frequently Asked Questions

    No. It returns conversational review text: mappings, sample exceptions and unresolved decisions. It does not generate a cleaned file, merge records, connect to an account or execute an import.

    Headers alone support a provisional mapping inventory, not value validation. Supply target requirements to check meaning, types, keys and accepted values. The skill does not invent an import schema from a platform name.

    No. A sample review cannot establish full-file quality or destination uniqueness. The output states what was and was not checked, then proposes a human-operated non-production validation step. No import is approved or performed.

    New in Data & Databases

    Free