tabular-audit
First step for a table: profile it, fix the target and problem type, find leaking and impossible columns. Usually the first step of a tabular plan. Check: expects reports/audit.md.
- License 许可
- MIT
- 最近更新
- 2026-10-25
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- tabular-audit
- metadata
- { "beyondml": { "kind": "step", "modality": "tabular" } }
- description
- First step for a table: profile it, fix the target and problem type, find leaking and impossible columns. Usually the first step of a tabular plan. Check: expects reports/audit.md.
- allowed-tools
- read_file list_files write_file run_python profile scan_leakage chart ask_user finish_step
03 SKILL.md 正文
You audit the raw table before anything is built on it.
- Call profile(path=<the raw file>) and read the target analysis and the ranked target candidates.
- Confirm the target. Call ask_user("Which column is the target?", options=<the ranked candidates>, recommended=<the top candidate>) and use the answer.
- Call profile again with target=<the target> and note the problem type (classification or regression).
- Call scan_leakage(path, target). Treat target_correlation and single_feature_score suspects as leaks; treat id_like columns as drop candidates; name hints need your judgement.
- Look for impossible values (sentinels such as age 999 or zip 00000, negative counts, future years). Only flag values that are clearly impossible, not merely rare.
- Write reports/audit.md with write_file: target, problem type, the drop list with one reason per column, impossible values per column.
- Call finish_step with a summary that states the target, the problem type and the drop list, and outputs=["reports/audit.md"].
04 同仓库更多 Skills
tabular-demo
Demo step skill for tabular data.
leakage-demo
Demo knowledge skill about target leakage.
bad-name
Name does not match its folder.
train-test-split
How to split data so the score is honest.
tabular-features
Writes src/features.py with derived features (ratios, logs, interactions) and no target use. Usually right after tabular-eda. Check: run src/features.py, expects data/processed/features.csv.
tabular-export
Writes the shipped code (src/pipeline.py, src/train.py, src/predict.py) from the winning run and trains it. Usually right after evolve-search or tabular-ensemble. Check: run src/train.py, expects models/model.joblib, metric accuracy (classification) or r2 (regression) with a minimum.