What problem does it solve? Writing a GraphQL API on top of a Neo4j graph database requires mastering many library-specific directives, version differences, and security patterns. This Skill guides an agent through the correct @neo4j/graphql v7 (or v5 LTS) syntax so type definitions, relationships, custom resolvers, and authorization rules work on the first attempt. ## Core Features & Use Cases - Schema and Directive Authoring: Write type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher custom resolvers, @id, @timestamp, and @alias, including relationship properties via the Connection API. - Security Configuration: Set up JWT or JWKS-based @authentication and @authorization rules, choosing deliberately between filter (silent hiding) and validate (thrown errors). - OGM and Subscriptions: Use the OGM for trusted server-side programmatic access and enable CDC-backed subscriptions for real-time events. - Use Case: You are wiring Neo4j to Apollo Server and need auto-generated queries and mutations, JWT-secured fields, and a v6-to-v7 migration path with a checklist of common errors like missing @node or mismatched @cypher columnName. ## Quick Start Ask the agent to create a Neo4j-backed GraphQL API with Apollo Server, defining Movie and Person types with an ACTED_IN relationship and JWT-based authorization.