helix-query-json-dynamic
Helix Dynamic Query JSON
Use this skill for inline dynamic query requests sent directly to POST /v1/query.
The inline query body is a JSON serialization of the Rust DSL AST. Every variant an agent can send is documented in the companion files. If you are writing anything beyond a trivial read, open REFERENCE.md first — do not guess variant names or field shapes.
Reference Files
REFERENCE.md— complete AST variant catalog (everyStep,Predicate,Expr,PropertyValue,IndexSpec,RepeatConfig,BatchCondition, envelope field). Use when writing a non-trivial request.EXAMPLES.md— working end-to-end JSON bodies: reads, writes, vector/text search,Repeat,Choose,Coalesce,Union, aggregations, upserts,ForEach, index management, warming. Copy the closest scenario as a starting point.
When To Use
Use this skill when the task is to:
- build a dynamic Helix request body
- debug a failing
POST /v1/querycall - add
parameter_typesto a dynamic request - send
DateTimeor typed-array parameters correctly
More from helixdb/skills
helix-query-authoring
Write and revise HelixDB Rust DSL stored queries from scratch. Use when the task is to add, update, or review a Helix query built with read_batch, write_batch, traversal builders, projections, indexes, BM25 text search, or vector search. Inspect local labels, edges, properties, and existing query patterns before inventing new code. See REFERENCE.md for the full builder catalog and EXAMPLES.md for end-to-end patterns.
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