Skills dotnet-backend
📦
dotnet-backend
Content revision r2 Safe ⚙️ External commands
Build Production ASP.NET Core Backends
Building reliable .NET APIs requires consistent patterns for data access, security, background work, and testing. This skill provides practical ASP.NET Core and EF Core guidance.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "dotnet-backend" from https://skillstore.io/skills/sickn33-dotnet-backend.md and its manifest at https://skillstore.io/api/skills/sickn33-dotnet-backend/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "dotnet-backend". Design a user registration API with PostgreSQL and JWT authentication.
Expected outcome:
- A component plan for endpoints, DTOs, validation, persistence, password hashing, token generation, and authorization.
- Configuration guidance for PostgreSQL, EF Core migrations, JWT settings, and dependency injection.
- Test cases covering valid registration, duplicates, weak passwords, invalid tokens, and protected routes.
Using "dotnet-backend". Review an EF Core endpoint that loads every order and related item.
Expected outcome:
- A diagnosis of excessive loading, tracking overhead, pagination needs, and possible query multiplication.
- A recommended projection with filtering, pagination, asynchronous execution, and read-only behavior.
- Measurement steps using query logging, generated SQL inspection, and representative performance tests.
Using "dotnet-backend". Plan a reliable background email worker.
Expected outcome:
- A worker lifecycle covering scoped dependencies, cancellation, batching, retries, and idempotent status updates.
- Operational guidance for structured logs, health checks, failure monitoring, and graceful shutdown.
- Tests for cancellation, repeated delivery attempts, transient failures, and successful state changes.
Security Audit
Safev5 • 7/23/2026 Open versioned report
All seven external-command alerts are false positives caused by Markdown code fences around C# examples. The reconnaissance alert matches a normal ASP.NET Core response, and no malicious intent or prompt injection was found.
1
Files scanned
265
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (7)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-dotnet-backend/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-dotnet-backend?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-dotnet-backend?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-dotnet-backend/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-dotnet-backend.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). dotnet-backend security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-dotnet-backend/audits/5BibTeX citation
@techreport{sickn33-sickn33-dotnet-backend-2026,
author = {sickn33},
title = {dotnet-backend security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-dotnet-backend/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "dotnet-backend security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-dotnet-backend/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-dotnet-backend:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance
What You Can Build
Create a New Service
Define API endpoints, persistence, validation, authentication, and tests for a new ASP.NET Core service.
Improve Data Access
Review EF Core queries and service boundaries to reduce tracking, excessive loading, and database round trips.
Modernize a Backend
Plan upgrades from older .NET patterns to modern dependency injection, authentication, observability, and background processing.
Try These Prompts
Create a Minimal API
Create an ASP.NET Core 8 Minimal API for [resource]. Include validation, EF Core persistence, DTOs, and clear setup notes.
Add JWT Security
Add JWT authentication and policy-based authorization to my [application type]. Explain configuration, token validation, claims, and protected endpoint changes.
Optimize EF Core
Review this EF Core query: [query]. Identify correctness and performance issues, then propose an optimized version with testing recommendations.
Design a Production Architecture
Design a production backend for [domain] with APIs, persistence, background jobs, observability, resilience, and tests. State assumptions and architecture tradeoffs.
Best Practices
- Provide the target .NET version, database, authentication model, deployment environment, and existing project structure.
- Request tests and security assumptions with every generated endpoint or background process.
- Validate generated migrations, configuration, queries, and authorization rules in a representative environment.
Avoid
- Do not request production code without domain rules, data constraints, or access requirements.
- Do not place secrets, connection strings, or real tokens in prompts.
- Do not deploy generated code before review, automated tests, dependency checks, and performance validation.
Frequently Asked Questions
Which .NET versions does this skill target?
It targets ASP.NET Core 8 and newer versions. Older frameworks may need different hosting, configuration, and authentication patterns.
Can it work with Minimal APIs and controllers?
Yes. It supports both approaches and can recommend one based on project complexity and existing conventions.
Which databases and data tools are supported?
The guidance covers EF Core, Dapper, SQL Server, PostgreSQL, and MySQL.
Can it implement authentication and authorization?
Yes. It covers JWT, ASP.NET Core Identity, OAuth 2.0, Azure AD, roles, claims, and policies.
Does it generate deployment configuration?
Provider-specific deployment is outside the default scope. Supply the cloud provider and runtime environment for tailored guidance.
Does generated code still require review?
Yes. Review security, error handling, migrations, dependencies, configuration, tests, and performance before production use.