SKILLEMALL.ai
GitHub ↗ RU Sign in

CC implementing-vulnerability-sla-breach-alerting

Build an automated SLA breach alerting system for vulnerability remediation, including a database schema for SLA tracking, breach detection logic, notification dispatch, a scheduled check runner, and a KPI/compliance metrics dashboard. Use when implementing severity-based SLA timelines (critical/high/medium/low), detecting and escalating SLA breaches, or building vulnerability remediation compliance reporting.

Not recommendedcritical or high security findings
mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 8 files · 2 scripts body ≈ 2 360 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Build an automated SLA breach alerting system for vulnerability remediation, including a database schema for SLA tracking, breach detection logic…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

GeneratorSlackMedia and videotype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
79/100
safety, quality, tests
Safety 60%
82
Quality 40%
75
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
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 · 1

  • high Dangerous commands cmd-persistence SKILL.md:267
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    echo "0 * * * * cd /opt/vuln-sla && python3 scripts/process.py --check-sla" | crontab -

Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • note frontmatter-key unknown frontmatter key "domain"
  • note frontmatter-key unknown frontmatter key "subdomain"
  • note frontmatter-key unknown frontmatter key "nist_csf"
  • note frontmatter-key unknown frontmatter key "mitre_attack"

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 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 (python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 12 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2360 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
  • -43 reference files, but SKILL.md never points to them: the model will not open them
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 413: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 12 items
  • +4Has examples (6 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.