BC aws-finops-report
Generate executive-ready monthly AWS FinOps reports with team-level chargeback and savings opportunities
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
GeneratorAWSInfrastructureData and analyticstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 0
✓ No critical or high findings
Files scanned: 2. 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") - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "pack" - note
frontmatter-keyunknown frontmatter key "tier" - note
frontmatter-keyunknown frontmatter key "price"
Process rating: all ten parameters 57/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (aws-finops-report) differs from the folder (finops-report)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 306 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 104: 120–800 characters recommended
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: clean
This skill appears to be a straightforward AWS cost-reporting helper with no evidence of hidden, destructive, or unrelated behavior.
LLM: benign (high) · VirusTotal: benign · 28 May 2026