Agent skill

Building Soc Playbook For Ransomware

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and…

Apache-2.0Auto-check passedSecurity

Install Building Soc Playbook For Ransomware

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-soc-playbook-for-ransomware -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills building-soc-playbook-for-ransomware --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/building-soc-playbook-for-ransomware .claude/skills/building-soc-playbook-for-ransomware && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
building-soc-playbook-for-ransomware
GitHub stars
34k
Token cost
~2.9k tokens
SKILL.md length
535 words
Files
4 (incl. scripts, references)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and…

  • Works in 6 steps: Define Detection Triggers → Build Triage Decision Tree → Containment Procedures → …
  • SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques
  • SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
  • Runs Python scripts from its folder; calls curl; reaches api.crowdstrike.com and api.securitycenter.microsoft.com

What it does

Building Soc Playbook For Ransomware is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).

It sits in Security, covering Security operations and Incident response. It works with Splunk. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques
  • Tasks that involve Security operations
  • Tasks that involve Incident response

Example prompts

  • “Use the building-soc-playbook-for-ransomware skill to build a structured SOC incident response playbook for ransomware attacks covering detection…”
  • “/building-soc-playbook-for-ransomware”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Define Detection Triggers
  2. Build Triage Decision Tree
  3. Containment Procedures
  4. Evidence Collection and Preservation
  5. Eradication and Recovery
  6. Post-Incident Documentation

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.crowdstrike.com
    • api.securitycenter.microsoft.com

    Also links to:

    • id-ransomware.malwarehunterteam.com
    • nomoreransom.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Building Soc Playbook For Ransomware loads about 2.9k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 535 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 535 words, ~2,924 tokens.

Download SKILL.mdSave it as .claude/skills/building-soc-playbook-for-ransomware/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
building-soc-playbook-for-ransomware
description
Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.
domain
cybersecurity
subdomain
soc-operations
tags
soc, ransomware, incident-response, playbook, nist, mitre-attack, containment
mitre_attack
T1486, T1490, T1489, T1566, T1059.001
mitre_f3.version
1.1
mitre_f3.tactics
initial-access, monetization
version
1.0
author
mahipal
license
Apache-2.0
d3fend_techniques
Platform Hardening, Restore Object, Restore Configuration, Restore Software, Software Update

Building SOC Playbook for Ransomware

When to Use

Use this skill when:

  • SOC teams need a standardized ransomware response playbook for Tier 1-3 analysts
  • An organization lacks documented procedures for ransomware containment and recovery
  • Tabletop exercises reveal gaps in ransomware response coordination
  • Compliance requirements (NIST CSF, ISO 27001) mandate documented incident playbooks

Do not use during an active ransomware incident as the sole guide — have pre-built playbooks tested and rehearsed before incidents occur.

Prerequisites

  • SIEM platform (Splunk ES, Elastic Security, or Sentinel) with endpoint and network data
  • EDR solution (CrowdStrike, SentinelOne, or Microsoft Defender for Endpoint) with network isolation capability
  • Backup infrastructure with tested recovery procedures and offline/immutable backups
  • Communication plan with legal, executive leadership, and external IR retainer contacts
  • MITRE ATT&CK knowledge for ransomware technique chains

Workflow

Step 1: Define Detection Triggers

Create SIEM detection rules for early ransomware indicators:

Mass File Encryption Detection (Splunk):

spl
index=sysmon EventCode=11
| bin _time span=1m
| stats dc(TargetFilename) AS unique_files, values(TargetFilename) AS sample_files by Computer, Image, _time
| where unique_files > 100
| eval suspicious_extensions = if(match(mvjoin(sample_files, ","), "\.(encrypted|locked|crypt|enc|ransom)"), "YES", "NO")
| where suspicious_extensions="YES" OR unique_files > 500
| sort - unique_files

Shadow Copy Deletion (T1490):

spl
index=wineventlog sourcetype="WinEventLog:Security" OR index=sysmon EventCode=1
(CommandLine="*vssadmin*delete*shadows*" OR CommandLine="*wmic*shadowcopy*delete*"
 OR CommandLine="*bcdedit*/set*recoveryenabled*no*" OR CommandLine="*wbadmin*delete*catalog*")
| table _time, Computer, User, ParentImage, Image, CommandLine

Ransomware Note File Creation:

spl
index=sysmon EventCode=11
TargetFilename IN ("*README*.txt", "*DECRYPT*.txt", "*RANSOM*.txt", "*RECOVER*.html", "*HOW_TO*.txt")
| stats count by Computer, Image, TargetFilename
| where count > 5

Elastic Security EQL variant:

eql
sequence by host.name with maxspan=2m
  [process where event.type == "start" and
    process.args : ("*vssadmin*", "*delete*", "*shadows*")]
  [file where event.type == "creation" and
    file.name : ("*README*DECRYPT*", "*RANSOM*", "*HOW_TO_RECOVER*")]
Step 2: Build Triage Decision Tree
RANSOMWARE ALERT TRIAGE
│
├── Is encryption actively occurring?
│   ├── YES → IMMEDIATE: Isolate host from network (Step 3)
│   │         Do NOT power off (preserve memory for forensics)
│   └── NO → Is this a pre-encryption indicator?
│       ├── Shadow copy deletion → HIGH PRIORITY: Isolate and investigate
│       ├── Known ransomware hash → HIGH PRIORITY: Block hash, scan enterprise
│       └── Suspicious process behavior → MEDIUM: Investigate, prepare isolation
│
├── How many hosts affected?
│   ├── Single host → Contained incident, follow host isolation procedure
│   ├── Multiple hosts (2-10) → Escalate to Tier 2, begin enterprise-wide scan
│   └── Enterprise-wide (>10) → Activate full IR team, engage external retainer
│
└── Is data exfiltration confirmed?
    ├── YES → Double extortion scenario, engage legal for breach notification
    └── NO/UNKNOWN → Check for Cobalt Strike/C2 beacons, review outbound transfers
Step 3: Containment Procedures

Network Isolation via EDR (CrowdStrike Falcon):

bash
# Isolate host using CrowdStrike Falcon API
curl -X POST "https://api.crowdstrike.com/devices/entities/devices-actions/v2?action_name=contain" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"ids": ["device_id_here"]}'

Network Isolation via Microsoft Defender for Endpoint:

powershell
# Isolate machine via MDE API
$headers = @{Authorization = "Bearer $token"}
$body = @{Comment = "Ransomware containment - IR-2024-0500"; IsolationType = "Full"} | ConvertTo-Json
Invoke-RestMethod -Uri "https://api.securitycenter.microsoft.com/api/machines/$machineId/isolate" `
    -Method Post -Headers $headers -Body $body -ContentType "application/json"

Firewall Emergency Rules:

# Palo Alto — Block SMB lateral spread
set rulebase security rules RansomwareContainment from Trust to Trust
set rulebase security rules RansomwareContainment application ms-ds-smb
set rulebase security rules RansomwareContainment action deny
set rulebase security rules RansomwareContainment disabled no
commit

Active Directory Emergency Actions:

powershell
# Disable compromised account
Disable-ADAccount -Identity "compromised_user"

# Reset Kerberos TGT (if domain admin compromised)
# WARNING: This resets krbtgt and requires two resets 12+ hours apart
Reset-KrbtgtKeys -Server "DC-PRIMARY" -Force

# Block lateral movement by disabling remote services
Set-Service -Name "RemoteRegistry" -StartupType Disabled -Status Stopped
Step 4: Evidence Collection and Preservation

Collect forensic artifacts before remediation:

powershell
# Capture running processes and network connections
Get-Process | Export-Csv "C:\IR\processes_$(hostname).csv"
Get-NetTCPConnection | Export-Csv "C:\IR\netstat_$(hostname).csv"

# Capture memory dump (if host still running)
winpmem_mini_x64.exe C:\IR\memory_$(hostname).raw

# Collect ransomware artifacts
Copy-Item "C:\Users\*\Desktop\*README*" "C:\IR\ransom_notes\" -Recurse
Copy-Item "C:\Users\*\Desktop\*.encrypted" "C:\IR\encrypted_samples\" -Force

# Capture event logs
wevtutil epl Security "C:\IR\Security_$(hostname).evtx"
wevtutil epl System "C:\IR\System_$(hostname).evtx"
wevtutil epl "Microsoft-Windows-Sysmon/Operational" "C:\IR\Sysmon_$(hostname).evtx"
Step 5: Eradication and Recovery

Identify ransomware variant:

Enterprise-wide IOC scan in Splunk:

spl
index=sysmon (EventCode=1 OR EventCode=11 OR EventCode=3)
(TargetFilename="*ransomware_binary_name*" OR sha256="KNOWN_HASH"
 OR DestinationIp="C2_IP_ADDRESS" OR CommandLine="*malicious_command*")
| stats count by Computer, EventCode, Image, CommandLine
| sort - count

Recovery from backups:

  1. Verify backup integrity (offline/immutable backups not affected)
  2. Rebuild affected systems from known-good images
  3. Restore data from last clean backup
  4. Validate restored systems before reconnecting to network
  5. Monitor restored systems for 72 hours for reinfection
Step 6: Post-Incident Documentation

Structure the playbook conclusion with lessons learned:

POST-INCIDENT REVIEW TEMPLATE
1. Timeline of events (detection to full recovery)
2. Initial access vector identification
3. Dwell time analysis (time from initial compromise to encryption)
4. Detection gaps identified
5. Response effectiveness metrics (MTTD, MTTC, MTTR)
6. Playbook improvements recommended
7. New detection rules deployed
8. Backup and recovery procedure updates
Show full SKILL.md (244 more words)Show less

Key Concepts

TermDefinition
Double ExtortionRansomware tactic combining data encryption with data theft, threatening public release if ransom unpaid
Dwell TimeDuration between initial compromise and detection — ransomware operators average 5-9 days before encryption
MTTCMean Time to Contain — time from detection to successful isolation of affected systems
Kill ChainRansomware progression: Initial Access -> Execution -> Persistence -> Privilege Escalation -> Lateral Movement -> Collection -> Exfiltration -> Impact
Immutable BackupBackup storage that cannot be modified or deleted for a defined retention period (WORM storage)
RTO/RPORecovery Time Objective / Recovery Point Objective — maximum acceptable downtime and data loss thresholds

Tools & Systems

  • CrowdStrike Falcon / SentinelOne: EDR platforms with network isolation, process kill, and threat hunting capabilities
  • Splunk ES / Elastic Security: SIEM platforms for detection rule deployment and enterprise-wide IOC scanning
  • ID Ransomware: Online service identifying ransomware variants from encrypted file samples and ransom notes
  • No More Ransom Project: Europol-backed initiative providing free decryption tools for known ransomware families
  • Veeam / Rubrik: Enterprise backup solutions with immutable backup support and instant recovery capabilities

Common Scenarios

  • LockBit Attack: Detected via SMB lateral movement and mass file encryption — isolate, scan for Cobalt Strike beacons
  • BlackCat/ALPHV: Detected via ransomware note creation — check for data exfiltration via Rclone or Mega upload
  • Conti/Royal: Detected via shadow copy deletion — check for prior BazarLoader/Emotet initial access
  • RansomHub: Detected via anomalous process execution — investigate for compromised VPN or RDP credentials
  • Play Ransomware: Detected via service account abuse — audit AD for newly created accounts and group membership changes

Output Format

RANSOMWARE PLAYBOOK EXECUTION — IR-2024-0500
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Phase 1 - Detection:
  Alert:      Mass file encryption detected on FILESERVER-03
  Variant:    LockBit 3.0 (confirmed via ID Ransomware)
  MTTD:       12 minutes from first encryption to SOC alert

Phase 2 - Containment:
  [DONE] FILESERVER-03 isolated via CrowdStrike at 14:35 UTC
  [DONE] SMB blocked enterprise-wide via firewall emergency rule
  [DONE] Compromised service account disabled in AD
  MTTC:       23 minutes

Phase 3 - Eradication:
  [DONE] 3 additional hosts with C2 beacon identified and isolated
  [DONE] Cobalt Strike C2 domain (c2[.]evil[.]com) sinkholed
  [DONE] Enterprise-wide IOC scan completed — no additional infections

Phase 4 - Recovery:
  [DONE] FILESERVER-03 rebuilt from gold image
  [DONE] Data restored from immutable Veeam backup (RPO: 4 hours)
  [DONE] Systems monitored 72 hours — no reinfection
  MTTR:       18 hours

Total Affected: 1 server, 3 workstations
Data Loss:      4 hours of file modifications (backup RPO)
Exfiltration:   No evidence of data exfiltration confirmed

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/building-soc-playbook-for-ransomware of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Building Soc Playbook For Ransomware next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Building Soc Playbook For Ransomware compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Building Soc Playbook For Ransomware this skillmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: PassApache-2.0
Msp HelpdeskRTFM-IT-Services-LLC/msp-claude-skills115—~3.3kAutomated safety check: PassCustom licence
Detection SigmaAgentSecOps/SecOpsAgentKit2201 repos~4kAutomated safety check: PassCustom licence
Incident Triagebriiirussell/cybersecurity-skills413—~1.5kAutomated safety check: NotesMIT
Siem Detectionbriiirussell/cybersecurity-skills413—~2.6kAutomated safety check: NotesMIT
Doca ArgusNVIDIA/skills3.6k—~4.8kAutomated safety check: PassApache-2.0

Similar skills

  • Msp Helpdesk

    RTFM-IT-Services-LLC/msp-claude-skills

    A skill your agent uses for anything about how your MSP runs day-to-day support: setting or questioning a ticket's priority, response and resolution targets, "the client says everything is down"…

    115 GitHub stars~3.3k tokensUpdated 8 days ago
    SecurityAuto-check passed
  • Detection Sigma

    AgentSecOps/SecOpsAgentKit

    Generic detection rule creation and management using Sigma, the universal SIEM rule format.

    220 GitHub starsUsed in 1 repo~4k tokens
    SecurityAuto-check passed
  • Incident Triage

    briiirussell/cybersecurity-skills

    Guide rapid triage and initial response to security incidents following NIST SP 800-61 methodology.

    413 GitHub stars~1.5k tokensUpdated 4 mo ago
    SecurityAuto-check: notes
  • Siem Detection

    briiirussell/cybersecurity-skills

    Engineer and audit SIEM detection rules — log source coverage, Sigma / KQL / SPL / Elastic query authoring, MITRE ATT&CK mapping, false-positive tuning, and detection-as-code workflows.

    413 GitHub stars~2.6k tokensUpdated 4 mo ago
    SecurityAuto-check: notes
  • Doca Argus

    NVIDIA/skills

    Official

    A skill your agent uses when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for…

    3.6k GitHub stars~4.8k tokensUpdated yesterday
    SecurityAuto-check passed
  • Hunting Threats

    trilwu/secskills

    Run hypothesis-driven threat hunts across endpoint, network, cloud, and identity telemetry using stack counting, outlier analysis, and ATT&CK-based hypotheses, with SIEM query patterns for Splunk…

    157 GitHub stars~3.5k tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Building Soc Playbook For Ransomware

What does Building Soc Playbook For Ransomware do?

Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and…. Building Soc Playbook For Ransomware is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees.

When should I use Building Soc Playbook For Ransomware?

Building Soc Playbook For Ransomware fits situations like: SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques; tasks that involve Security operations; tasks that involve Incident response.

How do I install Building Soc Playbook For Ransomware in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-soc-playbook-for-ransomware -a claude-code`. Or copy the skill folder (skills/building-soc-playbook-for-ransomware in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/building-soc-playbook-for-ransomware in your project. Claude Code loads it when a task matches its description.

How do I install Building Soc Playbook For Ransomware in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-soc-playbook-for-ransomware -a codex`. Or copy the skill folder (skills/building-soc-playbook-for-ransomware in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/building-soc-playbook-for-ransomware in your project. Codex loads it when a task matches its description.

Can I use Building Soc Playbook For Ransomware in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill building-soc-playbook-for-ransomware -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/building-soc-playbook-for-ransomware, .gemini/skills/building-soc-playbook-for-ransomware, .github/skills/building-soc-playbook-for-ransomware and .opencode/skills/building-soc-playbook-for-ransomware in your project.

What does Building Soc Playbook For Ransomware need to run?

Going by SKILL.md and its folder, Building Soc Playbook For Ransomware needs Python for the scripts in its folder and the command-line tools its instructions call (curl). Our summary lists: Python 3.

Does Building Soc Playbook For Ransomware access the network?

SKILL.md names 4 domains. In commands or code: api.crowdstrike.com and api.securitycenter.microsoft.com; the agent is likely to contact these when it follows the instructions. As links in the text: id-ransomware.malwarehunterteam.com and nomoreransom.org. This is read from the text; nothing was executed.

Is Building Soc Playbook For Ransomware safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Building Soc Playbook For Ransomware use?

Building Soc Playbook For Ransomware is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Building Soc Playbook For Ransomware use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 555 tokens, read only when the agent opens those files.

What are the alternatives to Building Soc Playbook For Ransomware?

Skills that share tags, products or a category with Building Soc Playbook For Ransomware: Msp Helpdesk (RTFM-IT-Services-LLC/msp-claude-skills, 115 stars), Detection Sigma (AgentSecOps/SecOpsAgentKit, 220 stars), Incident Triage (briiirussell/cybersecurity-skills, 413 stars) and Siem Detection (briiirussell/cybersecurity-skills, 413 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Building Soc Playbook For Ransomware?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.