nacl-sa-validate

Run read-only Cypher checks to detect consistency issues in Neo4j SA/BA graphs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and reports inconsistencies and gaps in the specification graph by running read-only Cypher validations against the Neo4j model. It provides a gate to ensure data integrity and cross-layer traceability before moving forward in development.

Core Features & Use Cases

  • L1-L6 validation: data consistency, model connectivity, requirement completeness, form-domain traceability, UC-form validation, and cross-module consistency.
  • XL6-XL9 cross-layer checks: BA-to-SA coverage, entity, role, and rule coverage, plus cross-workflow traceability.
  • Non-destructive checks: all validations are read-only and report findings without modifying the graph.

Quick Start

Invoke the validation workflow to check the entire specification graph and generate a report.

Frequently Asked Questions about nacl-sa-validate

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

FAQPage Schema
How do I validate specification graph consistency in Neo4j?

To validate specification graph consistency in Neo4j, you run read-only Cypher checks against the populated graph to detect data and model inconsistencies across L1-L6 and XL6-XL9 layers. It ensures cross-layer traceability before development.

Can I run Cypher validation queries without modifying the graph database?

Yes, you can run Cypher validation queries without modifying the graph database. All validations are strictly read-only operations that report findings and detect specification gaps without altering nodes or relationships.

What is cross-layer traceability validation for a specification graph?

Cross-layer traceability validation for a specification graph is the process of checking BA-to-SA coverage, entity, role, and rule coverage, plus cross-workflow traceability using read-only Cypher queries across XL6-XL9 layers.

Do I need a fully populated Neo4j graph to run architecture validation checks?

Yes, you need a fully populated Neo4j graph to run architecture validation checks. The graph must contain nodes for Modules, UseCases, DomainEntities, Requirements, and related relationships to execute the L1-L6 validations.

How to avoid false positives during model connectivity validation in Neo4j?

To avoid false positives during model connectivity validation in Neo4j, the validation process respects mandatory exemption filters. This ensures that read-only consistency checks do not report incorrect gaps in the specification graph.

When should I use graph queries for requirement completeness validation?

You should use graph queries for requirement completeness validation when applying quality gates before development. It checks the full specification graph for data consistency, UC-form validation, and cross-module consistency.