CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-vector-index-skill

Create and manage Neo4j vector indexes, run vector similarity search (ANN/kNN), store embeddings on nodes or relationships, use SEARCH clause (Neo4j 2026.01+, preferred) or db.index.vector.queryNodes() procedure (deprecated 2026.04, still works on 2025.x), configure HNSW and quantization options, pick similarity function and embedding provider dimensions, and batch-update embeddings. Use when tasks involve CREATE VECTOR INDEX, vector.dimensions, cosine/euclidean search, embedding ingestion pipelines, semantic or structural nearest-neighbor lookup, or hybrid search (vector + fulltext, multiple vector sources, or graph-derived scores). Does NOT handle GraphRAG retrieval_query graph traversal — use neo4j-graphrag-skill. Does NOT handle fulltext-only/keyword-only search — use neo4j-cypher-skill. Does NOT compute GDS graph embeddings (FastRP, Node2Vec) — use neo4j-gds-skill.

74

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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, comprehensive skill that provides excellent actionable guidance for Neo4j vector index operations. Its main strengths are the fully executable Cypher/Python examples, clear multi-step workflow with validation checkpoints, and well-organized progressive disclosure. The primary weakness is moderate redundancy across sections (similarity function guidance repeated, gotchas partially duplicating common errors, and when-to-use sections restating the YAML description), which could be tightened to save tokens.

DimensionReasoningScore

Conciseness

The skill is comprehensive and mostly efficient, but includes some redundancy — the 'When to Use' / 'When NOT to Use' sections overlap with what the YAML description already covers, the similarity function guidance is repeated across multiple sections (Step 1 table, Extended Guidance section), and the Gotchas table partially duplicates the Common Errors table. Some sections like the extended similarity function guidance explain concepts Claude would know (e.g., what cosine vs euclidean means). However, most content earns its place with specific Cypher syntax and concrete parameters.

2 / 3

Actionability

Excellent actionability throughout — every step includes fully executable Cypher queries and Python code that are copy-paste ready. The index creation, polling, ingestion, and search patterns all have concrete, parameterized examples with specific model dimensions, provider names, and batch sizes. The embedding provider quick-reference table with exact dimension counts is highly actionable.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (Pre-flight → Create Index → Wait for ONLINE → Ingest → Search → Combine → Hybrid) with explicit validation checkpoints: polling for ONLINE state before querying, dimension assertion before ingest, sanity check queries after index creation, and a shell polling script. The checklist at the end reinforces the critical ordering constraints. Error recovery paths are documented in the Common Errors and Gotchas tables.

3 / 3

Progressive Disclosure

The skill appropriately keeps core workflow inline while deferring hybrid search details to a referenced file (references/hybrid-search.md), linking to external docs for deep dives, and cross-referencing related skills (neo4j-graphrag-skill, neo4j-genai-plugin-skill, neo4j-document-import-skill). References are one level deep and clearly signaled with 'Load on demand' framing. The content is well-organized with clear section headers and tables.

3 / 3

Total

11

/

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 excels across all dimensions. It provides highly specific capabilities, rich trigger terms that match natural user language, explicit 'Use when' guidance, and clear boundary definitions with related skills. The 'Does NOT handle' clauses with redirects to alternative skills are a particularly strong feature for disambiguation in a multi-skill environment.

DimensionReasoningScore

Specificity

Lists numerous specific concrete actions: create/manage vector indexes, run vector similarity search (ANN/kNN), store embeddings on nodes/relationships, use SEARCH clause, configure HNSW and quantization options, pick similarity function, batch-update embeddings. Highly detailed and actionable.

3 / 3

Completeness

Clearly answers both 'what' (create/manage vector indexes, run similarity search, store embeddings, configure HNSW, etc.) and 'when' (explicit 'Use when' clause listing specific trigger scenarios). Additionally includes explicit 'Does NOT handle' boundaries with redirects to other skills, which further strengthens the 'when' guidance.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'CREATE VECTOR INDEX', 'vector.dimensions', 'cosine/euclidean search', 'embedding ingestion', 'semantic nearest-neighbor lookup', 'hybrid search', 'kNN', 'ANN', 'HNSW', 'quantization'. These are terms a user working with Neo4j vector search would naturally use.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinctive — explicitly delineates boundaries with three related skills (neo4j-graphrag-skill, neo4j-cypher-skill, neo4j-gds-skill) using 'Does NOT handle' clauses. This makes it very clear when this skill should and should not be selected, minimizing conflict risk.

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.