csv-cleaner
Skill0 starsChanged 5 months agoMITView on GitHub
Use when the user provides a CSV or TSV file that is broken, malformed, or messy. Triggers on phrases like "fix this CSV", "clean up this data", "this CSV won't import", or when a file with .csv/.tsv extension is shared and the contents show obvious problems (mixed delimiters, encoding artifacts like ÃÂ, ragged rows, headers in the middle, etc.).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 0xelitesystem/claude-skills-templatestheir own version, first seen Apr 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 0xelitesystem/claude-skills-templates★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- api-docs-from-openapiSkill
- changelog-writerSkill
- code-review-preflightSkill
- json-schema-from-sampleSkill
- meeting-notes-summarizerSkill
- regex-builderSkill
- sql-from-questionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Inspect the first 200 lines: Don't load the whole file blindly.
- Distinctive: line 34
If >95% of non-empty values fit a type, suggest that type
- Distinctive: line 35
Never coerce silently; report the inference and let the user confirm
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CSV Cleaner
Detect and fix common CSV problems without losing data.
Process
- Inspect the first 200 lines. Don't load the whole file blindly. Look for:
- Encoding artifacts (
ÃÂ,’,\ufffd) → likely UTF-8 read as Latin-1 or vice versa - Mixed delimiters (commas in some rows, tabs in others) → file is mislabeled
- Quoted fields containing the delimiter
- Headers appearing more than once (file is concatenated dumps)
- Trailing commas (Excel quirk)
- BOM at start of file
- Encoding artifacts (
- State the diagnosis to the user before changing anything. "I see X, Y, Z problems. I will fix them by doing A, B, C. Confirm or tell me what to skip."
- Fix in this order:
- Re-decode encoding if artifacts present (try cp1252 → utf-8, latin-1 → utf-8)
- Strip BOM
- Detect actual delimiter via
csv.Snifferor character-frequency analysis - Re-parse with the correct delimiter and quote character
- Drop duplicate header rows (keep first)
- Pad ragged rows with empty strings rather than dropping them; flag the row count
- Trim whitespace from cell values but NOT from quoted strings
- Type inference (only if user requested):
- For each column, sample 100 rows
- Try int → float → date (ISO, US, EU formats) → bool → string
- If >95% of non-empty values fit a type, suggest that type
- Never coerce silently; report the inference and let the user confirm
- Output: save as a NEW file (don't overwrite the original). Default name:
<original>_cleaned.csv. Always UTF-8, always LF line endings, always RFC 4180 quoting.
What NOT to do
- MUST NOT silently drop rows. Pad them or flag them.
- MUST NOT rename columns unless the user asks.
- MUST NOT change cell values (other than re-encoding) unless explicitly requested.
- MUST NOT assume the first row is a header without checking. Ask if the file has no consistent header.
Edge cases worth flagging
- Files larger than 100MB: ask if streaming is okay before loading into memory
- Files with no clear delimiter (likely fixed-width): say so and ask the user to confirm
- Files where the header has fewer columns than the data: data row with the most columns sets the count
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

