/leakage-check
Audit data preprocessing and splitting logic for target leakage.
$ npx -y skills add yeaight7/agent-powerups --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/leakage-check
Context preview
What this command does when you run it.
Audit data preprocessing and splitting logic for target leakage.
Command definition
leakage-check.mddescription: "Audit data preprocessing and splitting logic for target leakage." argument-hint: "<preprocessing_script_path>"
Leakage Check Command
CRITICAL BEHAVIORAL RULES
1. **Hunt the Future**: Target leakage occurs when information from the future (the target variable) sneaks into the training features.
Execution Steps
1. Read the preprocessing and splitting code. 2. **Split First**: Verify that the dataset is split into train/val/test *before* any global transformations are applied. 3. **Imputation Leakage**: Verify that scalers, encoders, and imputers are `fit` ONLY on the training set, and `transform` is applied to train/val/test. If `fit_transform` is used on the entire dataset, flag it as a critical leakage error. 4. **Feature Leakage**: Look for features that are direct proxies for the target (e.g., a "cancellation_date" feature when predicting churn). 5. **Output**: Generate a Leakage Audit Report highlighting unsafe transformations and risky features.
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Repo: yeaight7/agent-powerups
Other commands on agent-powerups.
- /bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Open command - /build-fix
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Open command - /debug
Use when a bug needs systematic diagnosis before a fix is attempted.
Open command - /doctor
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Open command - /implement
Use to turn a spec or user request into working, tested code.
Open command - /mcp-check
Use to check MCP server prerequisites before activating or using a server.
Open command

