data-cleaning-planner
Skill4 starsChanged 4 months agoLicence not identifiedView on GitHub
Use this skill when planning or reviewing data cleaning for empirical research. Given a variable list and data dictionary, it drafts a cleaning plan; checks whether a merge/join is sound (1:1 vs m:1, key name/case/type/leading-zero consistency, expected match rate); explains the differences among missing-value handling, outliers, winsorizing, trimming, log transform and standardization; recommends exploratory plots given variable types; explores each table's observation unit, grain, primary key and shape (long/wide) into a review checklist; and plans text-variable extraction without hand-writing regex. Emphasizes judgment and human review; never fabricates data, codebooks, or results.
In this repository7 other files it gives its agents.
- paper-contextSkill
- paper-strategySkill
- replication-navigatorSkill
- regression-interpreterSkill
- repro-loggerSkill
- stata-runnerSkill
- data-auditSkill
The file
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.