Entity Framework6

What it does

When your agent uses it

• : EF6 codebases
• Runtime versus ORM migration decisions
• Legacy data-access review
• : unrelated stacks

Example prompts

• “/entity-framework6”

Requirements

• Compatibility (from SKILL.md): Requires EF6 or a transition plan from EF6 to EF Core or modern .NET.

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Audit current EF6 usage before planning any migration. Identify which features the codebase depends on
2. 2Decide runtime vs ORM migration separately
3. 3For maintenance work — keep EF6 stable
4. 4For migration work — validate each slice
5. 5Do not promise EF Core features to EF6 codebases — EF6 is stable and supported but not on the innovation path. Keep expectations realistic.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • dotnet

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Requires EF6 or a transition plan from EF6 to EF Core or modern .NET.

  From compatibility in the SKILL.md frontmatter.

Context cost

Entity Framework6 loads about 1.1k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 133 tokens; SKILL.md has 417 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~133

When it runs · the whole SKILL.md, loaded when a task matches

~1.1k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 417 words, ~1,143 tokens.

name

entity-framework6

description

Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

compatibility

Requires EF6 or a transition plan from EF6 to EF Core or modern .NET.

flowchart LR
  A["Audit EF6 usage"] --> B{"EDMX or complex mappings?"}
  B -->|Yes| C["High migration cost — consider keeping EF6"]
  B -->|No| D["Evaluate EF Core migration"]
  D --> E["Migrate one context at a time"]
  E --> F["Integration test against real DB"]
  C --> G["Modernize runtime only"]
  F --> H["Validate query equivalence"]
  G --> H

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in catalog/Frameworks/Entity-Framework-6/skills/entity-framework6 of managedcode/dotnet-skills.

• SKILL.md
• manifest.json
• references/migration.md
• references/patterns.md

Open the folder on GitHubat commit 535dd55