BC red-alert
Israel Red Alert API — real-time and historical rocket/missile alert data. Query alerts by city, time range, generate shelter time stats. Uses redalert.orielhaim.com (socket.io for real-time) and tzevaadom.co.il (REST for history).
Israel Red Alert API — real-time and historical rocket/missile alert data.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:23High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:68High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…X9X+a368j/Ft0w…TWZ/g==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:96High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CzX+oOPq…N14+GARU…vzg==",
detector
Files scanned: 6. 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 "provides" - note
frontmatter-keyunknown frontmatter key "credentials" - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 62/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
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 963 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)
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 231: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 6 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.