CB analyzing-ransomware-encryption-mechanisms
Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware cryptanalysis, encryption analysis, key recovery assessment, or ransomware decryption feasibility.
Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify…
As a process B 66/100 · Nearly there — weak spots: failures and branches, progress reporting
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 · 10
✓ No critical or high findings
Medium and low: 10
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# API Reference: Ransomware Encryption Mechanism Analysis
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:17Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# AES-ECB (weak mode used by some ransomware)
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:43Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)pe = pefile.PE("ransomware.exe")quoted -
low Risky intent
intent-offensive-securityreferences/api-reference.md:91Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## Known Ransomware Encryption Schemes
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:108Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### Common Ransomware File Layout
-
low Risky intent
intent-offensive-securitySKILL.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)name: analyzing-ransomware-encryption-mechanisms
-
low Risky intent
intent-offensive-securitySKILL.md:4Offensive-security / dual-use content (legitimate for authorised testing; review intended use)routines used by ransomware families to assess decryption feasibility, identify
-
low Risky intent
intent-offensive-securitySKILL.md:6Offensive-security / dual-use content (legitimate for authorised testing; review intended use)and hybrid encryption schemes. Activates for requests involving ransomware cryptanalysis,
-
low Risky intent
intent-offensive-securitySKILL.md:7Offensive-security / dual-use content (legitimate for authorised testing; review intended use)encryption analysis, key recovery assessment, or ransomware decryption feasibility.
-
low Risky intent
intent-offensive-securitySKILL.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- ransomware
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack" - note
frontmatter-keyunknown frontmatter key "mitre_f3"
Process rating: all ten parameters 66/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3231 tokens
- 100Running it twice. Mutating operations check current state
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
- -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
- +4Description says when NOT to use the skill
- +3Description length 405: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.