Claude Skills by mehdiforoozandeh

Launch and manage the crux cockpit — the read-only browser GUI over a crux research vault (`crux serve`). This skill runs it beginning to finish: locate the vault, start the server fresh on localhost, verify it actually serves, and hand the user one clickable URL — plus status / stop / restart, and a setup-or-demo path when no vault exists yet. Works wherever the agent runs: local machine, VS Code Remote-SSH (drives the port forward itself via `code --openExternal`), or a plain SSH terminal (...

Write the Requirements Document for a crux node — the design detail that does not fit, and should not fit, inside a 400-word question or hypothesis. An RD is one immutable design document per node, living in `rd/` beside the tree, linked from the node, outside the roll-up: the estimand and its bound, the probe ladder, the negative control, the known distortion that must travel with every result. You do not interview and you do not re-derive — you write up the design that has just been settled...

A literature wiki for a crux research vault — Andrej Karpathy's LLM-wiki pattern applied to a crux project. The PI curates immutable sources under `raw/`; you (the agent) compile them into a persistent, interlinked `wiki/` of background, prior methods, SOTA, baselines, datasets, and definitions, and draw on it to ask sharper questions and design better hypotheses. The crux engine owns the bookkeeping (source hashes, the generated `WIKI.md` index, structural lint via `crux validate`); you supp...

An agentic research companion — a scientific-method lab notebook for a research program. Organize work as a tree of Questions (what we don't know) and falsifiable Hypotheses (testable leaves), each with pre-registered verifiables and findings; a deterministic engine derives verdicts, rolls them up, and trips a human review gate. Use when the user wants to run a research program rigorously: open/track research questions, design experiments as problem-statement → hypothesis → verifiables → find...

Evolve crux itself — add a capability or fix a recurring flaw in the crux tool, end to end: ideate → build → validate → ship. Turns a feature idea or a "crux keeps doing X" annoyance into a signed-off PRD, a tests-first implementation, a hard validation gate (selftest green · stdlib-only · existing vaults still load · version/migration), and a pull request. Works for anyone contributing to crux, not just the maintainer; the maintainer self-merges and cuts releases. Use when working ON crux — ...

Turn one crux anchor node and everything under it into a minimal, professional, self-contained HTML slide deck — the "here's what we found" update a research group gives — where every number on a slide is an address into the vault, not a photocopy of one, and `crux deck --verify` can prove it still matches. Drives the engine's `crux deck` verbs (--json harvest, --verify, --refresh, --lint), fills the shipped template, and runs the refinement loop with the PI. Use when a crux user wants slides...