Plan and verify internal web tools, desktop tools and local connectors for importing, merging, exporting, migrating and restoring business records and original files.
For owners of internal workbenches, libraries and local tools. On import, merge or device change, check the authorized source of truth, storage, business keys and originals. Use a read-only preview and an isolated copy to deliver differences, a data package and recovery evidence.
How to verify the work
Use a consistent snapshot to replay duplicate imports, conflicts and interruptions. Match changes by business key and verify records, original bytes and references. Restore to a new location, reopen the tool, find records and open attachments.
When to hand it over
Give the data owner the preview, conflicts and unresolved items. Hold the affected write, restore or sharing if merge rules are unsettled, originals are missing or access to the new location is unverified. Gather evidence within actual permissions.
What to measure
Log conflicts and missing files found before import and count records and originals that reopen after restoration.
What it does
Use stable business keys and isolated trials to verify imports, merges, exports and restoration.
What it helps with
See conflicts before bulk writes and verify records and source files from a separate entry point afterwards.
Why it matters
Keep business records and attachment provenance available when teams change tools, accounts or devices.
PDF · Chinese
Guide
Core guidance, examples and a revision worksheet. PDF in Chinese.
Identify the authoritative data source, actual storage locations and concurrent writers. Use stable business keys, read-only previews and isolated replays to protect records, attachments and provenance. The workflow applies to workbenches, repositories and local tools.
What to prepare
Locations and authoritative sources for records, originals, caches and authorized folders
Schema versions, business keys, merge rules, and actual account or device permissions
Records, references, and attachments to preserve, plus migration or failure samples
What you receive
An import diff that distinguishes new, unchanged, conflicting, unmatched and missing attachment records
A handoff package covering the agreed records, originals, references and verification data
A record of the isolated replay, recovery to a new location and read-back after reopening
Who it is for
Merge two project libraries while preserving attachments and provenance
Migrate existing data before changing machines, browser origins or drives
Reproduce import conflicts, incomplete packages, disk disconnection or revoked access
How the work progresses
01
Record the actual locations and writers of databases, originals, indexes and caches
02
Preview matches and conflicts without writing. Retain provenance and distinguish true zero, empty values and uncollected data
03
Start from a consistent snapshot and replay duplicate inputs, concurrent changes, interruptions, corrupt packages or revoked access in isolation
04
Verify bytes and references. Restore to a new location, reopen the tool, find the records and open their originals
Getting started
Download and extract the complete ZIP. Read the README if included, or start with SKILL.md. Install the complete folder containing SKILL.md in your AI tool’s skills directory under the skill name. In a multi-version repository, choose the version you need and retain its supporting files. Try a small task with the required inputs and review the result.
Plan and verify internal web tools, desktop tools and local connectors for importing, merging, exporting, migrating and restoring business records and original files.