agentleFS
bastosbastos/skills/review-training-data-quality/SKILL.md

review-training-data-quality

Skill7 starsChanged 10 months agoMITView on GitHub

Audits a candidate or labeled training corpus for distribution collapse, ambiguity, context sufficiency, hard-negative quality, abstention behavior, leakage, and stable label defensibility. Use before scaling teacher calls or starting fine-tuning.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Distinctive:

    Test whether the dataset teaches the intended capability rather than merely producing an easy loss curve.

    line 8
  2. Distinctive:

    Use the generic JSONL summary helper:

    line 14
  3. Distinctive:

    Look beyond equal row counts.

    line 22
  4. Distinctive:

    every lane has sufficient facts to make a defensible choice.

    line 34
  5. Distinctive:

    Run a small balanced teacher preflight before labeling the full corpus.

    line 36

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

Review Training Data Quality

Test whether the dataset teaches the intended capability rather than merely producing an easy loss curve.

Inspect deterministic distributions

Summarize every product-relevant axis by split and overall: source group, task lane, goal, format, label, abstention, difficulty, candidate count, sequence length, terminal state, role, and preferred-answer position.

Use the generic JSONL summary helper:

python scripts/summarize_jsonl_fields.py corpus.jsonl \
  --field split --field lane --field goal --field label \
  --output quality-distributions.json

Look beyond equal row counts. Verify group-safe splits, distinct source groups, reasonable joint distributions, and enough examples at safety boundaries. Flag any category whose dominance would let the model ignore important context.

Review candidate and label quality

Check that:

  • positives are legal, plausible, and supported by supplied context;
  • hard negatives are tempting but wrong for an explainable reason;
  • multiple acceptable answers are preserved when evidence supports them;
  • abstention is available and labeled only when warranted;
  • teacher outputs use supplied identifiers and validate without silent repair;
  • prompts exclude reference answers and teacher-only metadata;
  • every lane has sufficient facts to make a defensible choice.

Run a small balanced teacher preflight before labeling the full corpus. Stop on identifier, replay, legality, terminal-boundary, context, or label-collapse failures.

Test label defensibility

Blind-review difficult representative cases twice with candidate order reversed. Select cases from metadata, not label outcomes. Count a judgment as stable only when both orders choose the same underlying answer. Preserve ties, ambiguity, both-poor, and insufficient-context results.

Define the stability threshold before review. If the threshold fails, fix the smallest corpus or rubric defect before scaling. More examples of the same biased lane are not evidence of broader capability.

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.