SKILLEMALL.ai

DD security-compliance

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.

davila7/claude-code-templates Agent Skills author: davila7 MIT 13 files · 2 scripts body ≈ 7 112 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR…

As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerSecurityData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
D
61/100
safety, quality, tests
Safety 60%
65
Quality 40%
55
Run on models
none yet
Process rating
D
47/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 35

✓ No critical or high findings

Medium and low: 35
  • low Risky intent intent-offensive-security examples/incident-response-template.md:171
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)
    | 2 | Update incident response playbook with ransomware procedures | Security Manager | 2025-02-01 | High | Open |
    fixture
  • low Risky intent intent-offensive-security examples/incident-response-template.md:229
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition; test fixture / example file)
    [Detailed technical analysis, IoCs, malware analysis, etc.]
    detectorfixture
  • low Risky intent intent-offensive-security README.md:107
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    **Situation**: Your SOC detected ransomware on multiple systems.
    detector
  • low Risky intent intent-offensive-security README.md:111
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    2. Use IR playbook for ransomware (included in security-operations.md)
  • low Risky intent intent-offensive-security README.md:220
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Ransomware Attack on Production Infrastructure: $900,000
  • low Risky intent intent-offensive-security README.md:286
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Segment networks to limit lateral movement
  • low Risky intent intent-offensive-security README.md:430
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - OSCP (Offensive Security Certified Professional)
  • low Risky intent intent-offensive-security reference/application-security.md:45
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    │  □ Penetration testing                                     │
  • low Risky intent intent-offensive-security reference/application-security.md:70
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    │  □ Periodic penetration testing (annually)                 │
  • low Dangerous commands cmd-eval-dynamic reference/application-security.md:209
    Dynamic code execution from decoded/untrusted input (documentation of a security skill)
    result = os.system(f'ping -c 1 {host}')
    security skill
  • low Secrets in code secret-high-entropy-token reference/application-security.md:494
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    integrity="sha3…kM6+R9GqQ8K/uxy9…8wC"
    quoted
  • low Risky intent intent-offensive-security reference/application-security.md:562
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    □ Privilege escalation attempts
  • low Risky intent intent-offensive-security reference/compliance-frameworks.md:1093
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Threat: Ransomware Attack
  • low Risky intent intent-offensive-security reference/compliance-frameworks.md:1097
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Likelihood: High (0.9) - Widespread ransomware campaigns targeting healthcare
  • low Risky intent intent-offensive-security reference/compliance-frameworks.md:1203
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    • Perform penetration testing (annually + after significant changes)
  • low Risky intent intent-offensive-security reference/security-architecture.md:206
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Limits lateral movement
  • low Risky intent intent-offensive-security reference/security-architecture.md:284
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | Lateral movement | Possible | Prevented |
  • low Secrets in code secret-aws-key reference/security-architecture.md:361
    AWS access key ID (placeholder value)
    aws iam update-access-key --access-key-id AKIA…PLE --status Inactive
    placeholder
  • low Risky intent intent-offensive-security reference/security-operations.md:24
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ├─ Advanced forensics and malware analysis
  • low Risky intent intent-offensive-security reference/security-operations.md:226
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    # Hunt 3: WMIC used for lateral movement
  • low Risky intent intent-offensive-security reference/security-operations.md:308
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    | P0 - Critical | Active breach, data exfiltration, ransomware | Active data theft, ransomware encryption, complete system compromise | Immediate (24/7) |
  • low Dangerous commands cmd-cron-mention reference/security-operations.md:419
    Mentions editing / listing crontab (documentation of a security skill)
    crontab -e  # Remove malicious line
    security skill
  • low Risky intent intent-offensive-security reference/security-operations.md:573
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Isolation prevented lateral movement
  • low Risky intent intent-offensive-security reference/security-operations.md:579
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Incident response playbook for ransomware needed update
  • low Risky intent intent-offensive-security reference/threat-modeling-risk.md:39
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    • Examples: Privilege escalation, exploiting vulnerabilities, bypassing access controls
  • low Risky intent intent-offensive-security reference/threat-modeling-risk.md:135
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Penetration test results
  • low Risky intent intent-offensive-security reference/threat-modeling-risk.md:147
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    │  └─ Bypass WAF
  • low Risky intent intent-offensive-security reference/threat-modeling-risk.md:341
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    # Example: Assess risk of ransomware attack
  • low Risky intent intent-offensive-security reference/threat-modeling-risk.md:617
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    6. Privilege Escalation
  • low Risky intent intent-offensive-security SKILL.md:104
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    - Perform vulnerability scanning and penetration testing
    detector
  • low Risky intent intent-offensive-security SKILL.md:115
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Penetration test reports
  • low Risky intent intent-offensive-security SKILL.md:325
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Ransomware encryption in progress
  • low Risky intent intent-offensive-security SKILL.md:437
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    □ Penetration test results (for high/critical)
  • low Risky intent intent-offensive-security SKILL.md:573
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Penetration testing and red teaming

A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 7112 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 47/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. 8 mutating operations with no state check
  • 70Execution cost. Instruction body is 7112 tokens
  • 85Steps. 330 steps, 2 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 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
  • -45 reference files, but SKILL.md never points to them: the model will not open them
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 308: enough signal without eating the budget
  • +4Structure: 82 headings
  • +3Step-by-step instructions: 330 items
  • +4Has examples (10 code blocks)

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