croissant-validator
Skill30 starsChanged 50 days agoBSD-2-ClauseView on GitHub
Validates and generates Croissant metadata for ML datasets. Use when checking dataset metadata compliance, creating new croissant.json files, validating existing metadata, or ensuring ML dataset descriptions follow the MLCommons Croissant format specification.
- Deletes or force-pushes
- Installs packages
In this repository30 other files it gives its agents.
- skills/academy/agents.mdAGENTS.md
- academySkill
- amsc-data-movement-apiSkill
- amsc-magSkill
- amsc-python-clientSkill
- globus-computeSkill
- i2-apiSkill
- iri-apiSkill
- skill-explorerSkill
- datacard-generatorSkill
- hdmf-schema-builderSkill
- skill-creatorSkill
- well-convertSkill
- card-eval-updaterSkill
- agentic-vulnerabilities-scanSkill
- ai-fingerprintSkill
- battleprintSkill
- fingerprintingSkill
- uncertainty-quantificationSkill
- uq-metrics-evaluatorSkill
- skill-searchSkill
- auroraSkill
- frontierSkill
- pbsSkill
- perlmutterSkill
- slurmSkill
- literature-searchSkill
- multi-agent-systemsSkill
- gkeyllSkill
- gs2Skill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Keep executable code in scripts/.
- Very specific: line 35
Never run global pip install.
- Very specific: line 44
If mlcroissant validation is required, run in venv:
- Distinctive: line 74
If needed, rerun generation or patch metadata manually.
- Very specific: line 101
Add checksums to cr:FileObject entries.
- Very specific: line 102
Add missing field.source mappings.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Croissant Metadata Validator & Generator
Validate and generate croissant.json metadata for ML datasets.
Use This Skill When
- User asks to validate Croissant metadata.
- User asks to create or update
croissant.json. - User asks for MLCommons Croissant conformance checks.
Skill Layout
scripts/validate_croissant.py: required-field checks + optionalmlcroissantvalidation.scripts/generate_croissant_from_csv.py: generate metadata from CSV headers and sample values.
Keep executable code in scripts/; keep SKILL.md focused on workflow.
Python Environment Rule
For any command requiring package installs, use a temporary venv in the working directory and remove it after execution.
python3 -m venv .venv_croissant && \
.venv_croissant/bin/pip install -q mlcroissant pandas && \
# ... run command(s) ... && \
rm -rf .venv_croissantNever run global pip install.
Validation Workflow
- Locate metadata file (
croissant.json,metadata.json, or user-provided path). - Run script-level validation:
python3 skills/croissant-validator/scripts/validate_croissant.py path/to/croissant.json - If
mlcroissantvalidation is required, run in venv:python3 -m venv .venv_croissant && \ .venv_croissant/bin/pip install -q mlcroissant && \ .venv_croissant/bin/python skills/croissant-validator/scripts/validate_croissant.py path/to/croissant.json && \ rm -rf .venv_croissant - Report: pass/fail, missing required fields, structural warnings, and fix suggestions.
Generation Workflow (CSV)
- Collect required inputs:
- dataset name
- description
- SPDX license URL
- creator name
- dataset URL
- Generate metadata from CSV:
python3 skills/croissant-validator/scripts/generate_croissant_from_csv.py \ data.csv \ "My Dataset" \ "Dataset description" \ "https://spdx.org/licenses/MIT.html" \ "Creator Name" \ "https://example.com/dataset" \ --output croissant.json \ --cite-as "@misc{my-dataset-2026, title={My Dataset}, author={Creator Name}, year={2026}}" - Validate generated file with
validate_croissant.py. - If needed, rerun generation or patch metadata manually.
Required Metadata Fields
@context@type=sc:DatasetconformsTo=http://mlcommons.org/croissant/1.0namedescriptionlicenseurlcreatordatePublisheddistribution
High-Value Checks
- All
@idvalues are unique. - Each
cr:FileObjecthassha256ormd5. recordSet/fieldreferences are valid.- Dates use ISO format (
YYYY-MM-DD). - License uses SPDX URL.
Common Fixes
- Add missing
conformsTo. - Replace non-SPDX license values with SPDX URLs.
- Add checksums to
cr:FileObjectentries. - Add missing
field.sourcemappings.
Resources
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.

