agentleFS
AI-ModConAI-ModCon/genesis-skills/skills/basedata-skills/croissant-validator/SKILL.md

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

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
  1. Very specific:

    Keep executable code in scripts/.

    line 22
  2. Very specific:

    Never run global pip install.

    line 35
  3. Very specific:

    If mlcroissant validation is required, run in venv:

    line 44
  4. Distinctive:

    If needed, rerun generation or patch metadata manually.

    line 74
  5. Very specific:

    Add checksums to cr:FileObject entries.

    line 101
  6. Very specific:

    Add missing field.source mappings.

    line 102

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 + optional mlcroissant validation.
  • 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_croissant

Never run global pip install.

Validation Workflow

  1. Locate metadata file (croissant.json, metadata.json, or user-provided path).
  2. Run script-level validation:
    python3 skills/croissant-validator/scripts/validate_croissant.py path/to/croissant.json
  3. If mlcroissant validation 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
  4. Report: pass/fail, missing required fields, structural warnings, and fix suggestions.

Generation Workflow (CSV)

  1. Collect required inputs:
    • dataset name
    • description
    • SPDX license URL
    • creator name
    • dataset URL
  2. 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}}"
  3. Validate generated file with validate_croissant.py.
  4. If needed, rerun generation or patch metadata manually.

Required Metadata Fields

  • @context
  • @type = sc:Dataset
  • conformsTo = http://mlcommons.org/croissant/1.0
  • name
  • description
  • license
  • url
  • creator
  • datePublished
  • distribution

High-Value Checks

  • All @id values are unique.
  • Each cr:FileObject has sha256 or md5.
  • recordSet/field references 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:FileObject entries.
  • Add missing field.source mappings.

Resources

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.