SKILLEMALL.ai
GitHub ↗ RU Sign in

CD azure-security

Expert knowledge for Azure Security development including best practices, decision making, security, configuration, integrations & coding patterns, and deployment. Use when configuring Azure antimalware, container SBOM/signing, CMK encryption, AKS/VM hardening, or Key Vault keys, and other Azure Security related development tasks. Not for Azure Defender For Cloud (use azure-defender-for-cloud), Azure Information Protection (use azure-information-protection), Azure DDoS Protection (use azure-ddos-protection), Azure Web Application Firewall (use azure-web-application-firewall).

MicrosoftDocs/Agent-Skills Agent Skills author: MicrosoftDocs CC-BY-4.0 1 file body ≈ 3 150 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Expert knowledge for Azure Security development including best practices, decision making, security, configuration, integrations & coding patterns, and…

As a process D 36/100 · Unfinished process — References files that are not bundled: security.md

GeneratorAzureGitHubInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
75
Run on models
none yet
Process rating
D
36/100
Unfinished process
References files that are not bundled: security.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

✓ No critical or high findings

Medium and low: 5
  • low Risky intent intent-offensive-security SKILL.md:27
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Best Practices | L34-L58 | End-to-end Azure security guidance: hardening IaaS/PaaS, identity and access, network and operational security, backups and ransomware resilience, secrets management, and
  • low Risky intent intent-offensive-security SKILL.md:30
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    | Configuration | L98-L108 | Configuring Azure security features: antimalware, container scanning (Dependabot/Copacetic), firewall rules, CMK encryption, logging/auditing, TLS changes, ransomware prot
    detector
  • low Risky intent intent-offensive-security SKILL.md:38
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Design Azure backup and restore plans against ransomware | https://learn.microsoft.com/en-us/azure/security/fundamentals/backup-plan-to-protect-against-ransomware |
  • low Risky intent intent-offensive-security SKILL.md:51
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    | Detect and respond to ransomware in Azure | https://learn.microsoft.com/en-us/azure/security/fundamentals/ransomware-detect-respond |
    detector
  • low Risky intent intent-offensive-security SKILL.md:52
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Prepare Azure environments for ransomware resilience | https://learn.microsoft.com/en-us/azure/security/fundamentals/ransomware-prepare |

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: security.md

Process rating: all ten parameters 36/100

Will not run. References files that are not bundled: security.md
  • 0Tools and files. 1 referenced file(s) missing: security.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 7 mutating operations with no state check
  • 50Steps. 2 steps
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3150 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 582: enough signal without eating the budget
  • +4Structure: 9 headings

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.