data-mapping
/data-mapping
Translate between an external service's data model and your own, handling mismatches, nulls, and enum drift explicitly. Use when integrating a service whose model differs from yours.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Translate between an external service's data model and your own, handling mismatches, nulls, and enum drift explicitly. Use when integrating a service whose model differs from yours.
Original author description
Translate between an external service's data model and your own, handling mismatches, nulls, and enum drift explicitly. Use when integrating a service whose model differs from yours.
How it works
- Method
- Boundaries
SKILL.md preview
--- name: data-mapping description: Translate between an external service's data model and your own, handling mismatches, nulls, and enum drift explicitly. Use when integrating a service whose model differs from yours. --- # Data mapping Two systems rarely agree on shape, naming, or what a field means. The mapping layer is where those disagreements are resolved, and doing it implicitly is how wrong data enters your system quietly. ## Method 1. **Map explicitly at the boundary.** One translation layer between their model and yours, so the rest of your code never sees their shape (see third-party-integration). 2. **Never store their identifiers as your primary keys.** Their identifier is a foreign reference, and coupling your keys to it makes provider migration nearly impossible. 3. **Handle unknown enum values without failing.** Providers add values, and a strict parser turns a routine provider change into an outage. 4. **Distinguish absent from null from empty.** These mean different things and providers use them inconsistently, so decide the mapping deliberately (see null-semantics). 5. **Validate on the way in.** Their data is untrusted input regardless of the provider's reputation (see input-validation). 6. **Record the raw payload alongside the mapped result.** When a mapping bug is found, the original is what allows reprocessing (see change-data-capture). 7. **Version the mapping.** Provider changes mean the mapping evolves, and knowing which version produced a record aids debugging. ## Boundaries Mapping resolves structure, not semantics: two systems can both call something status and mean unrelated things. Lossy mappings discard data that a later requirement needs, which is why raw payloads are worth keeping. Bidirectional sync multiplies the difficulty (see offline-sync).
Versions
The database has no other skills named data-mapping.
Database snapshot: 13.11.2026 · package version 43e3ff214faa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100service-registry
Registers external services with health checks, central config, and unified execution. Use when integrating multiple external services needing coordination. - 100add-service
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.