neo4j-labs

Run memory-grounded multiagent orchestration with Meta Knowledge Graph in Codex. Use when the user asks to execute a task through MKG, recall prior learnings first, route memory into subagents, verify phases, and capture durable learnings or decisions.

Read-only Meta Knowledge Graph memory lookup for Codex. Use to fetch and summarize relevant project-scoped and user-scoped Learning or Decision context from Neo4j before planning, reviewing, or orchestrating work.

Onboard or check a Meta Knowledge Graph session in Codex. Use when the user asks to start MKG, verify mounted MKG MCP tools, inspect graph state, choose between the RoadFlex sales demo and a custom persona, or run the Codex equivalent of the Claude Code /mkg-start command.

Set up or verify the MKG RoadFlex sales-agent demo in Codex. Use when the user asks for the sales demo, RoadFlex, demo seeding, Neo4j/BigQuery/Neocarta/Diffbot setup, or the Codex equivalent of the Claude Code sales_agent_demo command.

Brand identity guidelines for Neo4j Labs projects. Use when creating documentation, README files, presentations, diagrams, or marketing materials for Neo4j Labs projects. Defines visual identity, tone, messaging, and lifecycle badges that differentiate Labs from official Neo4j products while maintaining brand connection.

Ensure consistency with Neo4j brand guidelines, Needle design system, and Cypher code style conventions. Use when creating Neo4j documentation, diagrams, presentations, Cypher queries, code examples, or any content that should align with Neo4j's visual identity and coding standards. Reference https://neo4j.design for the Needle design system.

Generate Excalidraw JSON format diagrams for documentation, architecture diagrams, flowcharts, entity relationships, and visual explanations. Use when users request Excalidraw diagrams, .excalidraw files, visual diagrams for docs, architecture visualizations, flowcharts, or when converting ASCII art/placeholder diagrams to proper Excalidraw format.

Neo4j CLI. Runs and pipes Cypher, introspects the schema, generates a data model, and embeds text inline as a query parameter. Discovers and loads example datasets from GitHub repos into local Docker, Neo4j Desktop, or a new Aura instance. Manages local Neo4j Docker containers and Neo4j Desktop DBMSs; Aura instances, projects, and Agents; and Aura, Neo4j connection (dbms), and embedding-provider credentials. Installs, removes, and refreshes agent skills, and self-updates the binary. Skip for Cypher syntax help, Neo4j drivers, Kubernetes, Neo4j Browser, or other databases.

Strict maintainability review — abstraction quality, file size, spaghetti growth. Use for a stellar code quality review, deep quality audit, or harsh maintainability review.

Fixture CLI for golden-file tests. Trigger when render code changes.

Scaffold, wire, and verify a neocarta CLI command that wraps a source/format connector (the `neocarta <source> <verb>` integration that follows building the library connector). Use when asked to add/expose/wire a connector into the CLI, add a `neocarta <source>` subcommand, or check a connector command against the CLI contract. Connectors only — enrichment/embedding and MCP-tool CLI commands are separate skills.

Scaffold, build, and verify a neocarta source or format connector against the connector contract. Use when asked to add/create/scaffold/write a new connector (BigQuery, Dataplex, query log, CSV, OSI, etc.), port a data source into neocarta, or check that a connector conforms to the standard.

Explicitly use $nams:workspace use <workspace-id-or-name> to select the NAMS workspace for the current Codex session after a NAMS workspace ambiguity notice.

Explicitly use $nams:workspace use <workspace-id-or-name> to select the NAMS workspace for the current Codex session after a NAMS workspace ambiguity notice.

Comprehensive guide for developing a Terraform provider in Go against the Neo4j Aura API, using the modern terraform-plugin-framework. Use this skill whenever the user is writing, reviewing, structuring, testing, or debugging any part of a Terraform provider codebase — including resource/data source definitions, schema design, CRUD operations, error handling, import support, state upgrades, acceptance testing, and documentation. Trigger on any mention of "terraform provider", "plugin framework", "resource schema", "data source", "acceptance test", "tfproviderlint", "terraform import", or "state upgrade" in the context of provider development. Also trigger when reviewing Go code that imports terraform-plugin-framework packages.