CSV

**Judgement:** This CSV skill appears to be a well-thought-out, standards-aware utility focused on producing and consuming RFC 4180–compliant CSV that behaves predictably across Excel and other tools. The author clearly understands real-world CSV pitfalls (quoting, delimiters, encoding, Excel quirks), which suggests above-average quality within this narrow domain. **Key strengths & scenarios where it’s a good fit:** - When you need CSV that **opens cleanly in Excel** across locales (BOM handling, semicolon vs comma, embedded newlines, etc.). - When correctness around **quoting rules, embedded quotes/newlines, and column count validation** matters. - For data pipelines that must **ingest messy CSV** from varied sources and normalize them for further processing. - When you care about **Excel-specific issues** like formula injection, numeric precision, or scientific-notation surprises. **Risks & limitations:** - Scope is CSV-only; if you need broader data formats (Parquet/JSON/Arrow), this will be just one component. - No explicit evidence of performance tuning or streaming for very large files; treat performance as adequate but unproven for multi-GB workloads. - Reliability and safety look conceptually strong, but with limited public evidence (moderate download count and no exposed test matrix), production-critical use should include your own validation and benchmarking. **Recommended use:** Ideal as a **CSV interoperability layer** in ETL/ELT jobs, data export components, or integrations where Excel compatibility and edge-case correctness are important. For high-volume or mission-critical pipelines, pilot it with your largest and messiest CSVs to confirm performance and robustness before standardizing on it.