helix-query-authoring
Helix Query Authoring
Write Helix Rust DSL queries in a way that is schema-aware, explicit, and easy for agents to reason about.
When To Use
Use this skill when the task is to:
- write a new Helix query in Rust
- revise an existing Helix Rust DSL route
- add a stored query for deployment
- choose between
read_batch()andwrite_batch() - add traversal, projection, pagination, BM25 search, or vector search to an existing query
Do not use this skill as the main guide for inline POST /v1/query payloads. Use the dynamic-query skill for that.
First Steps
Before writing any query code:
More from helixdb/skills
helix-query-json-dynamic
Build and validate HelixDB dynamic inline-query requests for POST /v1/query. Use when the task involves dynamic queries, inline query JSON, the inline AST (steps, predicates, expressions, projections), parameter_types, DateTime coercion, query warming, or debugging a request body sent directly to the Helix gateway. See REFERENCE.md for every AST variant and EXAMPLES.md for copy-pasteable payloads.
13helix-query-optimize
Review and improve HelixDB query performance and query shape. Use when the task is to optimize a slow Helix query, improve anchor choice, tighten index usage, reduce traversal breadth, slim projections, fix BM25 or vector search scope, or decide between stored and dynamic routes.
10helix-query-from-gremlin
Translate Gremlin and TinkerPop-style traversals into HelixDB Rust DSL stored queries. Use when the input contains Gremlin, TinkerPop, g.V, g.E, hasLabel, has, out, in, both, outE, inE, repeat, emit, dedup, valueMap, count, range, or limit and the goal is to produce an equivalent Helix Rust query.
9helix-query-from-cypher
Translate Cypher and Neo4j-style queries into HelixDB Rust DSL stored queries. Use when the input contains Cypher, Neo4j, MATCH, OPTIONAL MATCH, WHERE, RETURN, ORDER BY, LIMIT, DISTINCT, MERGE, CASE, UNWIND, FOREACH, DETACH DELETE, IS NULL, or variable-length path patterns and the goal is to produce an equivalent Helix Rust query.
9