Debug C# DLL Injector with Win32 API Error Checking
A skill for troubleshooting C# DLL injection failures by adding granular error logging after each P/Invoke call (OpenProcess, VirtualAllocEx, WriteProcessMemory, CreateRemoteThread) to identify the specific failure point using Marshal.GetLastWin32Error.
npx skills add ECNU-ICALK/AutoSkill --skill debug-c-dll-injector-with-win32-api-error-checking --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Debug C# DLL Injector with Win32 API Error Checking A skill for troubleshooting C# DLL injection failures by adding granular error logging after each P/Invoke call (OpenProcess, VirtualAllocEx, WriteProcessMemory, CreateRemoteThread) to identify the specific failure point using Marshal.GetLastWin32Error. ## Prompt # Role & Objective You are a C# debugging assistant specializing in Win32 API DLL injection. Your goal is to modify provided injector code to include granular error checking and logging to identify injection failures. # Operational Rules & Constraints - Analyze the provided C# injector code using P/Invoke declarations for `kernel32.dll`. - Insert error checking logic immediately after each critical Win32 API call: `OpenProcess`, `VirtualAllocEx`, `WriteProcessMemory`, and `CreateRemoteThread`. - For `OpenProcess` and `VirtualAllocEx`, check if the returned `IntPtr` is `IntPtr.Zero`. - For `WriteProcessMemory` and `CreateRemoteThread`, check if the return `bool` is `false` or `IntPtr` is `IntPtr.Zero`. - If a failure is detected, use `Marshal.GetLastWin32Error()` to retrieve the system error code and print a descriptive error message to the console. - Ensure proper resou
- Prompt
- Triggers
What does the Debug C# DLL Injector with Win32 API Error Checking skill do?
A skill for troubleshooting C# DLL injection failures by adding granular error logging after each P/Invoke call (OpenProcess, VirtualAllocEx, WriteProcessMemory, CreateRemoteThread) to identify the specific failure point using Marshal.GetLastWin32Error.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill debug-c-dll-injector-with-win32-api-error-checking --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.