SKILLEMALL.ai

CC analyzing-ransomware-network-indicators

Identify ransomware-related network indicators, including C2 beaconing patterns, TOR exit node connections, data exfiltration flows, and encryption key exchange, by analyzing Zeek conn.log and NetFlow data. Use when threat hunting for active ransomware network activity or investigating suspected pre-encryption exfiltration during incident response.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 4 files · 1 script body ≈ 485 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Identify ransomware-related network indicators, including C2 beaconing patterns, TOR exit node connections, data exfiltration flows, and encryption key…

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

AnalyzerInfrastructureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
93
Quality 40%
71
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    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 · 7

    ✓ No critical or high findings

    Medium and low: 7
    • low Risky intent intent-offensive-security references/api-reference.md:1
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # Ransomware Network Indicator Analysis API Reference
    • low Risky intent intent-offensive-security references/api-reference.md:83
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | Data Encrypted for Impact | T1486 | Ransomware encryption |
    • low Risky intent intent-offensive-security SKILL.md:2
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      name: analyzing-ransomware-network-indicators
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      description: Identify ransomware-related network indicators, including C2 beaconing patterns, TOR exit node connections, data exfiltration flows, and encryption key exchange, by analyzing Zeek conn.lo
    • low Risky intent intent-offensive-security SKILL.md:7
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - ransomware
    • low Risky intent intent-offensive-security SKILL.md:54
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # Analyzing Ransomware Network Indicators
    • low Risky intent intent-offensive-security SKILL.md:58
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Before and during ransomware execution, adversaries establish C2 channels, exfiltrate data, and download encryption keys. This skill analyzes Zeek conn.log and NetFlow data to detect beaconing pattern

    Files scanned: 4. 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 "d3fend_techniques"
    • note frontmatter-key unknown frontmatter key "nist_csf"
    • note frontmatter-key unknown frontmatter key "mitre_attack"
    • note frontmatter-key unknown frontmatter key "mitre_f3"

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web, python, node) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 19 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 485 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress

    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
    • +4No input/output examples
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • -31 of 1 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +3Description length 350: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 19 items
    • +1License stated

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