SKILLEMALL.ai

CC performing-dark-web-monitoring-for-threats

Dark web monitoring involves systematically scanning Tor hidden services, underground forums, paste sites, and dark web marketplaces to identify threats targeting an organization, including leaked cre

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 8 files · 2 scripts body ≈ 2 323 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Dark web monitoring involves systematically scanning Tor hidden services, underground forums, paste sites, and dark web marketplaces to identify threats…

As a process C 57/100 · Has gaps — weak spots: result and completion, failures and branches, progress reporting

ProcedurePeople and hiringPersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
91
Quality 40%
75
Run on models
none yet
Process rating
C
57/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

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

    ✓ No critical or high findings

    Medium and low: 9
    • low Risky intent intent-offensive-security assets/template.md:19
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ## Ransomware Group Mentions
    • low Risky intent intent-offensive-security references/standards.md:21
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | Leak Sites | Ransomware data publication | LockBit, BlackCat, Royal blogs |
    • low Risky intent intent-offensive-security references/standards.md:27
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - Credential harvesting for defensive purposes requires clear policy
    • low Risky intent intent-offensive-security references/workflows.md:19
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ## Workflow 3: Ransomware Leak Monitoring
    • low Risky intent intent-offensive-security SKILL.md:61
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **Ransomware Leak Sites**: Blogs where ransomware groups post stolen data from victims
    • low Risky intent intent-offensive-security SKILL.md:180
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ### Step 3: Monitor Ransomware Leak Sites
    • low Risky intent intent-offensive-security SKILL.md:184
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      """Check known ransomware group leak sites for organization mentions."""
      detector
    • low Risky intent intent-offensive-security SKILL.md:185
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # Use Ransomwatch API (clearnet aggregator of ransomware leak sites)
    • low Risky intent intent-offensive-security SKILL.md:237
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      f"and {ransom_count} ransomware group mentions for {organization}."
      detector

    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 57/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
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 37 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2323 tokens
    • 100Running it twice. No mutating operations

    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
    • -32 of 2 scripts are never mentioned in SKILL.md
    • +2Single-language instructions
    • +3Description length 200: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 37 items
    • +4Has examples (4 code blocks)
    • +1License stated

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