BF aws-cloudformation
Author, validate, and troubleshoot AWS CloudFormation templates. Covers template authoring with secure defaults, pre-deployment validation (cfn-lint, cfn-guard, change sets), and root-cause diagnosis of failed stacks using CloudFormation events and CloudTrail correlation.
Author, validate, and troubleshoot AWS CloudFormation templates.
As a process F 42/100 · Will not run — References files that are not bundled: references/author-cloudformation-best-practices.script.md, references/lookup-resource-properties.script.md, references/validate-cloudformation-template.script.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/author-cloudformation-best-practices.script.md - warning
missing-refreference to a missing file: references/lookup-resource-properties.script.md - warning
missing-refreference to a missing file: references/validate-cloudformation-template.script.md - warning
missing-refreference to a missing file: references/check-cloudformation-template-compliance.script.md - warning
missing-refreference to a missing file: references/cloudformation-pre-deploy-validation.script.md - warning
missing-refreference to a missing file: references/deploy-with-express-mode.script.md - warning
missing-refreference to a missing file: references/troubleshoot-deployment.script.md - note
edit-residuethe text marks something as outdated (lines 76): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 42/100
- 0Tools and files. 7 referenced file(s) missing: references/author-cloudformation-best-practices.script.md, references/lookup-resource-properties.script.md, references/validate-cloudformation-template.script.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 20 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1527 tokens
- 100Running it twice. Mutating operations check current state
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 272: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 20 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.