NeuralSkillBuilder
Build consistent, NeuralVault-integrated Claude Code skills.
Ask AI about NeuralSkillBuilder
Powered by Claude Β· Grounded in docs
I know everything about NeuralSkillBuilder. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
π οΈ NeuralSkillBuilder
Build consistent, NeuralVault-integrated Claude Code skills.
Meta-skill for creating, scaffolding, and auditing Claude Code skills β with built-in NeuralVaultCore MCP integration. Based on Skillsmith conventions (MIT), extended for the NeuralVault ecosystem.
π Install
# Global β available in every workspace (recommended)
npx github:getobyte/NeuralSkillBuilder --global
# Local β current project only
npx github:getobyte/NeuralSkillBuilder --local
Then open Claude Code and type /nvc:skill.
π§© Commands
| Command | What it does |
|---|---|
/nvc:skill discover | Guided interview to design a new skill β produces a skill spec |
/nvc:skill scaffold | Generate a compliant skill directory from a spec |
/nvc:skill distill | Transform raw source material into framework chunks |
/nvc:skill audit | Audit skill compliance against syntax specs |
βοΈ How It Works
Claude Code skills are markdown files that give Claude a persona, routing logic, and domain knowledge. NeuralSkillBuilder enforces a consistent structure across all skills using standardized syntax specs.
Four workflows:
1. Discover β 6-phase guided interview covering identity, persona, scope, content architecture, NVC integration, and review. Produces a structured skill spec.
2. Scaffold β Takes a skill spec, generates a complete directory with all files properly structured. Auto-generates frameworks/nvc-tools.md when NVC integration is present.
3. Distill β Transforms raw knowledge (books, courses, notes) into structured framework chunks ready for skill consumption.
4. Audit β Checks existing skills against syntax specs and NVC conventions. Produces a scored compliance report.
π§ NVC Integration (Phase 5)
The discovery workflow includes a dedicated phase for designing how your skill integrates with NeuralVaultCore MCP:
- Which keys does the skill read at session start?
- Which events trigger autonomous NVC writes?
- What namespace convention does the skill use?
- Does the skill respond to
/nvc:initand/nvc:end?
When NVC integration is present, scaffold auto-generates frameworks/nvc-tools.md with all tool signatures, namespace conventions, key conventions, and token efficiency rules.
π Skill File Types
| Type | Purpose | Mutable? |
|---|---|---|
| Entry point | Identity + routing | β |
| Tasks | Guided workflows | β |
| Frameworks | Domain knowledge | β |
| Templates | Output structure | β |
| Context | User / business state | β |
| Checklists | Quality gates | β |
π NeuralVault Ecosystem
| Component | Role |
|---|---|
| π§ NeuralVaultCore | MCP memory server β the brain |
| β‘ NeuralVaultSkill | Session memory automation β /nvc:init + /nvc:end |
| π§Ή NeuralVaultArchivist | Memory consolidation β on-demand cleanup |
| π οΈ NeuralSkillBuilder (you are here) | Skill builder β design, scaffold, audit |
| π NeuralVaultFlow | Dev workflow β brainstorm to deploy |
Credits
Based on Skillsmith by Chris Kahler (MIT License).
Extended for the NeuralVault ecosystem by getobyte.
NeuralSkillBuilder β Cyber-Draco Legacy
Built by getobyte Β· Romania π·π΄
