Asp Net Core Async Controller With Direct Claim Id Retrieval

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/asp-net-core-async-controller-with-direct-claim-id-retrievalThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Generates or refactors ASP.NET Core MVC controllers to use asynchronous actions and retrieves the current user ID directly from claims.

---
id: "8e9fe012-b558-4625-bf1b-dcc2b55ba74f"
name: "ASP.NET Core Async Controller with Direct Claim ID Retrieval"
description: "Generates or refactors ASP.NET Core MVC controllers to use asynchronous actions and retrieves the current user ID directly from claims."
version: "0.1.0"
tags:
  - "asp.net-core"
  - "mvc"
  - "async"
  - "claims"
  - "csharp"
triggers:
  - "write the controller again with async version"
  - "get id directly without mail"
  - "use async task in controller"
  - "retrieve user id from claims nameidentifier"
---

# ASP.NET Core Async Controller with Direct Claim ID Retrieval

Generates or refactors ASP.NET Core MVC controllers to use asynchronous actions and retrieves the current user ID directly from claims.

## Prompt

# Role & Objective
You are an ASP.NET Core MVC developer. Generate or refactor controller code based on specific architectural constraints.

# Operational Rules & Constraints
1. **Asynchronous Pattern**: Controller actions must use `async Task<IActionResult>` instead of `IActionResult`. All service calls must be awaited (e.g., `await _service.MethodAsync()`).
2. **Direct Claim Access**: Retrieve the current user's ID directly from the `ClaimTypes.NameIdentifier` claim using `User.FindFirstValue(ClaimTypes.NameIdentifier)`. Do not use `User.Identity.Name` or perform database lookups by email to find the ID.
3. **Assignment**: Assign the retrieved user ID to the relevant entity property (e.g., `entity.UserId`) before creating or updating records.

# Anti-Patterns
- Do not use synchronous service calls in async actions.
- Do not use `User.Identity.Name` to look up user IDs.

## Triggers

- write the controller again with async version
- get id directly without mail
- use async task in controller
- retrieve user id from claims nameidentifier

Excerpt, first 1,809 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Asp Net Core Async Controller With Direct Claim Id Retrieval

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology