AD senior-secops
Comprehensive SecOps skill for application security, vulnerability management, compliance, and secure development practices. Includes security scanning, vulnerability assessment, compliance checking, and security automation. Use when implementing security controls, conducting security audits, responding to vulnerabilities, or ensuring compliance requirements.
Comprehensive SecOps skill for application security, vulnerability management, compliance, and secure development practices.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Risky intent
intent-offensive-securityreferences/compliance_requirements.md:59Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Penetration testing (annual)
-
low Dangerous commands
cmd-eval-dynamicreferences/security_standards.md:105Dynamic code execution from decoded/untrusted input (documentation of a security skill)# NEVER use: os.system(f"ping {user_input}")security skill -
low Risky intent
intent-offensive-securitySKILL.md:36Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Security Testing** | SAST, DAST, penetration test, security scan, Snyk, Semgrep, CodeQL, Trivy |
-
low Risky intent
intent-offensive-securitySKILL.md:369Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Req 11 | Security testing (SAST, DAST, penetration testing) |
-
low Secrets in code
secret-password-literalSKILL.md:399Hard-coded password / key literal (may be an example) (placeholder value)API_KEY = "sk-1…def"
placeholder
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3819 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 361: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.