The autonomous build contract, out of the box — "/brain-build " activates the disciplined hands-off build power users used to hand-write a standing prompt for. Use when the user says "/brain-build", "brain build", "build this autonomously", "build this hands-off", "loop until it's done", "don't ask me, just build it", or asks for an unattended/self-grading build. Phase-gated per rUv's SPARC, self-verified and self-graded /100 against a per-phase rubric (below 95 → fix and regrade, max 5 iterations), cost-tier routed with printed receipts, crash-resumable via checkpoints, questions batched into one list — the user writes the goal, not the contract.
EnglishMetaprompting assistant — "/brain-prompt " turns a rough ask into "the right prompt": a complete, tuned master prompt with SPARC phases, per-phase rubrics, standing rules, and cost guardrails, ready to paste or run. Use when the user says "/brain-prompt", "brain prompt", "write me the right prompt for this", "turn this idea into a proper prompt", "metaprompt this", "what should I actually ask for", or hands over a vague one-liner they want expanded into a disciplined build brief. Ends by offering to execute the produced prompt with /brain-build semantics.
EnglishScore ANY repository 0-100 across 8 dimensions using the exact evidence-or-it-didn't-happen scorecard RuvNet-Brain applies to itself. Use when the user says "score this repo", "score my repo", "scorecard", "brain-score", "how good is this codebase", "rate this project", "audit quality", or asks for an honest 0-100 quality assessment of a repository. Every deduction must cite evidence from the actual repo; a known architectural flaw caps its dimension at ≤70; a "what I did NOT test" section is mandatory; all scores are out of 100, never out of 10.
EnglishUse whenever a task involves the RuvNet / rUv ecosystem (Ruflo, RuVector/RVF, AgentDB, RuLake, RuView, agentic-flow, agenticow, SAFLA, QuDAG, DAA, ruv-fann, FACT, SynthLang, SPARC, or any of rUv's 20+ repos) — OR whenever you are asked to build, implement, add, refactor, enhance, or fix ANYTHING, in any repo, on any stack. Grounds every RuvNet capability claim in real source via searchruvnet before asserting, actively considers the FULL toolkit (not just the 2-3 most-cited tools) for whichever one or two would genuinely help THIS project, and TAKES THE LEAD the Ruv way on every build regardless of stack — proposes the right architecture + why, gets one go/no-go, then orchestrates end-to-end (SPARC, parallel swarms, persistent memory, QA gates, proof) instead of acting like a passive answer-bot.
EnglishIncludes Brain Build, Brain Prompt, Brain Score, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Brain Build
The autonomous build contract, out of the box — "/brain-build " activates the disciplined hands-off build power users used to hand-write a standing prompt for. Use when the user says "/brain-build", "brain build", "build this autonomously", "build this hands-off", "loop until it's done", "don't ask me, just build it", or asks for an unattended/self-grading build. Phase-gated per rUv's SPARC, self-verified and self-graded /100 against a per-phase rubric (below 95 → fix and regrade, max 5 iterations), cost-tier routed with printed receipts, crash-resumable via checkpoints, questions batched into one list — the user writes the goal, not the contract.
Brain Prompt
Metaprompting assistant — "/brain-prompt " turns a rough ask into "the right prompt": a complete, tuned master prompt with SPARC phases, per-phase rubrics, standing rules, and cost guardrails, ready to paste or run. Use when the user says "/brain-prompt", "brain prompt", "write me the right prompt for this", "turn this idea into a proper prompt", "metaprompt this", "what should I actually ask for", or hands over a vague one-liner they want expanded into a disciplined build brief. Ends by offering to execute the produced prompt with /brain-build semantics.
Brain Score
Score ANY repository 0-100 across 8 dimensions using the exact evidence-or-it-didn't-happen scorecard RuvNet-Brain applies to itself. Use when the user says "score this repo", "score my repo", "scorecard", "brain-score", "how good is this codebase", "rate this project", "audit quality", or asks for an honest 0-100 quality assessment of a repository. Every deduction must cite evidence from the actual repo; a known architectural flaw caps its dimension at ≤70; a "what I did NOT test" section is mandatory; all scores are out of 100, never out of 10.
Ruvnet Brain
Use whenever a task involves the RuvNet / rUv ecosystem (Ruflo, RuVector/RVF, AgentDB, RuLake, RuView, agentic-flow, agenticow, SAFLA, QuDAG, DAA, ruv-fann, FACT, SynthLang, SPARC, or any of rUv's 20+ repos) — OR whenever you are asked to build, implement, add, refactor, enhance, or fix ANYTHING, in any repo, on any stack. Grounds every RuvNet capability claim in real source via searchruvnet before asserting, actively considers the FULL toolkit (not just the 2-3 most-cited tools) for whichever one or two would genuinely help THIS project, and TAKES THE LEAD the Ruv way on every build regardless of stack — proposes the right architecture + why, gets one go/no-go, then orchestrates end-to-end (SPARC, parallel swarms, persistent memory, QA gates, proof) instead of acting like a passive answer-bot.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Brain Build skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.