sqlite-adonet

Implementation details for the Microsoft.Data.Sqlite ADO.NET provider. Use when changing files under `src/Microsoft.Data.Sqlite.Core/`.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

A concise, well-organized reference of notable implementation facts for this provider. Its main gap is actionability: it tells Claude what is true about the code but not what to concretely do when changing it.

Suggestions

Add a short, concrete action or checklist for the common change (e.g., how to regenerate the T4-generated overloads, or the command to run after editing a `.tt` file) so the skill instructs rather than only describes.

Optionally include a one-line pointer to where the static-constructor and battery-init logic lives (file/method name) so guidance is directly actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — a one-line positioning statement plus two factual bullets — with no padding and no explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	It names concrete specifics (the reflective `SQLitePCL.Batteries_V2.Init()` call, the `.tt` T4 templates) but describes facts rather than giving executable guidance, commands, or steps for what a developer should actually do when changing these files.	2 / 3
Workflow Clarity	This is a simple single-purpose knowledge skill under 50 lines with no multi-step process and no destructive/batch operations requiring validation, so the single unambiguous purpose meets the top anchor per the simple-skills scoring note.	3 / 3
Progressive Disclosure	At under 50 lines with no external references needed (none provided), the well-organized H1/intro/bulleted-section structure satisfies the top anchor for compact skills that do not require bundle files.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 tight, well-targeted description that names a specific provider and directory, with an explicit 'Use when' trigger. The only weakness is that it describes one action category rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the specific domain ("Microsoft.Data.Sqlite ADO.NET provider") and a concrete scope ("changing files under `src/Microsoft.Data.Sqlite.Core/`"), but lists only a single action category rather than the multiple distinct concrete actions the top anchor exemplifies.	2 / 3
Completeness	It explicitly answers both what ("Implementation details for the Microsoft.Data.Sqlite ADO.NET provider") and when ("Use when changing files under `src/Microsoft.Data.Sqlite.Core/`") with an explicit trigger clause.	3 / 3
Trigger Term Quality	"Microsoft.Data.Sqlite ADO.NET provider" and "changing files under `src/Microsoft.Data.Sqlite.Core/`" are exactly the natural technical terms a developer working on this codebase would say when needing the skill.	3 / 3
Distinctiveness Conflict Risk	The description is pinned to a single named provider and a specific directory path, giving it a clear niche that is very unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: dotnet/efcore
Path: .agents/skills/sqlite-adonet/SKILL.md
Commit: 61317c9

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.