CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-snowflake-graph-analytics-skill

Run Neo4j Graph Analytics algorithms (PageRank, Louvain, WCC, Dijkstra, KNN, Node2Vec, FastRP, GraphSAGE) directly inside Snowflake without moving data. Use when running graph algorithms against Snowflake tables via the Neo4j Snowflake Native App ("GDS Snowflake", "graph algorithms in Snowflake", "Neo4j Graph Analytics"). Covers the explore → prepare projection views → project-compute-write flow, the strict view/column type rules the graph engine requires, exact SQL CALL syntax, and privilege setup in both modes — app-identity grants and execute-as-user / per-user PAT auth (programmatic access token, set_enable_custom_credentials, register_user_role, caller grants). Does NOT cover Cypher or Neo4j DBMS queries — use neo4j-cypher-skill. Does NOT cover Aura Graph Analytics — use neo4j-aura-graph-analytics-skill. Does NOT cover self-managed GDS — use neo4j-gds-skill.

94

1.70x
Quality

94%

Does it follow best practices?

Impact

94%

1.70x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable guide: executable SQL throughout, a clearly sequenced workflow with validation checkpoints and error-recovery feedback loops, and a sensible split of the verbose parameter reference into a single one-level-deep file. The only mild weakness is length — some explanatory prose could be tightened to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and information-rich — rules, tables, and executable SQL dominate with minimal padding, and it assumes Claude's competence about Snowflake/SQL/graph concepts. A few explanatory prose passages (e.g., the orientation rationale and some privilege-mode narrative) could be trimmed slightly without losing value, keeping it just below a 5.

4 / 5

Actionability

Provides copy-paste-ready SQL CALL examples with full project/compute/write config, exact casting rules, real procedure names, and complete privilege-grant scripts covering both auth modes plus rotation/rollback. Placeholders like <user_name> are appropriately templated, and common cases are covered.

5 / 5

Workflow Clarity

A clear 4-step sequence (Explore → Prepare projection views → Project-Compute-Write → Inspect) is explicitly sequenced with a STOP checkpoint for collecting the PAT secret, a Checklist, and a detailed Troubleshooting table mapping errors to fixes that serves as error-recovery feedback loops for these batch/write operations.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview with algorithm tables and the core flow, while the bulk per-algorithm compute/write parameter reference is correctly split into the one-level-deep references/algorithms.md, explicitly signaled with a link. The body is fairly long with auth-mode SQL and algorithm notes inlined, but that is appropriate core content rather than material that clearly belongs in a separate file, so it is just shy of a 5.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-disambiguated: it names concrete algorithms and actions, gives explicit 'Use when' triggers with natural synonyms, and draws clear boundaries against related Neo4j skills. It uses third-person voice throughout with no padding.

DimensionReasoningScore

Specificity

Names concrete algorithms (PageRank, Louvain, WCC, Dijkstra, KNN, Node2Vec, FastRP, GraphSAGE) and lists multiple specific actions — running algorithms in Snowflake without moving data, the explore→prepare→project-compute-write flow, strict type rules, exact SQL CALL syntax, and privilege setup — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (run graph algorithms inside Snowflake without moving data, the flow, type rules, CALL syntax, privilege setup) and 'when' ('Use when running graph algorithms against Snowflake tables via the Neo4j Snowflake Native App'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('graph algorithms in Snowflake', 'GDS Snowflake', 'Neo4j Graph Analytics', 'Snowflake tables', 'Neo4j Snowflake Native App') with synonyms in quotes, covering the common ways a user would request this skill.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (graph algorithms in Snowflake via the Native App) and explicitly disambiguates against three sibling skills via 'Does NOT cover' clauses, minimizing the chance of triggering for the wrong skill.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (524 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
neo4j-contrib/neo4j-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.