CD azure-backup
Expert knowledge for Azure Backup development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when protecting Azure VMs, SQL/SAP HANA, AKS, Files/Blobs, or using CLI/PowerShell/REST for backup automation, and other Azure Backup related development tasks. Not for Azure Site Recovery (use azure-site-recovery), Azure Virtual Machines (use azure-virtual-machines), Azure Blob Storage (use azure-blob-storage).
Expert knowledge for Azure Backup development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas…
As a process D 40/100 · Unfinished process — References files that are not bundled: security.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securitySKILL.md:32Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)| Security | L136-L172 | Securing Azure Backup and AKS backups: RBAC and managed identities, CMK encryption, soft delete, private endpoints, MUA/Resource Guard, ransomware protection, and secure resto
detector -
low Risky intent
intent-offensive-securitySKILL.md:159Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Secure Azure Backup against ransomware and threats | https://learn.microsoft.com/en-us/azure/backup/protect-backups-from-ransomware-faq |
-
low Risky intent
intent-offensive-securitySKILL.md:287Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Integrate Defender ransomware alerts with Azure Backup | https://learn.microsoft.com/en-us/azure/backup/backup-azure-integrate-microsoft-defender-using-logic-apps |
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10106 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: security.md - note
edit-residuethe text marks something as outdated (lines 194, 241): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: security.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 45 mutating operations with no state check
- 40Execution cost. Instruction body is 10106 tokens: crowds the task out of the window
- 50Steps. 2 steps
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 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 545: enough signal without eating the budget
- +4Structure: 12 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.