dataset-audit
Skill0 starsChanged 4 months agoApache-2.0View on GitHub
Audit a Hugging Face dataset before training or evaluation. Use before any training job, when choosing between datasets, or when a KeyError or format mismatch appears during training.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- BraveDistribution/claude-skillstheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- BraveDistribution/claude-skills★ 0same 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 repository5 other files it gives its agents.
- hf-doctorSkill
- hf-jobsSkill
- ml-autopilotSkill
- ml-internSkill
- trackioSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 7
Before working with any dataset, audit it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Before working with any dataset, audit it. Do not assume you know what the data looks like, inspect it. Looking at data is the best way to boost model performance and the cheapest way to prevent failed jobs.
One call does the audit:
hf-dataset-inspect <repo_id> [--config C] [--split S] [--rows N]It returns validity status, configs and splits, the schema, row counts, sample rows, and parquet info as one JSON object.
Check, in order:
- The dataset loads at all (status). If it does not, tell the user; never substitute a different dataset silently.
- Columns match the training method:
- SFT: "messages", "text", or "prompt"/"completion"
- DPO: "prompt", "chosen", "rejected"
- GRPO: "prompt"
- Row counts per split are sane for the plan (enough for training, an eval split exists when evaluation is expected).
- Sample rows look right: read several end to end. Surface anything notable to the user: class imbalance, missing values, unexpected formats, duplicates, truncated text, license or gating surprises.
Private datasets and ones behind an access request need HF auth; if the inspect call reports an auth error, run /hf-doctor first.
Record the verified column names in your plan and assert them at the top of every training script. The audit is a prerequisite for /hf-jobs preflight; a job submitted against unverified columns is a wasted GPU hour.
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.

