Data cleaning automation expertise covering missing value strategies, outlier detection methods, duplicate detection and deduplication, data type correction, text normalization, date parsing across formats, encoding fixes, validation rules, pipeline design patterns, and data quality reporting.
Use when the user asks about data scrubber, data scrubber best practices, or needs guidance on data scrubber implementation.
Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Data cleaning automation expertise covering missing value strategies, outlier detection methods, duplicate detection and deduplication, data type correction, text normalization, date parsing across formats, encoding fixes, validation rules, pipeline design patterns, and data quality reporting.
Use when the user asks about data scrubber, data scrubber best practices, or needs guidance on data scrubber implementation.
Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
Data cleaning is the unglamorous but critical foundation of any data-driven system. Raw data is messy: missing values, inconsistent formats, duplicates, encoding errors, and outliers. A systematic data cleaning pipeline transforms raw chaos into reliable, analysis-ready data. The goal is not perfection -- it is fitness for purpose. Every cleaning decision should be documented, reversible, and auditable.
Never modify raw data in place: Always work on copies, keep originals
Document every cleaning decision: Why was this value removed/changed?
Make cleaning reproducible: Scripts, not manual edits
Generate quality reports before AND after cleaning: Measure improvement
Handle edge cases explicitly: Empty strings, whitespace-only, special characters
Validate after cleaning: Ensure constraints are satisfied
Use appropriate methods per data type: Median for numeric, mode for categorical
Be conservative with outlier removal: Flag first, remove only when justified
Test cleaning pipeline on sample data: Verify behavior before full run
Version control cleaning scripts: Track changes to cleaning logic
When to Use
Use this skill when:
Designing or implementing data scrubber solutions
Reviewing or improving existing data scrubber approaches
Making architectural or implementation decisions about data scrubber
Learning data scrubber patterns and best practices
Troubleshooting data scrubber-related issues
Do NOT use this skill when:
The question is about a fundamentally different technology domain
A more specific sibling skill covers the exact topic needed
The user needs a complete hands-on tutorial rather than expert guidance
Output Format
# Data Scrubber Analysis## Context Assessment
[Situation summary and constraints]
## Recommended Approach
[Primary recommendation with rationale]
## Implementation Steps1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]
## Trade-offs and Considerations- [Key trade-off 1]
- [Key trade-off 2]
## Next Steps- [Immediate action item]
- [Follow-up action item]
Example
Input: "Help me implement data scrubber for a medium-scale production application"
Output: A structured analysis covering current state assessment, recommended data scrubber approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.
Edge Cases
Legacy system integration: When data scrubber must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities