crux-cockpit
SolidLaunch 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.
Install
Quality Score: 79/100
Skill Content
Details
- Author
- mehdiforoozandeh
- Repository
- mehdiforoozandeh/crux
- Created
- 4 weeks ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
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.
curiosity-engine
Self-improving knowledge wiki with a vault of raw sources. Use when the user mentions 'curiosity engine', 'wiki', 'vault', 'knowledge base', 'ingest', 'iterate', 'refine', 'improve', 'evolve', 'curator', 'lint', or wants to add sources, query accumulated knowledge, check wiki health, or run autonomous improvement. Also triggers on 'add to vault', 'what do I know about', 'improve wiki', 'set up knowledge base', 'new knowledge base', 'run curator'. Use even without explicit naming — if the user wants to file something for later or asks about accumulated knowledge, this is the skill.
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.