← ClaudeAtlas

mad-science-setuplisted

Set up a repository for the mad-science data science skills: experiment tracker folder, domain glossary, agent instructions block and .env.example. Run once per repo before the other skills, or when the user says 'set up mad-science' or 'configure this repo for experiments'.
samuhs/mad-science · ★ 3 · AI & Automation · score 80
Install: claude install-skill samuhs/mad-science
## Setup Mad Science Skills 1. Explore Look at the current repo to understand its starting state. Read whatever exists; don't assume: - git remote -v and .git/config: is this a GitHub repo? Which one? - AGENTS.md and CLAUDE.md at the repo root: does either exist? Is there already an ## Agent skills section in either? - GLOSSARY.md and GLOSSARY-MAP.md at the repo root - Monorepo signals: a pnpm-workspace.yaml, a workspaces field in package.json, or a populated packages/* with its own src/. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo. 2. Show the Finds and Ask Summarize what's present and what's missing. Then take the sections in order. One section, one answer, then the next. #### Section A: Experiment tracker: The experiment tracker lives in this repo at docs/experiments-pipeline. #### Section B: Domain docs: Default to single-context (one GLOSSARY.md at the repo root). This fits almost every repo; write it without asking. Offer multi-context (a root GLOSSARY-MAP.md pointing to per-context GLOSSARY.md files) only when exploration found monorepo signals. Then confirm which layout they want. 3. Confirm and edit Show the user a draft of: - The ## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules) 4. Write Pick the file to edit: - If CLAUDE.md exists, edit it. - Else if AGENTS.md exists, edit it. - If neither exists, ask