Back to catalog
Human reviewedOther

Skill dossier

dotnet-core-expert

Source declaration

Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.

The author's original description, preserved in English. It describes intent, not verified performance.

Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.

references

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A backend Skill for .NET 8 and C# 12 applications using minimal APIs, clean architecture, EF Core and MediatR, with build and test steps built into the workflow.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Designs clean architecture layers and minimal API endpoints with OpenAPI documentation.
  • Writes async EF Core queries and MediatR handlers using record-type DTOs.
  • Runs dotnet build and dotnet test, fixing failures before continuing.
  • Writes integration tests with WebApplicationFactory and adds authentication and authorization.

Limitations & scope

  • Scoped to .NET 8 and C# 12; legacy .NET Framework projects are explicitly excluded.
  • Most detail sits in reference files loaded only on demand.
  • Build, test and endpoint behavior are not verified here.

Relevant for

  • C# developers building ASP.NET Core APIs
  • Teams adopting clean architecture with CQRS

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
65.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/dotnet-core-expert/references/authentication.mdReference14.6 KB
skills/dotnet-core-expert/references/clean-architecture.mdReference11.7 KB
skills/dotnet-core-expert/references/cloud-native.mdReference13.7 KB
skills/dotnet-core-expert/references/entity-framework.mdReference12.1 KB
skills/dotnet-core-expert/references/minimal-apis.mdReference8.2 KB
skills/dotnet-core-expert/SKILL.mdInstruction5.1 KB

SKILL.md frontmatter

{
  "name": "dotnet-core-expert",
  "description": "Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "backend",
    "triggers": ".NET Core, .NET 8, ASP.NET Core, C# 12, minimal API, Entity Framework Core, microservices .NET, CQRS, MediatR",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "fullstack-guardian, microservices-architect, cloud-architect, test-master"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze requirements

    Identify the architecture pattern, data models and API design.

  2. 02
    Action

    Design and implement

    Create clean architecture layers and write modern C#, running dotnet build after implementing.

  3. 03
    Decision

    Fix on failure

    If the build or tests fail, diagnose the errors, fix the implementation and rerun before continuing.

  4. 04
    Output

    Deliver structure and code

    Provide project structure, models, endpoints, database context and a brief architectural explanation.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

236 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

225 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 225 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

8 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review generated authentication, authorization and input validation code before exposing any endpoint.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/dotnet-core-expert # .claude/skills/dotnet-core-expert
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/dotnet-core-expert/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to scaffold one endpoint and confirm it runs dotnet build and dotnet test.

Prerequisites

  • Scoped to .NET 8 and C# 12; legacy .NET Framework projects are explicitly excluded.
  • Most detail sits in reference files loaded only on demand.
  • Build, test and endpoint behavior are not verified here.

Example prompts

Representative task

Use the dotnet-core-expert skill to add a GET /users/{id} minimal API endpoint backed by a MediatR query handler and EF Core, returning a record UserDto, with a WebApplicationFactory integration test.

Inspect before use

Read the dotnet-core-expert skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/dotnet-core-expert/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Includes a build-and-test loop with explicit fix-then-rerun instructions.
  • Constraints cover async I/O, nullable reference types and not exposing entities directly.

Considerations

  • Assumes MediatR and Swagger, which some teams may not use.
  • Does not state how to choose between patterns beyond the listed rules.
Research conclusion

A solid, constraint-driven guide for modern .NET API work whose value depends on adopting its clean architecture and MediatR conventions.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/dotnet-core-expert
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.