CSV Manual Export

CSV Manual Export renders an already confirmed business field list as a clean CSV. It acts as a transport helper for an active module's schema, rather than defining a new table. The header preserves exact field names and their canonical order. A template contains the header and no data rows unless illustrative rows were explicitly requested.

The skill distinguishes template creation, synthetic examples, corrections, column mappings and target-specific imports before doing the work. An import failure receives the requested escaping or column correction. A request for a mapping receives the mapping alone. SQL, JSON and Notion mappings are additional deliverables only when requested, keeping a CSV-only request focused on the file.

Use it for a CSV template, an Excel-compatible CSV, a Notion import file, database staging data or a handoff between systems. A confirmed source module supplies the fields; if that module is unknown or the field list is ambiguous, the skill asks which list to export. Already supplied names, types, options, statuses, dates and IDs are reused.

Do not use it to create a database, upload a file, schedule a load or clean up a destination system. Row and file-size limits belong to the importer. Successful generation does not establish successful import: the user must import the file and check it. Legal, tax and payroll review remains necessary before using the file for real decisions.

Inputs include the source module, confirmed field list, named destination and any material encoding or delimiter requirement. Clarifying questions arrive individually and only when the answer changes the file. The output is data-only CSV, with necessary type notes or material limitations provided separately.

UTF-8 is the default. Excel compatibility calls for a byte order mark, while a strict importer that rejects it calls for its omission. Comma is the normal delimiter; a different delimiter follows the named target's requirements. The helper neither silently renames nor drops fields, adds guessed columns, or reorders them without reason.

Values containing a comma, quote or line break are quoted, and embedded quotes are doubled. Machine-readable dates use ISO YYYY-MM-DD unless the user requests another format. Missing dates stay missing. Monetary cells use numeric values without currency symbols unless the source schema embeds a currency. A generated ID is not invented to fill a template.

An empty header example is:

Field 1,Field 2,Field 3

Example rows, when requested, must be obviously fake, consistent and non-sensitive. Template generation remains empty by default. Reviews and conversions use only necessary supplied fields and avoid repeating sensitive identifiers.

CSV does not enforce numbers, currency, dates, select configurations, formulas, constraints or relations. Required type mappings and select options travel beside the file. A relation cell carries a reference key; the destination creates the working link after its target database exists. The helper does not add lookup formulas or promise link resolution. Related notion-manual-import and spreadsheet-manual-build skills provide Notion import guidance and workbook formatting for the same field list.