import-mapping-feedback-loop

Resolve exact-match header and material mappings during CSV/XLSX imports.

Updated Mar 16, 2026

Search Tags:#workflow #validation #deterministic #headers #mapping #import #materials

Ready to run

npx skills add https://github.com/BSchafer01/PanelNester --skill import-mapping-feedback-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: import-mapping-feedback-loop
Source: https://github.com/BSchafer01/PanelNester/tree/main/.squad/skills/import-mapping-feedback-loop
Command: npx skills add https://github.com/BSchafer01/PanelNester --skill import-mapping-feedback-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicit import-time mapping ensures headers and material names remain aligned with the canonical library, preventing drift and misclassification when source files change or contain unknown values.

Core Features & Use Cases

Return mapping metadata on every import response, including detected columns and the status of each material.
Enforce explicit user mapping before import succeeds, while preserving the fast path for exact matches.
Rewrite imported material values to canonical library names prior to validation, and keep the parsing phase separate from side effects to support safe recovery and library updates.

Quick Start

Map the header aliases and material names explicitly during import to guarantee deterministic results.

Frequently Asked Questions about import-mapping-feedback-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce deterministic CSV imports when file headers drift or change?▼

You enforce deterministic CSV imports by resolving exact-match header mappings and requiring explicit user confirmation for unknown columns before allowing the import to succeed. This prevents misclassification when source files change.

What is the best way to handle unknown materials in an XLSX import workflow?▼

The best way to handle unknown materials in an XLSX import workflow is to return per-import mapping metadata showing each material's status, then require explicit user mapping before creating new materials or completing the import.

How does separating parsing from side effects improve file import validation?▼

Separating parsing from side effects during file import validation ensures that new materials are created only after explicit user confirmation. This isolation supports safe recovery and prevents unintended library updates during the mapping phase.

Can I preserve a fast path for exact header matches while still requiring explicit mapping for unknowns?▼

Yes, you can preserve a fast path for exact header matches while enforcing explicit user mapping for unknowns. The workflow returns mapping metadata for detected columns and requires user confirmation only for header drift or unknown materials.

Why do my imported material values need to be rewritten to canonical library names before validation?▼

Imported material values must be rewritten to canonical library names before validation to prevent drift and misclassification. This ensures all imported data aligns with the canonical library and maintains deterministic behavior across changing source files.