kg-adoptlisted
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-adopt — adopt an existing competition repo
Run kgkit with the Bash tool, as `PYTHONPATH="${CLAUDE_PLUGIN_ROOT}" python -m kgkit <command>`: this command
pre-approves that form for the kgkit calls it makes. Submitting, pushing or publishing still asks (so does a
PowerShell `$env:` assignment).
Arguments: `$ARGUMENTS` (competition slug; optional when the repo's `kernel-metadata.json` or README names it).
kgkit: use the absolute path from the session context ("kgkit home"), else `$KGKIT_HOME`, else
`${CLAUDE_PLUGIN_ROOT}`. Invoke as `PYTHONPATH=<kgkit home> python -m kgkit <cmd>`
(PowerShell: `$env:PYTHONPATH="<kgkit home>"; python -m kgkit <cmd>`).
The repo already has its own layout, scripts, ledger and validation. **Adopt, do not rebuild**: no data
download, no new folds, no new baseline, no moving files. The point is to switch on what the plugin
does around the existing work: submission logging and the daily budget, the session status brief,
`kgkit status` / `ledger` / `kernels top` / `discussions`.
1. **Facts.** Read the README, kernel folders (`kernel-metadata.json`: `competition_sources`,
`enable_internet`, `enable_gpu`) and any notes to find: slug, metric and direction, task, target,
id column, code competition (runtime limit, internet), daily submissions, deadline. Fill gaps with
`kaggle competitions list -s <slug>` (deadline) and the `competition-recon` skill; ask the user
only for what you cannot determine.
2. **Workspace.** Run from the repo ro