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.

A dense, highly actionable reference skill with executable examples, a useful API-selection table, and clean progressive disclosure to three real reference files. Its main weakness is mild redundancy between inline ❌/✅ warnings and the trailing Common Mistakes table, and the absence of an explicit validate-retry loop for batch writes.

Suggestions

Collapse the 'Common Mistakes' table or the inline ❌/✅ blocks — keeping one canonical form would remove redundancy and reclaim tokens.

Add an explicit validate-then-retry checkpoint to the UNWIND batching / write flow (e.g., verify Counters after ExecuteAsync and re-run on transient failure) to satisfy the batch-operation feedback-loop bar.

Consider moving the long 'Type Mapping' table into a reference file to keep SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

Lean, code-forward body that assumes competence and avoids explaining basic concepts, but the closing 'Common Mistakes' table largely restates the inline ❌/✅ warnings — a minor redundancy that could be trimmed. Not a 5 because of that duplicated material; not a 3 because the rest is efficient.

4 / 5

Actionability

Copy-paste-ready executable C# across read, write, UNWIND batching, object mapping, and error handling, each with concrete parameters and configs — fully covering the common cases per the 5 anchor.

5 / 5

Workflow Clarity

The 'Choose the Right API' decision table, idempotency/retry guidance, commit-uncertainty handling, and a verification Checklist sequence the work with most checkpoints present. Not a 5 because batch (UNWIND) and write flows lack an explicit validate-then-retry feedback loop; not a 3 because the checklist and error-handling section supply genuine verification.

4 / 5

Progressive Disclosure

Well-organized overview body with three clearly signaled one-level-deep references — transactions.md, performance.md, object-mapping.md — each annotated with its scope; all referenced files exist, matching the 5 anchor for clear overview with well-signaled shallow references.

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.

A highly specific, well-triggered description that concretely enumerates capabilities, gives explicit positive and negative trigger guidance, and cleanly separates from sibling skills. It is dense but every clause earns its place.

DimensionReasoningScore

Specificity

Lists many concrete capabilities — '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' — comprehensive coverage of specific actions, matching the 5 anchor.

5 / 5

Completeness

Explicitly answers both what (the enumerated capabilities) and when ('Use when writing C# or .NET code connecting to Neo4j. Also triggers on...'), plus negative triggers, hitting the 5 anchor for explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural domain triggers are exhaustively listed — 'Neo4j.Driver, IDriver, ExecutableQuery, ExecuteReadAsync, ExecuteWriteAsync, IResultCursor, IAsyncSession, or any Bolt/Aura work in .NET/C#' — the exact type/API names a .NET user would name when they need this skill.

5 / 5

Distinctiveness Conflict Risk

Narrow niche (Neo4j .NET Driver v6) with explicit deconfliction — 'Does NOT handle Cypher authoring — use neo4j-cypher-skill' and 'Does NOT cover driver version upgrades — use neo4j-migration-skill' — minimal 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.