data-cleaning

data-cleaning is a skill for Claude Code, Codex from genspark-ai/genoffice. It costs 33 tokens per session (805 once invoked), scanned A, original, Apache-2.0.

A data-cleaning workflow that turns messy tables into a standardised table and a line-by-line Excel cleaning log. It checks blanks, mixed data types, duplicate records, inconsistent dates, units, codes, and text formatting before changes are made.

In plain words
What is it for?
Use it to prepare system imports, analysis tables, or mailing lists by defining cleaning rules, removing or flagging duplicates, standardising fields, and documenting each change.
Why use it?
It makes data problems visible and records what changed, which helps prevent accidental data loss or unexplained edits. Rules for deletion, deduplication, and formatting are confirmed before they are applied.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare system imports, analysis tables, or mailing lists by defining cleaning rules, removing or flagging duplicates, standardising fields, and documenting each change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/genspark-ai/genoffice/data-cleaning
About the project

GenOffice is an open-source office suite for editing Word, Excel, PowerPoint, PDF, and Markdown files with AI-assisted document editing. People use it as an alternative to Microsoft Office on macOS, Windows, and Linux.

genspark-ai/genoffice · 10,762 stars · on GitHub · genoffice.ai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add genspark-ai/genoffice --skill data-cleaning
Clone the repo
git clone --depth 1 https://github.com/genspark-ai/genoffice

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for data-cleaning

README.md
[![agentmods](https://agentmods.dev/badge/skills/genspark-ai/genoffice/data-cleaning/github.svg)](https://agentmods.dev/skills/genspark-ai/genoffice/data-cleaning)
Your own site
<a href="https://agentmods.dev/skills/genspark-ai/genoffice/data-cleaning"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/data-cleaning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for data-cleaning

Your own site · 80×15
<a href="https://agentmods.dev/skills/genspark-ai/genoffice/data-cleaning"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/data-cleaning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 805 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00805
Opus 5.5 $0.00013 $0.00322
Sonnet 5.5 $0.00007 $0.00161
Haiku 4.5 $0.00003 $0.00081

Measured 2d ago against content hash 644faf90f428, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

data-cleaning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/recommended/data-cleaning/SKILL.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 " 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.
  • Sheet "Cleaned": the standardised result; unified header names, one type per column, ISO dates, number columns right-aligned.
  • Sheet "Cleaning rules": # / Field / Problem / Rule / Rows affected.
  • Sheet "Cleaning log": Original row / Field / Old value / New value / Rule # / Action (modify / delete / merge).
  • Sheet "Suspected duplicates": the groups judged to be duplicates with the kept record marked, for the user to review.
  • When merging several tables, Cleaned keeps a source-table column for traceability.

Read the full file on GitHub · 43 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 43 lines · 33 tokens per session scan A 644faf90f428

Subscribe to this mod's changes

data-cleaning is a skill published in the GitHub repository genspark-ai/genoffice (10,762 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 805 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-23.