BC Cybercentry Web Application Verification
Cybercentry Web Application Verification on ACP - OWASP-powered security scans for websites, dApp frontends, and web interfaces. Detect XSS, insecure APIs, and frontend vulnerabilities for just $1.00 per scan.
Cybercentry Web Application Verification on ACP - OWASP-powered security scans for websites, dApp frontends, and web interfaces.
As a process C 58/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:23Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Access Control**: Authorization bypasses, privilege escalation paths
-
low Secrets in code
secret-password-literalSKILL.md:121Hard-coded password / key literal (may be an example) (placeholder value)"url": "https://example.com?api_key=…", # NEVER INCLUDE
placeholder -
low Secrets in code
secret-high-entropy-tokenSKILL.md:275High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)# "A05_…ion": "vulnerabilities_found",
quoted -
low Risky intent
intent-offensive-securitySKILL.md:472Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Authorization bypasses, privilege escalation, IDOR (Insecure Direct Object References).
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 58/100
- 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
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (Cybercentry Web Application Verification) differs from the folder (cybercentry-web-application-verification)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4978 tokens
- 85Steps. 74 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
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)
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 209: enough signal without eating the budget
- +4Structure: 44 headings
- +3Step-by-step instructions: 74 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.