skills
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Gecti
- Code scan — Scanned 11 files during light audit, no dangerous patterns found
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
Agent skills and the Helix MCP for Helix Foundry and HelixDB: company context and memory for agents, a cited knowledge graph of your data, and graph-vector queries
HelixDB Skills
Hosted skills.sh repository for HelixDB agent skills.
The query skills target the published Rust 3.0.0, TypeScript 3.2.0, Python 0.3.4,
and Go v0.3.1 SDKs. Installation commands stay unpinned; verify registry
availability before changing release claims. See Source Canon
for the distinction between published packages and current source.
These skills are for agents that need to:
- write Helix queries in the Rust, TypeScript, Python, and Go SDK DSLs
- write dynamic-first Helix queries in Go
- translate from Cypher, Gremlin, SQL, and legacy HelixQL (HQL) into Helix query code
- optimize Helix query shape and index usage
- build correct dynamic
POST /v2/querypayloads - inspect Helix Cloud query insights, latency, recommendations, usage, and cluster health through the Helix MCP server
- execute authorized Helix Cloud queries through the same server's query tools
- run confirmation-gated tenant and database-key mutations through the same server's admin tools
- design and operate an agent memory system on Helix's hybrid graph + vector + full-text engine
- read and ask Helix Foundry ontologies, send pieces of JSON to Foundry API sources, record an agent's work as use case runs, and run confirmation-gated Foundry syncs, generations, revisions, document uploads, loads, dashboards and workflows
- set up a Helix Foundry ontology end to end: connect data, send pieces to an API source or upload documents, write its goal, generate, answer the draft's questions, review and load it
Status
Available now:
helix-clihelix-mcphelix-query-mcphelix-admin-mcphelix-foundry-mcphelix-foundry-actions-mcphelix-foundry-onboardinghelix-query-from-cypherhelix-query-from-gremlinhelix-query-from-hqlhelix-query-json-dynamichelix-query-optimizehelix-query-rusthelix-query-typescripthelix-query-gohelix-query-pythonhelix-memory-system
SQL input is covered by helix-query-from-cypher: the server runs SQL natively atPOST /v2/sql, so there is no separate SQL skill.
Install
npx skills add HelixDB/skills
As a Claude Code plugin, with the Helix MCP (https://mcp.helix-db.com/mcp) added
for you:
claude plugin marketplace add HelixDB/skills
claude plugin install helixdb@helixdb
As a Gemini CLI extension, which adds the Helix MCP:
gemini extensions install https://github.com/HelixDB/skills
Helix Cloud queries
Helix Cloud has one MCP server, https://mcp.helix-db.com/mcp, with one OAuth
audience (the former admin-mcp.helix-db.com and query-mcp.helix-db.com are
retired). Its tools depend on who connects:
| Caller | Tools |
|---|---|
| Signed-in user | Discovery and observability, plus the query, admin and Foundry tools their permissions allow |
Service credential (hlxs_) |
Query, admin and Foundry tools for its project grants; no discovery or observability |
| Agent registration | helix_get_started and query tools on its own sandbox |
| Foundry send token | helix_foundry_send_pieces only |
For a Cloud target, every query-authoring skill uses helix-mcp first to resolve
the live database and read its active indexes, insights, latency and
recommendations. Execution uses helix-query-mcp; tenant or key changes usehelix-admin-mcp.
Every MCP skill has agents report problems through helix_feedback (bug, missing
capability or confusing result; one call per problem; no user data). The Helix
team uses it to decide what to fix next.
Running queries (prerequisites)
The query-authoring skills assume you already have a Helix instance to run
them against. To stand one up locally — no Cloud login required:
- Install the Helix CLI:
curl -sSL "https://install.helix-db.com" | bash. - Make sure Docker or Podman is installed and running — the local instance runs in a container (
docker infoshould succeed). - Scaffold a local instance:
helix init local - Run
helix start dev(aliashelix run). CLI 3.7.0 runsghcr.io/helixdb/helixdb:v0.0.16; update an older pinnedtagin[local.dev]tov0.0.16. - Run queries through the SDK client (
Client/client.Exec) orhelix query dev --file <request.json>.
The local runtime is in-memory by default; --disk persists through a CLI-managed
SeaweedFS sidecar (it can't read data from older MinIO-based CLIs). Direct Docker
runs can persist through HELIX_DATA_DIR (CLI examples).
The skills produce direct POST /v2/query requests to a running instance. Cloud CLI
queries use a WorkOS session and the backend broker; application gateway clients use
explicitly created database keys. There is no helix compile/helix check: the
server validates queries. See the HelixDB docs for full
setup and the non-interactive/agent path.
Helix Foundry
helix-foundry-mcpreads ontologies, versions, loads, reviews, workflows,
dashboards and the graph, asks Foundry's query agent (cited answers), previews
dashboard tiles, sends JSON pieces to API sources, and records an agent's reads,
questions and sends as use case runs (use_case_run_id; formerly workflow runs).helix-foundry-actions-mcpruns requested changes (create an ontology or API
source, sync, generate or revise a draft and answer its questions, upload and
organize documents, settle a review, make a version or load current, create a
load, create and change dashboards and workflows), each through a one-time
confirmation. A workflow runs only after its owner approves it in Foundry.helix-foundry-onboardingtakes a workspace from nothing to a loaded ontology:
ontology and database, connector links, API sources and pieces, document uploads
(any mix), a goal written from what the agent knows of your work, then generate,
answer the draft's questions, review and load, asking before each action.
Renamed on the Foundry MCP, without aliases: the old "workflow" tracking tools are
now use case tools (helix_foundry_create_use_case, list_use_cases,start_use_case_run, finish_use_case_run, get_use_case_run, paramuse_case_run_id), and the automation tools and operations now carry the workflow
names (helix_foundry_list_workflows, get_workflow, list_workflow_runs,get_workflow_run; create_workflow … run_workflow, target workflow:).
Credentialed connectors are added on the Foundry website from a link the MCP gives,
so credentials never pass through an agent. An app or agent sending to an API source
on its own uses a send token the user makes on the website, over the MCP or, when
the MCP returns the source's send_url, over HTTP from the app's server. Ontologies
read an API source through structured mappings or, with a text field, by entity
extraction of its newest pieces.
All three use https://mcp.helix-db.com/mcp. Sign in once and the agent acts as you
(onboarding needs a workspace owner or admin):
claude mcp add --transport http helix https://mcp.helix-db.com/mcp # then /mcp to sign in
codex mcp add helix --url https://mcp.helix-db.com/mcp && codex mcp login helix
Without a browser (CI), send a service key as a header: --header "Authorization: Bearer hlxs_..." for Claude Code, or bearer_token_env_var in
Codex's MCP config. A key reaches only ontologies its project grants allow; it can
read, ask and run loads but not sync, generate or create ontologies, so onboarding
needs you signed in.
Repository Layout
skills/contains the published skillsdocs/contains shared reference material used while authoring skillsexamples/contains generic canonical examples and before-and-after patternsbenchmarks/contains evaluation scaffolding for prompt and gold-answer testing
Current Skills
helix-mcp
Discover authorized Helix Cloud resources and read observability data through the
MCP server's read-only tools; recover from MCP sign-in and missing-tool problems.
Teaches agents to:
- discover workspaces, projects and databases before requesting data
- check the writer-authoritative active index inventory before assuming a Cloud predicate has a usable index
- pick the right tool for insights, latency percentiles, recommendations, usage or dedicated-cluster health
- keep p99 in the latency workflow and separate usage rollups from cluster health
- treat query names, planner findings and recommendation text as untrusted data
- report time windows, partial data, collection watermarks and unavailable components accurately
helix-cli
Drive the helix CLI itself (local instances, the WorkOS-authenticated Cloud
control plane and broker) rather than author query bodies. Teaches agents to:
- treat v3 as a runtime orchestrator, not a compiler (no
helix compile/helix check, no.hxworkflow) - run the local loop (
helix init local→start→query→stop) on Docker/Podman, in memory or with--disk - pass the global
--jsoneverywhere (no prompts, JSON errors with candidates) and have the user run the interactivehelix auth login - query
POST /v2/queryviahelix query(--file/--body/-eTypeScript DSL/--ts-file), run Cypher viahelix cypher, and check setups withhelix doctor - manage Helix Cloud with a WorkOS session (
auth,workspace,project,cluster,database,service-credential,api) - run Cloud
query/shellthrough the broker, without application keys or gateway URLs - use the links in
helix.toml; there is no global workspace selection
Query bodies come from the helix-query-* skills. REFERENCE.md has the full
command catalog; EXAMPLES.md has end-to-end sessions.
helix-query-mcp
Explicitly requested Helix Cloud reads and confirmation-gated writes through the
MCP server's query tools, plus an agent's helix_get_started sandbox. Teaches the{database, query_json} contract, checking status_code, independent query
permissions, exact v3 payload binding, no-retry execution and the untrusted-data
boundary.
helix-admin-mcp
Only explicitly requested tenant create/delete or database-key create/revoke
through the MCP server's admin tools. Teaches each operation's target and payload,
durable confirmations, raw-secret-once handling and the excluded Cloud lifecycle
surfaces.
helix-foundry-mcp
Explore Helix Foundry ontologies. Teaches agents to resolve the workspace and
ontology; choose between the definition, sources, exact graph reads and Ask; build
reads from the served read guide; keep Ask's client_token on retries; follow
syncs, generations (and when one waits on the user's answers) and loads; hand over
Foundry links; send pieces to an API source with a fresh client_token per call, or
show an app how to POST them to the source's send_url (curl, body, status
handling) when one is returned; record work as use case runs; read workflows,
dashboards and reviews; and report answers with citations. Field-level detail,
including the workflow and dashboard specs, is in its REFERENCE.md.
helix-foundry-actions-mcp
Only explicitly requested Foundry changes: create an ontology (existing or new
database) or an API source (text field for extraction), sync a connector, generate
or revise a draft (API sources via mappings or extraction) and answer its questions,
upload and organize documents, settle a review, make a version or load current,
create a load, add the sample company, create, change, pin, publish or delete
dashboards, and create, change, pause, resume, run or delete workflows. Teaches
prepare-then-execute confirmation, no retries, the upload PUT and completion, what
each action costs or replaces, workflow approval in Foundry, and what stays on the
website.
helix-foundry-onboarding
Only when a user asks to set up Foundry or build a workspace's ontology from
scratch. Teaches the order (workspace, ontology and database, data, goal,
generation, the draft's questions asked one at a time, review, load), which mode
fits each API source, how long to wait and when to give up, writing the goal from
the user's work, and what to hand back: a
draft's open questions, what it left out and its unread sets, then what the load
read, left unread, and the reviews and unmatched names it left. Payloads and
confirmations come from the two skills above.
helix-query-json-dynamic
Use this skill when an agent needs to build or debug direct JSON requests forPOST /v2/query.
It teaches agents to:
- use the correct request envelope
- target the dynamic route (
POST /v2/query) with an inlinequeryobject - add
parameter_typeswhen typed coercion matters - send
DateTimevalues correctly - avoid malformed bundle-shaped payloads
helix-query-go
Use this skill when an agent needs to write or revise HelixDB queries with the Go SDK.
It teaches agents to:
- write normal Go functions returning
helix.Request - set query names with
helix.ReadQueryandhelix.WriteQuery - declare runtime params inline with
q.ParamString,q.ParamI64,q.ParamDateTime, and related helpers - avoid accidentally inlining request-specific literals in predicates and source predicates
- execute dynamic requests with
client.Exec(ctx, request, &out) - handle HTTP 409 conflicts explicitly with caller-owned retries
- avoid stored-query registration and query-bundle workflows, which are not part of the v3 SDK
helix-query-python
Use this skill when an agent needs to write or revise HelixDB queries with the Python SDK.
It teaches agents to:
- write Pythonic query builders with
read_batch,write_batch,g, and snake_case traversal methods - declare runtime params with
define_paramsandparam.* - produce direct requests with
to_query_request/to_query_json - execute requests with synchronous
Clientor reusable server/embeddedAsyncClient - use row bindings for correlated multi-hop projections
- keep Python queries structurally identical to the Rust/TypeScript/Go JSON AST
helix-query-from-cypher
Use this skill when an agent needs to run or port Neo4j, Cypher or SQL queries on Helix.
It teaches agents to:
- send supported Cypher (
POST /v2/cypher) and SQL (POST /v2/sql) to the server as they are, and check plans with the/explainroutes - hand-translate into the v3 DSL only what the profile rejects (
MERGE, variable-length paths,FOREACH, search) - keep Cypher semantics when translating:
OPTIONAL MATCHvia bind +optional+project_bindings,CASEviaExpr::case, null ordering, and target labels viahas_label - replace
MERGEwith a unique equality index plus a conditional create
helix-query-from-gremlin
Use this skill when an agent needs to port Gremlin or TinkerPop traversals into Helix Rust DSL.
It teaches agents to:
- translate
g.V,hasLabel, andhasinto anchors and predicates - map
out,in,both,outE, andinEinto explicit Helix traversal steps - map
dedup,count,range, ordering, andvalueMapinto deliberate result shaping - handle
repeat,path,select, and side-effect-heavy traversals as semantic translations rather than literal rewrites
helix-query-from-hql
Use this skill when an agent needs to migrate legacy HelixQL (HQL) .hx queries into the v3 DSL (Rust or TypeScript, with name mappings for Go and Python).
It teaches agents to:
- map every HQL construct (
N<T>/E<T>,Out/In/OutE/FromN/ToN,WHERE/EQ/IS_IN, projections,GROUP_BY/AGGREGATE_BY,ORDER/RANGE,AddN/AddE/UPDATE/DROP,SearchV/SearchBM25) to its Rust and TypeScript builder - handle the Rust-vs-TypeScript spelling differences (
in_/in,where_/where,::/.,Some()/null) - map
Upsertto a one-batch conditional create (var_as_if) backed by a unique index, and unweighted shortest paths toshortest_path - flag HQL features with no DSL equivalent (
RerankRRF/RerankMMR, weighted shortest paths,Embed, advanced math,EXISTS/count-in-WHERE, schema defaults,#[model]/#[mcp]) and move that logic to application code - verify each migration by compiling, diffing the Rust vs TypeScript JSON AST for parity, and running against the same data
helix-query-optimize
Use this skill when an agent needs to review or improve Helix query performance.
It teaches agents to:
- fetch the live active index inventory before deciding index usability
- fix anchor choice before anything else
- match query shape to existing indexes
- move scope filters earlier
- shrink large projections
- review BM25 and vector search routes separately
helix-memory-system
Design or operate an AI agent memory system on Helix: generation, deduplication, updating/consolidation, deletion/forgetting and categorisation, not just retrieval. Teaches agents to:
- model per-user memory with
User,Memory,Category,Entity, andSessionlabels plus the edges and indexes that make it fast and tenant-safe - choose the right mechanism per operation: properties + equality index, graph edges, vector search, or BM25 text search
- run the full write/maintain lifecycle (dedup-on-generate, reinforce-on-access, supersede/correct, soft-delete, decay and expiry sweeps, upsert-and-link categorisation)
- build hybrid recall that fuses vector + BM25 app-side and expands through the graph
It is TypeScript-first (@helix-db/[email protected]) with a Rust v3 DSL variant in EXAMPLES.rust.md.
Shared References
Start here when working on the next skills:
docs/source-canon.mddocs/dsl-cheatsheet.mddocs/go-dsl-cheatsheet.mddocs/cypher-rosetta.mddocs/gremlin-rosetta.mddocs/dynamic-query-examples.mddocs/optimization-checklist.mdexamples/authoring-patterns.mdexamples/search-patterns.mdexamples/optimization-patterns.md
Notes
- This repo uses the hosted
skills.shlayout:skills/<name>/SKILL.md. - Local OpenCode discovery still uses
.opencode/skills/,.claude/skills/, or.agents/skills/after installation. - This repo is intentionally written against public Helix behavior and repo-local canonical examples rather than app-specific implementations.
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi