Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/schema-mapper

@9449d36
Run it yourself

Document column-level mappings between source and target schemas. Use when integrating data from multiple systems, designing ETL transformations, or documenting how raw fields become analytical assets.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/schema-mapper

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈557 when used: this file. ≈1.2k more on demand in 2 files.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈217 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Schema Mapper

When to use

  • Integrating a new data source and need to map its fields to the existing data model
  • Designing an ETL or dbt transformation and need to document the logic
  • Auditing what happened to a field during a migration
  • Onboarding a new analyst who needs to understand where columns come from
  • Preparing a data catalog entry that requires lineage at the column level

Process

  1. Collect the source schema — list every column name, data type, nullable flag, and a brief description. Pull from INFORMATION_SCHEMA, a data dictionary, or the source API documentation.
  2. Collect the target schema — same structure for the destination table or model. If the target doesn't exist yet, draft it based on the analytical requirements.
  3. Map source columns to target columns — for each target column, identify the source column(s) that feed it. Record direct mappings (rename only) and derived mappings (calculation, type cast, lookup join). Use scripts/schema_compare.py to automate direct-name matches.
  4. Document transformation rules — for each derived mapping, write the exact transformation (e.g., CAST(amount_cents AS FLOAT) / 100.0, COALESCE(first_name, email)).
  5. Flag gaps — identify target columns with no source (need to be created or defaulted) and source columns with no target (dropped or deferred). Record a decision for each.
  6. Produce the mapping document — complete assets/schema_mapping_template.md with the full column inventory and share for review before implementation.

Inputs the skill needs

  • Source schema: table name, column names, data types, and descriptions
  • Target schema: same, or the analytical requirements that define it
  • Any existing transformation logic (SQL, dbt models, Python code)
  • Business rules that govern how values should be transformed or defaulted
  • Stakeholder who can resolve ambiguous fields

Output

  • scripts/schema_compare.py — compares two schemas and finds direct-name matches and type mismatches
  • assets/schema_mapping_template.md — completed column-by-column mapping with transformation rules, gaps, and decisions
  • Optional: transformation SQL or dbt YAML generated from the mapping

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo4 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is a database schema mapping tool that requires database credentials and processes schema metadata to generate documentation. It presents a standard surface for indirect prompt injection and involves handling sensitive credentials.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/schema-mapper