SKILLEMALL.ai
GitHub ↗ RU Sign in

CC conducting-spearphishing-simulation-campaign

Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized engagements to gain initial access via personalized phishing against specific individuals, distinct from broad campaigns.

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

Run a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK…

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

ProcedureMarketingInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
80/100
safety, quality, tests
Safety 60%
86
Quality 40%
71
Run on models
none yet
Process rating
C
51/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 · 14

    ✓ No critical or high findings

    Medium and low: 14
    • low Risky intent intent-offensive-security assets/template.md:11
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | Red Team Lead | [NAME] |
    • low Risky intent intent-offensive-security assets/template.md:158
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      [Include screenshot of credential harvesting page]
    • low Risky intent intent-offensive-security references/api-reference.md:15
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | POST | `/api/campaigns/` | Launch new phishing campaign |
    • low Risky intent intent-offensive-security references/standards.md:11
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | T1598.002 | Phishing for Information: Spearphishing Attachment | Credential harvesting attachments |
    • low Risky intent intent-offensive-security references/standards.md:12
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | T1598.003 | Phishing for Information: Spearphishing Link | Credential harvesting links |
    • low Risky intent intent-offensive-security references/workflows.md:25
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Name: Red Team SMTP
    • low Risky intent intent-offensive-security references/workflows.md:77
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Sending Profile: Red Team SMTP
    • low Risky intent intent-offensive-security references/workflows.md:194
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      1. Send initial test email to red team operator
    • low Risky intent intent-offensive-security references/workflows.md:235
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      3. C2 beacon screenshot showing initial callback
    • low Risky intent intent-offensive-security SKILL.md:85
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - Familiarity with red teaming concepts and tools
    • low Risky intent intent-offensive-security SKILL.md:126
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - QR codes linking to credential harvesting pages
    • low Risky intent intent-offensive-security SKILL.md:136
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      5. Deploy credential harvesting pages with SSL certificates
    • low Risky intent intent-offensive-security SKILL.md:158
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | GoPhish | Phishing campaign management | Open Source |
    • low Risky intent intent-offensive-security SKILL.md:159
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | Evilginx2 | Real-time credential harvesting with MFA bypass | Open Source |

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

    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
    • -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 418: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 60 items
    • +1License stated

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