nacl-core

Standardize Neo4j connections, schema references, and Excalidraw templates for nacl-* skills.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nacl-core
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-core
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared references, templates, and utilities for all nacl-* skills to ensure consistency in Neo4j connections, schema references, ID formats, and Excalidraw standards.

Core Features & Use Cases

  • Shared references, templates, and utilities used across nacl-* skills.
  • Standardized Neo4j MCP usage (read/write/get-schema) and config-driven graph settings.
  • Excalidraw-based board templates and ID conventions for reproducible artifacts.

Quick Start

Initialize your nacl-* project to reuse the graph core references and conventions, then start developing skills with consistent foundations.

Frequently Asked Questions about nacl-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Neo4j connection settings across multiple skills?▼

Standardize Neo4j connections by centralizing configuration resolution through config.yaml. This enforces consistent schema references and MCP usage across all nacl-* skills.

What are Excalidraw board templates for reproducible artifacts?▼

Excalidraw board templates are standardized layouts with defined ID conventions for reproducible artifact generation. They ensure consistent board design across BA, SA, and TL project layers.

How do I enforce consistent ID formats in Neo4j graph skill development?▼

Enforce consistent ID formats by applying shared schema references and centralized templates during graph skill development. This ensures all nacl-* skills generate standardized identifiers and graph structures.

Do I need config.yaml to use Neo4j MCP with these templates?▼

Yes, config.yaml is required for configuration resolution. It drives graph settings and Neo4j MCP connections, ensuring dependent skills operate on a centralized, standardized foundation.

What is the best way to manage shared references for graph-core workflows?▼

Manage shared references by initializing a central utility skill that standardizes Neo4j schemas, Excalidraw templates, and config.yaml settings. This provides a consistent foundation for downstream workflows.

Can I use these conventions for artifact generation across BA, SA, and TL layers?▼

Yes, the conventions explicitly enforce consistent artifact generation across BA, SA, and TL layers. They provide standardized templates and schema references for each architecture level.