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, or semantic nearest-neighbor lookup. Does NOT handle GraphRAG retrieval_query graph traversal — use neo4j-graphrag-skill. Does NOT handle fulltext/keyword indexes (FULLTEXT INDEX, db.index.fulltext) — use neo4j-cypher-skill. Does NOT handle GDS graph embeddings (FastRP, Node2Vec) — use neo4j-gds-skill.
92
88%
Does it follow best practices?
Impact
100%
1.58xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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 with version-aware details, includes rich natural trigger terms, has an explicit 'Use when' clause, and uniquely includes negative boundary definitions that clearly distinguish it from three related Neo4j skills. The description is comprehensive yet focused, serving as a strong example of how to write skill descriptions in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create/manage vector indexes, run vector similarity search (ANN/kNN), store embeddings, use SEARCH clause, configure HNSW and quantization, pick similarity function, batch-update embeddings. Highly detailed with version-specific information. | 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 with specific triggers like CREATE VECTOR INDEX, vector.dimensions, cosine/euclidean search). Additionally includes explicit 'Does NOT handle' boundaries which further clarify when to use vs. not use. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'vector index', 'vector similarity search', 'embeddings', 'cosine/euclidean search', 'CREATE VECTOR INDEX', 'vector.dimensions', 'nearest-neighbor lookup', 'embedding ingestion pipelines', 'ANN/kNN'. These are terms a user working with Neo4j vectors 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) and specifies what each handles instead. The 'Does NOT handle' clauses directly minimize conflict risk with neighboring skills in the Neo4j ecosystem. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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, comprehensive skill with excellent actionability and workflow clarity. Every step includes executable Cypher/Python code, clear validation checkpoints (polling for ONLINE, dimension assertions), and well-organized error recovery tables. The main weakness is length — at 400+ lines with some redundancy between sections (common errors vs extended gotchas, repeated similarity function guidance), it could benefit from splitting reference material into separate files and tightening duplicated content.
Suggestions
Extract the Embedding Provider Quick-Reference table, Vector Functions reference, and Extended Gotchas into separate bundle files (e.g., PROVIDERS.md, FUNCTIONS.md) to reduce the main SKILL.md length and improve progressive disclosure.
Consolidate the 'Common Errors' and 'Gotchas — Extended' tables into a single reference, removing duplicated entries (e.g., dimension mismatch and index not ONLINE appear in both).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive and mostly efficient, but includes some redundancy — the 'When to Use' / 'When NOT to Use' sections partially duplicate the frontmatter description, the extended gotchas table repeats information from the common errors table, and the similarity function guidance section restates what was already covered. Some sections could be tightened, but most content earns its place. | 2 / 3 |
Actionability | Excellent actionability throughout — every step includes fully executable Cypher queries and Python code that is copy-paste ready. The version detection query, index creation variants, batch ingestion pattern, search queries (both SEARCH clause and procedure fallback), and polling scripts are all concrete and complete. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (version check → create index → poll ONLINE → ingest → search → combine with graph) with explicit validation checkpoints: polling for ONLINE state before querying, dimension assertions before ingest, sanity check queries after index creation, and error recovery guidance in the common errors table. The checklist at the end reinforces the critical steps. | 3 / 3 |
Progressive Disclosure | The skill has clear section structure and references external skills (neo4j-graphrag-skill, neo4j-genai-plugin-skill, neo4j-document-import-skill) and external docs appropriately. However, the content is quite long (~400+ lines) and some sections like the extended gotchas, extended similarity guidance, and embedding provider reference table could potentially be split into separate reference files. Without bundle files, the inline content is heavy for a single SKILL.md. | 2 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
66ed0e1
Table of Contents
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.