clojurescript-nbb
Write, review, and debug scripts for nbb (babashka/nbb) — ad-hoc ClojureScript scripting on Node.js via SCI. Use this whenever the user mentions nbb, "node babashka", .cljs scripts meant to run with `nbb script.cljs`/`npx nbb`, or wants a quick CLI/automation/serverless script written in ClojureScript instead of Node.js. Also use it for npm interop from nbb (`:require ["pkg" :as x]`, `$default` imports), promise handling with promesa (`p/let`, `p/do!`), first-class macros in nbb scripts, nbb.edn Clojure deps, or the nbb REPL/nREPL. Do NOT use this for shadow-cljs/Closure-compiled CLJS projects, advanced-compilation questions, or browser-optimized builds — nbb has no Closure Compiler stage and a different (smaller) language surface; prefer the general `clojurescript` skill for those.
Works with
This skill's source license couldn't be confirmed as safe to mirror here, so it isn't inlined. View the full skill directly on its source repository.
View on GitHubMore Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
