← ClaudeAtlas

kg-showcaselisted

After a competition ends — turn the work into a public repository with two ways in. solution/ for readers who want the result (the final pipeline and the exact commands), journey/ for readers who want to learn from it (how the ideas developed, phase by phase, written from the ledger, with links to the code each experiment ran). Tidies the tree, rebuilds the README, adds a license and figures, audits a public notebook and weights, drafts a Kaggle write-up and tags the final state. Asks before every public step.
TranBaDat2607/claude-code-kaggle-grandmaster · ★ 2 · AI & Automation · score 81
Install: claude install-skill TranBaDat2607/claude-code-kaggle-grandmaster
# /kg-showcase 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). Competition: `$ARGUMENTS` (default: from `.kaggle-gm/competition.json`). Best run after `/kg-postmortem`. The public repository has two ways in, for two readers: - **`solution/`**: the result. The final pipeline end to end, the exact commands that reproduce the finals, the hardware and time. For a reader who only wants the best result. - **`journey/`**: how the ideas developed. Phase by phase: what was tried, what the numbers said, what was kept, the dead ends and why they failed, with a link to the code each experiment ran from. For a reader who wants to learn from it. Most winners' repositories show only the first; the second is where people learn the most. The README is the landing page that sends each reader to theirs. Nothing in history is rewritten: the tree at the end of the competition stays one tag away (`<slug>-workbench`). What goes public stays public: a notebook, dataset or repo can be forked, cached or indexed within minutes. Prepare everything locally and show the user exactly what will become public. Then ask before each public step: making a notebook or dataset public, pushing a branch, a tag or the snapshot refs, opening a PR, changing the repo's visibility. Never rewrite history, forc