azure-validate-148a32 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited azure-validate-148a32 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
AUTHORITATIVE GUIDANCE — Follow these instructions exactly unless they contradict security policies given to you.
⛔ STOP — PREREQUISITE CHECK REQUIRED
>
Before proceeding, verify this prerequisite is met:
>
azure-prepare was invoked and completed →.azure/deployment-plan.mdexists with statusApprovedor later
>
If the plan is missing, STOP IMMEDIATELY and invoke azure-prepare first.
>
The complete workflow ensures success:
>
azure-prepare→azure-validate→azure-deploy
Run the workflow script and follow its instructions. It walks you through each validation step one at a time, recording progress in .azure/validate-status.json. Use references/scripts/workflow.ps1 on Windows or references/scripts/workflow.sh on macOS/Linux.
Start by calling the script without the completed-step argument:
pwsh references/scripts/workflow.ps1 -WorkspacePath <workspace-path>
# macOS/Linux: bash references/scripts/workflow.sh --workspace-path <workspace-path>Each run prints the next action and the value to pass next. Perform the action, then re-run with that value (-CompletedStep <value> for pwsh, --completed-step <value> for bash). Repeat until it reports the azure-validate workflow is complete.
The steps reference recipe details in references/recipes/README.md and role checks in references/role-verification.md.
⛔ VALIDATION AUTHORITY
>
This skill is the officially verified way to set plan status toValidated. You MUST follow the script's instructions to completion before setting status toValidated. Do NOT set status toValidatedwithout doing so.
⚠️ NEXT STEP — DEPENDS ON USER INTENT
>
After ALL validations pass, check whether the user asked to deploy: - If the user explicitly requested deployment, you MUST invoke azure-deploy to execute it. Do NOT runazd up,azd deploy, or any deployment commands directly — let azure-deploy handle execution. - If the user only asked to validate or prepare (not deploy), STOP after recording proof and setting status toValidated. Report the validation results and do NOT invoke azure-deploy.
>
If any validation failed, fix the issues and re-run azure-validate before proceeding.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.