neo4j-snowflake-graph-analytics-skill

Run Neo4j graph algorithms on Snowflake tables via SQL CALL procedures.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/cardox6/steuer-graph --skill neo4j-snowflake-graph-analytics-skill-cardox6
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neo4j-snowflake-graph-analytics-skill
Source: https://github.com/cardox6/steuer-graph/tree/main/.agents/skills/neo4j-snowflake-graph-analytics-skill
Command: npx skills add https://github.com/cardox6/steuer-graph --skill neo4j-snowflake-graph-analytics-skill-cardox6

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running graph algorithms normally requires exporting data out of Snowflake into a separate graph database. This Skill guides an AI agent through using the Neo4j Graph Analytics Snowflake Native App so algorithms like PageRank, Louvain, and Node2Vec execute directly inside Snowflake, with results written back as Snowflake tables. ## Core Features & Use Cases - End-to-end workflow guidance: Covers the full explore → prepare projection views → project-compute-write → inspect flow, including the strict view and column casting rules the graph engine requires. - Full algorithm catalog: Exact SQL CALL syntax and parameters for community detection, centrality, pathfinding, similarity, embeddings, and GraphSAGE graph ML procedures. - Privilege and auth setup: Step-by-step role grants for both app-identity mode and execute-as-user mode with programmatic access tokens, secrets, and caller grants. - Use Case: A data engineer wants to detect fraud rings in a Snowflake transactions table. The Skill instructs the agent to create node and relationship views with properly cast NODEID columns, run Louvain via a single CALL, and join results back to source tables for readable account names. ## Quick Start Ask the agent to run the WCC community detection algorithm on your Snowflake tables using Neo4j Graph Analytics and write the component assignments to an output table.

Frequently Asked Questions about neo4j-snowflake-graph-analytics-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run graph algorithms on Snowflake tables?▼

Install the Neo4j Graph Analytics Native App from the Snowflake Marketplace, create projection views exposing NODEID, SOURCENODEID, and TARGETNODEID columns, then call algorithms like Neo4j_Graph_Analytics.graph.page_rank with a compute pool and JSON config. Results are written back to Snowflake output tables.

What graph algorithms are available in Neo4j Graph Analytics for Snowflake?▼

Available algorithms include WCC, Louvain, Leiden, Label Propagation, K-Means, Triangle Count, PageRank, Article Rank, Betweenness, Degree, Dijkstra, Delta-Stepping, BFS, Yen's, Max Flow, Node Similarity, KNN, FastRP, Node2Vec, HashGNN, and GraphSAGE training and prediction procedures.

Why does my projection fail with a column type error?▼

The graph engine only accepts BIGINT, DOUBLE, ARRAY, and VECTOR node properties, and only BIGINT, DOUBLE, or INT relationship properties. Snowflake views inherit source column types, so every property column must be explicitly cast, and VARCHAR or VARIANT columns must be dropped.

Does Neo4j Graph Analytics for Snowflake support Cypher queries?▼

No, this app only runs graph algorithms via SQL CALL procedures and does not support Cypher or Neo4j DBMS queries. For Cypher workloads use a Neo4j database skill instead, and for Aura Graph Analytics or self-managed GDS use their respective skills.

What is the difference between app-identity and execute-as-user modes?▼

App-identity mode runs all jobs as the application using direct grants and is the default. Execute-as-user mode runs jobs as the calling user with a programmatic access token, registered role, and caller grants, giving per-user attribution in query history at the cost of more setup.

Why do I get insufficient privileges errors when running an algorithm?▼

The app needs SELECT on your source tables and views plus CREATE TABLE on the output schema, granted via a database role in app-identity mode or caller grants in execute-as-user mode. In execute-as-user mode there are no FUTURE caller grants, so re-grant after creating new views.