aj-kg-query

Query a Neo4j knowledge graph for AJ microkernel platform structure.

40|39|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/Architekt-Jutra/architekt-jutra-code --skill aj-kg-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aj-kg-query
Source: https://github.com/Architekt-Jutra/architekt-jutra-code/tree/main/.claude/skills/aj-kg-query
Command: npx skills add https://github.com/Architekt-Jutra/architekt-jutra-code --skill aj-kg-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the tedious manual work of grepping through source code to find structural facts about the AJ microkernel platform, saving developers significant time when exploring platform architecture, plugin wiring, or endpoint mappings.

Core Features & Use Cases

  • Platform Structure Queries: Retrieve details about host modules, domain entities, repositories, and REST endpoints without reading Java or TypeScript source files.
  • Plugin & Extension Point Analysis: Get information on registered plugins, their manifests, exposed extension points, declared filters, and data storage strategies.
  • Feature Traceability: Trace user-facing features from frontend pages down to backend actions and persistent entities for impact analysis. For example, you can use this Skill to list all endpoints in the product module, see which plugins extend the product detail page, or identify what storage strategy the warehouse plugin uses.

Quick Start

Ask the AJ knowledge graph query skill to list all REST endpoints exposed by the warehouse plugin.

Frequently Asked Questions about aj-kg-query

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

FAQPage Schema
How do I find REST endpoints in a microkernel platform without reading source code?

To find REST endpoints without reading source code, query the platform's knowledge graph. This Skill resolves structural and wiring queries against a seeded Neo4j database, returning endpoint mappings and host module details directly.

How can I trace user-facing features from frontend pages to backend actions?

Feature traceability is achieved by querying the platform knowledge graph. It maps end-to-end feature paths from frontend pages down to backend actions and persistent entities, enabling accurate impact analysis without manual code inspection.

Does this knowledge graph query approach work for analyzing plugin architecture and extension points?

Yes, the knowledge graph query approach works for plugin architecture analysis. It retrieves details about registered plugins, exposed extension points, declared filters, and data storage strategies by executing Cypher queries against the Neo4j instance data.

Can I retrieve domain entities and host bridge operations using a knowledge graph?

You can retrieve domain entities and host bridge operations using a knowledge graph. This Skill applies Cypher queries to the Neo4j knowledge graph modeling the platform's ontology to return accurate structural facts for platform analysis.

What is the best way to list all endpoints exposed by a specific plugin like a warehouse module?

The best way to list endpoints exposed by a specific plugin is querying the knowledge graph. By leveraging the neo4j-aj-kb MCP server, the Skill executes targeted Cypher queries to return structured endpoint mappings for the requested module.

Do I need a Neo4j database to query microkernel platform structure and wiring?

Yes, a Neo4j database is required to query microkernel platform structure and wiring. The Skill leverages the neo4j-aj-kb MCP server to execute Cypher queries against a seeded graph modeling the platform's ontology and instance data.