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, and exact SQL CALL syntax. 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.

91

1.65x
Quality

88%

Does it follow best practices?

Impact

99%

1.65x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a high-quality, highly actionable skill that provides a clear end-to-end workflow for running Neo4j graph algorithms in Snowflake. Its greatest strengths are the executable SQL examples at every step, the detailed casting rules table, and the comprehensive troubleshooting section. The main weakness is that the document is quite long and could benefit from splitting reference-heavy sections (algorithm tables, privilege setup, installation) into separate files for better progressive disclosure.

Suggestions

Move the algorithm tables and detailed privilege setup SQL into separate referenced files (e.g., references/algorithms.md already referenced, plus references/setup.md) to reduce the main skill's length and improve progressive disclosure.

Ensure the referenced 'references/algorithms.md' file actually exists in the bundle, as it's currently unverifiable.

DimensionReasoningScore

Conciseness

The skill is generally well-written and avoids explaining basic concepts Claude knows, but it's quite long (~400+ lines) with some sections that could be tightened. The algorithm tables are comprehensive but borderline reference material that could live in a separate file. The casting rules table and orientation guidance are valuable and earn their place, but some prose (e.g., 'This is the step that matters most', 'This is the flow that works') is slightly padded.

2 / 3

Actionability

Excellent actionability throughout — executable SQL examples for every step (DDL inspection, view creation, CALL syntax, result joining), explicit casting rules with exact syntax, complete privilege setup scripts, and concrete naming conventions. The examples are copy-paste ready with clear placeholder conventions.

3 / 3

Workflow Clarity

The 4-step end-to-end flow is clearly sequenced with explicit validation points. The skill warns against skipping data preparation, includes a troubleshooting table for common failure modes, provides a checklist at the end, and the casting rules table serves as a validation reference. The 'lowest-common-denominator policy' for column inclusion is a thoughtful safety guardrail.

3 / 3

Progressive Disclosure

The skill references 'references/algorithms.md' for detailed algorithm parameters, which is good progressive disclosure, but no bundle files were provided to verify this exists. The main file is quite long and the algorithm tables, installation instructions, and privilege setup could arguably be split into separate reference files. The external doc links are well-organized in the Further Reading section.

2 / 3

Total

10

/

12

Passed

Description

100%

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

This is an excellent skill description that hits all dimensions strongly. It provides specific algorithms and workflow steps, includes natural trigger terms users would use, explicitly states both what it does and when to use it, and goes above and beyond on distinctiveness by explicitly listing three related skills it should NOT be confused with. The description is comprehensive yet focused, using third person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and algorithms (PageRank, Louvain, WCC, Dijkstra, KNN, Node2Vec, FastRP, GraphSAGE) and describes the workflow (explore → prepare projection views → project-compute-write flow, view/column type rules, exact SQL CALL syntax).

3 / 3

Completeness

Clearly answers both 'what' (run graph analytics algorithms in Snowflake, covers projection views, SQL CALL syntax, column type rules) and 'when' (explicit 'Use when running graph algorithms against Snowflake tables via the Neo4j Snowflake Native App'). Also explicitly states what it does NOT cover with redirects to other skills.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'Neo4j', 'graph algorithms', 'Snowflake', 'GDS Snowflake', 'graph algorithms in Snowflake', 'Neo4j Graph Analytics', 'PageRank', 'Louvain', plus specific algorithm names users would mention. These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinctive — explicitly delineates boundaries against three related skills (neo4j-cypher-skill, neo4j-aura-graph-analytics-skill, neo4j-gds-skill) with 'Does NOT cover' clauses, making it very clear when this skill should and should not be selected.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.