dapr-dotnet
v1.0.1Expertise in backend development using Dapr and .NET7/8/9 to design, build, and optimize high-performance, maintainable microservice architectures.
⭐ 0· 254·0 current·0 all-time
byWesLon@weslon1987
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (Dapr + .NET backend expertise) match the SKILL.md content: project structure, YAML config for Dapr components, and C# code samples for typical microservice patterns.
Instruction Scope
SKILL.md contains architecture guidance, YAML and C# snippets, and recommendations for running a Dapr sidecar. It does not instruct reading unrelated system files, exfiltrating data, or accessing secrets beyond typical local dev config files (.dapr components/config). It does reference a helper (BaseHelper.AddDaprdProcess) that would start a process if implemented, which is expected for local Dapr debugging.
Install Mechanism
No install spec is present (instruction-only). Nothing will be written to disk by an installer; therefore there is no download or package-install risk from the skill itself.
Credentials
The skill declares no required environment variables or credentials. The included sample configs use local endpoints (localhost) and empty passwords; nothing in the skill requests unrelated cloud credentials or secrets.
Persistence & Privilege
Skill is user-invocable, not always-enabled, and allows model invocation (the platform default). It does not request persistent presence or system-wide config changes.
Assessment
This is an instruction-only skill that provides Dapr + .NET architecture guidance and code snippets — it is internally consistent. Before using it, review the SKILL.md yourself: 1) verify any commands or helper calls (e.g., AddDaprdProcess/BaseHelper) will be run in a safe development environment and won't spawn unexpected processes; 2) replace localhost/example credentials with safe values and never paste real production secrets into config snippets; 3) if you plan to let an agent apply these instructions, run it in a sandbox or dev cluster so it cannot touch production resources; and 4) because the skill's source is unknown, prefer manual review of the snippets before executing them.Like a lobster shell, security has layers — review code before you run it.
latestvk97fhskack05hsck9nbss6w4ph82vd1j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.