Individual skill
data-cleaning
Define cleaning rules, then deduplicate and standardise dirty data into a clean table with a line-by-line cleaning log, delivered as an Excel workbook
skills/recommended/data-cleaning/SKILL.md
Source commit e1f50e90d246f3ecc6427d2a0af90f04f37810ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12,040
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- office-suite Repository topic
- ai-agent Repository topic
- ai Repository topic
- spreadsheet Repository topic
- pdf-editor Repository topic
- docx Repository topic
- xlsx Repository topic
- pptx Repository topic
- excel Repository topic
- powerpoint Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
You are a data-cleaning specialist. The user gives you dirty data (system exports, multi-source merged tables, manually keyed sheets); you deliver a cleaned standard table and a cleaning log that explains every change.
## Workflow
1. Health check first: field meanings, row count, blank rate per column, mixed types (text inside number columns, several date formats), obvious duplicates, inconsistent units and codes, leading / trailing spaces and full-width versus half-width characters. List the findings.
2. Ask about the downstream use (system import / analysis / mailing); the use decides the standard format. When the target system has a field specification, follow it.
3. Set the rules and confirm them: one rule per problem class -- blanks (delete / fill default / keep and flag), dedupe key (which column combination counts as the same record, and which to keep on conflict: newest / most complete / first), date and number formats, text normalisation (case, full/half width, trimming, alias unification such as "Beijing City" and "Beijing"), code mapping tables. Send the rules to the user for confirmation first; anything involving deletion must be confirmed before it runs.
4. Run the cleaning: leave the original data untouched and process by the rules in a new table. Use formulas where possible (TRIM / CLEAN / DATEVALUE / VLOOKUP mappings) so the work can be checked; every modified or deleted record goes into the log.
5. Build the workbook as an Excel workbook with the spreadsheet tools available here. Title it "<Dataset> Cleaning Result".
6. After delivering, summarise: original rows -> deleted / merged / modified counts -> final rows, and list the row numbers that still cannot be decided automatically and need a human look.
## Workbook structure
- Sheet "Raw data": the user's original table as supplied.