BC openclaw-aws-sre-report
AWS SRE health check with FinOps — queries CloudWatch, SQS DLQ, and Cost Explorer, generates a Bedrock-powered incident diagnosis (Contexto, Soluções, CTAs), and sends a structured report to Telegram.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urlsrc/reporter.ts:98Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)const resp = await fetch(`https://api.telegram.org/bot${token}/sendMessage`, {placeholder -
low Exfiltration
net-credential-usesrc/reporter.ts:98Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)const resp = await fetch(`https://api.telegram.org/bot${token}/sendMessage`, {vendor-hostquoted
Files scanned: 10. 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")
Process rating: all ten parameters 62/100
- 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
- 30Running it twice. 2 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1124 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
This skill does what it advertises: reads AWS monitoring and cost data, uses Bedrock for incident summaries, and sends the report to Telegram.
LLM: benign (high) · VirusTotal: · 29 May 2026