BC web-health-suite
Comprehensive web health monitoring and quality assurance suite for AI agents. Performs HTTP health checks, response quality analysis, compliance validation, SSL certificate monitoring, API endpoint verification, and generates professional HTML reports for web applications and services. Use when: (1) monitoring web service health and uptime, (2) validating HTTP response quality and headers, (3) checking SSL certificate status and expiration, (4) verifying API endpoint availability and response format, (5) quality assurance testing for web deployments, (6) generating professional health monitoring reports.
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- 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 Risky intent
intent-offensive-securityTERMS_OF_USE.md:17Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Bug bounty programs** with written scope approval from the program owner
-
low Risky intent
intent-offensive-securityTERMS_OF_USE.md:64Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Bug bounty hunters** with confirmed program authorization
-
low Risky intent
intent-offensive-securityTERMS_OF_USE.md:85Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Bug bounty program rules and guidelines
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Comprehensive web health monitoring and quality assurance suite fo… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
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 (web-health-suite) differs from the folder (security-test-suite)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Execution cost. Instruction body is 1251 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +1No license
- +2Single-language instructions
- +3Description length 612: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 17 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.