ecm-import-mapper

Maps CSV exports to ECM Studio import artifacts using a mapping JSON.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/ThomasRohde/ecm-studio --skill ecm-import-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecm-import-mapper
Source: https://github.com/ThomasRohde/ecm-studio/tree/main/.agents/skills/ecm-import-mapper
Command: npx skills add https://github.com/ThomasRohde/ecm-studio --skill ecm-import-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert external CSV capability exports into ECM Studio import-ready artifacts such as CSV, JSONL, or bundled JSON, enabling seamless integration with ECM repositories and avoiding direct edits to live files.

Core Features & Use Cases

  • Import preparation for ECM model repositories by mapping source columns to capability fields
  • Generate stable import artifacts (CSV, JSONL, or bundled JSON) without touching ecm/capabilities.jsonl
  • Validate import shape, detect missing fields, duplicates, and hierarchy issues for safe ingestion

Quick Start

Run the mapper with your source CSV and a mapping JSON to produce an import artifact for ECM Studio.

Frequently Asked Questions about ecm-import-mapper

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

FAQPage Schema
How do I convert external CSV exports into ECM Studio import artifacts?

To convert external CSV exports into ECM Studio import artifacts, you run the mapper with a source CSV and a mapping JSON to deterministically generate stable CSV, JSONL, or bundled JSON files for repository ingestion.

What is the best way to map source columns to ECM capability fields before import?

The best way to map source columns to ECM capability fields is using a mapping JSON alongside your source CSV, which deterministically produces an import artifact that can be reviewed before ingestion.

Can I validate import shapes and detect duplicates when preparing ECM imports?

Yes, you can validate import shapes during ECM artifact preparation to detect missing fields, duplicates, and hierarchy issues, ensuring safe ingestion into capability repositories without direct edits to live files.

Does ECM import mapping work with JSONL and bundled JSON formats?

ECM import mapping works with JSONL and bundled JSON formats, allowing you to generate stable import artifacts from source CSV data without directly touching the ecm/capabilities.jsonl file.

Do I need a mapping JSON file to prepare ECM capability repository imports?

Yes, a mapping JSON file is required alongside your source CSV to deterministically produce an import artifact, ensuring source columns are accurately mapped to capability fields before review.

Why does ECM import preparation avoid direct edits to live capability files?

ECM import preparation avoids direct edits to live capability files by generating stable, reviewable artifacts like CSV or JSONL, preventing accidental data corruption during repository ingestion.