CtrlK
BlogDocsLog inGet started
Tessl Logo

change-tracking

Implementation details for EF Core change tracking. Use when changing InternalEntityEntry, ChangeDetector, SnapshotFactoryFactory, or related entity state, snapshot, or property accessor code.

68

Quality

81%

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

72%

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 concise, well-organized architecture map that respects token budget and avoids restating known concepts. It is weaker on actionability and workflow clarity because it offers overview-level guidance and test pointers rather than executable examples or an explicit procedural sequence with validation checkpoints.

Suggestions

Add a concrete code snippet showing how to check SharedIdentityEntry in the Common Pitfalls table so the solution is copy-paste-ready rather than directional.

Turn the Validation section into an explicit numbered checklist (e.g., run DetectChanges, compare original vs. current values, confirm Modified flag) with a verify-before-proceeding step.

Provide one executable example of invoking the change-detection workflow on an InternalEntityEntry so the guidance is actionable rather than purely descriptive.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — quotes like 'StateManager — central engine, identity maps, tracks all entities' convey architecture without explaining concepts Claude already knows, and every token earns its place.

3 / 3

Actionability

Concrete details exist (test paths 'test/EFCore.Tests/ChangeTracking/' and method names like 'DetectChanges()'), but the pitfall solution 'Add code that checks SharedIdentityEntry' is direction without executable code, and there are no copy-paste-ready examples for performing the actual work.

2 / 3

Workflow Clarity

Content is organized into clear sections, but it is descriptive architecture rather than a sequenced procedure; the 'Validation' section explains the mechanism ('identifies modified properties via snapshot comparison') without providing an explicit validate-then-proceed checklist or error-recovery feedback loop.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no external bundle files, and it is well-organized into Core Components, Testing, Common Pitfalls, and Validation sections, satisfying the simple-skill allowance for a top score on well-organized section structure.

3 / 3

Total

10

/

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.

The description cleanly answers both what the skill covers and when to use it, with an explicit 'Use when' trigger and distinct, domain-specific class names that a contributor would naturally invoke. Its only weakness is that 'Implementation details' is a somewhat abstract capability statement rather than a list of concrete actions.

DimensionReasoningScore

Specificity

Quotes 'Implementation details for EF Core change tracking' and 'Use when changing InternalEntityEntry, ChangeDetector, SnapshotFactoryFactory' — it names a domain and specific components, but 'Implementation details' is an abstract capability rather than multiple concrete action verbs like 'extract', 'fill', 'merge'.

2 / 3

Completeness

Quotes 'Implementation details for EF Core change tracking' (what) and 'Use when changing InternalEntityEntry, ChangeDetector...' (when) — both what and when are explicitly answered with an explicit 'Use when' trigger clause, satisfying the third-person voice rule.

3 / 3

Trigger Term Quality

Quotes 'InternalEntityEntry, ChangeDetector, SnapshotFactoryFactory, or related entity state, snapshot, or property accessor code' — these are exactly the natural terms a contributor working on EF Core internals would name, with good coverage of the relevant class and concept names.

3 / 3

Distinctiveness Conflict Risk

Quotes 'EF Core change tracking' and the specific class names — this is a narrow niche with distinct triggers tied to named internal types, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/efcore
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.