dotnet-input-validation

The skill's footprint is coherent with its stated purpose: it describes validation strategies, integration patterns, and security-conscious practices for .NET APIs. It relies on official, trusted sources (NuGet packages and Microsoft tooling) and focuses on in-process validation with clear, safe dataflow to RFC 9457 ProblemDetails. There are no explicit data exfiltration patterns, unverifiable binaries, or credential-forwarding mechanisms. The main risk is the potential for misconfiguration if developers mix frameworks or disable security controls (e.g., antiforgery) in their own code; however, as a guidance/documentation skill, these risks are mitigated by the explicit cautions and required prerequisites. Overall, the skill is BENIGN with some SUSPICIOUS signals only if deployed without adherence to its stated constraints (e.g., mixing frameworks, disabling security features in production).