mehdiforoozandeh

crux-cockpit

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 (hands the user the exact `ssh -L` tunnel command). Use when a crux user wants to see their vault in a browser. Triggers: "open the cockpit", "launch the crux GUI", "show me the tree in a browser", "serve the vault", "is the cockpit running", "stop the cockpit", "restart the cockpit", crux gui, crux cockpit.

crux-wiki

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 supply the reading and synthesis. One-way by design: literature → wiki → informs the tree; a project's own findings never enter the wiki. Use when a crux user wants a project-relevant literature base. Triggers: "ingest this paper", "add to the wiki", "what does the literature say", "compile a wiki", "lint the wiki", literature review, prior work / SOTA / baselines for a crux project, crux wiki, LLM wiki.

crux

An agentic research companion — a scientific-method lab notebook for navigating large research programs. 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 rolls results up into per-question answers, trips a human review gate, and regenerates an Obsidian-graphable META + experiments registry. Use when the user wants to run a research program rigorously: open/track research questions, design experiments as problem-statement → hypothesis → verifiables → findings, synthesize results, and update the open questions. Triggers: crux, "open a research question", "lab notebook", "hypothesis/experiment tracking", "design an experiment", "what should we try next", "research notebook", scientific method, meta-questions, Obsidian research vault.

evolve-crux

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 — adding to the engine/CLI/skill, picking up a ROADMAP epic (UI, wiki, marketing), or fixing an engine bug. Triggers: "evolve crux", "add a feature to crux", "crux keeps <doing X>", "improve crux", "contribute to crux", "send a crux PR", crux roadmap, wiki/GUI/autoresearch for crux.