CtrlK
BlogDocsLog inGet started
Tessl Logo

neo4j-driver-dotnet-skill

Neo4j .NET Driver v6 — IDriver lifecycle, DI registration (singleton), ExecutableQuery fluent API, ExecuteReadAsync/ExecuteWriteAsync managed transactions, IResultCursor (FetchAsync/ ToListAsync), record value access (.Get<T>/As<T>), null safety, UNWIND batching, temporal types, await using, EagerResult, object mapping, CancellationToken, error handling, and common traps. Use when writing C# or .NET code connecting to Neo4j. Also triggers on Neo4j.Driver, IDriver, ExecutableQuery, ExecuteReadAsync, ExecuteWriteAsync, IResultCursor, IAsyncSession, or any Bolt/Aura work in .NET/C#. Does NOT handle Cypher authoring — use neo4j-cypher-skill. Does NOT cover driver version upgrades — use neo4j-migration-skill.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 reference with executable code and effective progressive disclosure into real bundle files. Minor conciseness and feedback-loop gaps keep it just short of perfect.

Suggestions

Consolidate the inline ❌/✅ warnings with the "Common Mistakes" table to reduce duplication and token cost.

Add an explicit validate→fix→retry loop for UNWIND batch writes (e.g., check counts, retry failed batches) to strengthen feedback for batch operations.

Consider moving the full type-mapping table to a reference file and keeping only the most common types inline to further lean out the core skill.

DimensionReasoningScore

Conciseness

Code examples are tight and assume Claude's competence without explaining basics, but the large "Common Mistakes" table partly duplicates the inline ❌/✅ warnings, adding length that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready, executable C# covering read/write, managed transactions, FetchAsync loops, object mapping, error handling, and UNWIND batching across the common cases.

5 / 5

Workflow Clarity

Clear decision guidance ("Choose the Right API" table) plus a checklist and idempotency/commit-uncertainty notes for destructive/batch writes, but lacks explicit validate→fix→retry feedback loops for batch operations.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with three well-signaled, one-level-deep references (transactions.md, performance.md, object-mapping.md) that all exist and match their descriptions; advanced content is appropriately split out.

5 / 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 comprehensive and well-targeted, explicitly stating capabilities, trigger phrases, and clear boundaries against sibling skills. It fully answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists many concrete capabilities (IDriver lifecycle, DI singleton, ExecutableQuery fluent API, managed transactions, IResultCursor, record access, UNWIND batching, null safety) with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both "what" (detailed capability list) and "when" ("Use when writing C# or .NET code connecting to Neo4j", "Also triggers on...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrasing ("writing C# or .NET code connecting to Neo4j", "Bolt/Aura work") plus explicit API-type triggers (Neo4j.Driver, IDriver, ExecutableQuery, IAsyncSession) covering synonyms (.NET/C#).

5 / 5

Distinctiveness Conflict Risk

Niche-specific to Neo4j .NET Driver v6 with explicit boundary exclusions ("Does NOT handle Cypher authoring — use neo4j-cypher-skill", "Does NOT cover driver version upgrades"), minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.