Files and data

Neo can inspect supported files, extract information, summarize documents, transform content, analyze tables, and create new artifacts. Your request should identify the source of truth and define how completeness will be checked.

Common file tasks

• Summarize a long document with section references.
• Extract a list, table, or defined set of fields.
• Compare two versions and explain material differences.
• Classify or restructure tabular data.
• Identify trends, anomalies, duplicates, and missing values.
• Convert notes into Markdown, CSV, or a report.
• Review code or documentation in a workspace.
• Produce a new file from several inputs.

Prepare the inputs

Name the files Neo should use and explain their roles. If several versions exist, identify the authoritative one. State whether files contain headers, formulas, multiple sheets, scanned pages, hidden content, or unusual encodings when relevant.

Use approved-pricing.xlsx as the source of truth. Compare it with website-export.csv, match records by SKU, and create a CSV of differences. Do not modify either input.

Ask for a schema

For extraction or transformation, define the output fields and how missing or ambiguous values should be represented.

Return one row per contract with columns for counterparty, effective date, renewal date, termination notice, governing law, and source page. Use Not stated rather than guessing.

Data analysis workflow

1. Inspect the file structure and report what is present.
2. Confirm data types, units, date formats, and missing values.
3. Apply the requested cleaning or analysis.
4. Explain calculations and any rows excluded.
5. Validate totals, row counts, or samples.
6. Create the requested artifact and summarize its location.

Documents and PDFs

Text extraction may be imperfect for scans, complex layouts, handwriting, or embedded charts. Ask Neo to identify unreadable sections and cite page or section locations when possible. Confirm important quotations against the original file.

Spreadsheets and tables

State whether formulas must be preserved, recalculated, or replaced with values. Ask for checks such as row counts before and after cleaning, uniqueness of keys, reconciliation totals, and a list of rejected records.

Safer file editing

For existing workspaces:

• ask Neo to inspect before editing;
• limit which files may change;
• preserve originals unless replacement is required;
• request a summary or diff;
• keep backups or version control;
• validate outputs with the application that will consume them.

Verify generated artifacts

Never assume that a file is correct because it was created successfully. Open it, confirm that it renders, inspect a sample against the sources, and check that the file type, formulas, links, and formatting survived the transformation.