nacl-ba-entities

Catalog business entities in Neo4j with attributes, states, and CRUD matrices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catalog business entities in Neo4j: stereotypes, attributes, states, CRUD matrix to enable graph-first BA workflows and traceability.

Core Features & Use Cases

  • Phase-driven entity modeling: COLLECT, FULL, CREATE, and MODIFY phases to build and maintain a consistent BA catalog.
  • Lifecycle modeling: define HAS_STATE and EntityState nodes, TRANSITIONS_TO edges, and compute the CRUD matrix from graph relationships.
  • Graph-based provenance: store entities, attributes, and states as graph nodes with explicit relationships for traceability and governance.

Quick Start

Describe the initial catalog by configuring /nacl-ba-entities to collect entities from your graph and start building the catalog.

Frequently Asked Questions about nacl-ba-entities

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

FAQPage Schema
How do I catalog business entities in Neo4j as a single source of truth for BA workflows?

The Skill catalogs business entities in Neo4j by extracting stereotypes, attributes, states, and CRUD matrices from existing workflow steps. It applies phase-driven modeling and MERGE mutations to maintain a consistent, idempotent entity catalog graph.

What is the best way to model entity lifecycle states and transitions in a Neo4j graph?

Modeling entity lifecycle states in Neo4j involves creating HAS_STATE and EntityState nodes connected by TRANSITIONS_TO edges. This Skill structures these relationships to enable lifecycle tracking and compute CRUD matrices from the graph.

How do I enforce consistent ID conventions for business entity attributes and states in Neo4j?

Enforcing consistent ID conventions for business entities in Neo4j requires structured naming like OBJ-NNN for entities, OBJ-NNN-Axx for attributes, and OBJ-NNN-STxx for states. This Skill automatically applies these per-entity identifiers during catalog generation.

Can I generate a complete BA entity catalog from existing workflow processes in Neo4j?

Yes, you can generate a complete BA entity catalog from existing workflow processes in Neo4j. The Skill operates across COLLECT, FULL, CREATE, and MODIFY phases to build and maintain the catalog directly from your process data.

Does cataloging business entities with this approach maintain idempotency across multiple updates?

Cataloging business entities in Neo4j maintains idempotency across multiple updates by using graph queries with MERGE mutations. This ensures repeated operations update existing nodes without creating duplicates in the entity catalog.

When do I need a graph-based entity catalog for BA traceability instead of a standard document?

You need a graph-based entity catalog for BA traceability when you must store entities, attributes, and states as graph nodes with explicit relationships. This approach provides governance and provenance tracking that static documents cannot match.