SKILLEMALL.ai
GitHub ↗ RU Sign in

BC pilot-penetration-testing-setup

Deploy an automated penetration testing pipeline with 4 agents. Use this skill when: 1. User wants to set up a penetration testing or security assessment pipeline 2. User is configuring an agent as part of a vulnerability scanning workflow 3. User asks about recon, vulnerability scanning, exploit validation, or pentest reporting across agents Do NOT use this skill when: - User wants to run a single vulnerability scan (use pilot-task-parallel instead) - User wants to send a one-off security alert (use pilot-webhook-bridge instead)

ClawHub Agent Skills author: Calin Teodor v1.0.0 MIT-0 3 files body ≈ 1 906 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

ProcedureInfrastructureSecurityAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
81
Quality 40%
89
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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

    ✓ No critical or high findings

    Medium and low: 15
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash
    • low Risky intent intent-offensive-security README.md:1
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # Penetration Testing
    • low Risky intent intent-offensive-security README.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Deploy an automated penetration testing pipeline with 4 agents that perform reconnaissance, scan for vulnerabilities, validate exploitability with safe proof-of-concept tests, and generate comprehensi
    • low Risky intent intent-offensive-security README.md:24
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ### reporter (Pentest Reporter)
    • low Risky intent intent-offensive-security README.md:25
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Generates penetration test reports with findings, risk ratings, remediation steps, and executive summary. Delivers to stakeholders via Slack and webhooks.
    • low Risky intent intent-offensive-security README.md:35
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      reporter --> external : Pentest report via webhook and Slack (port 443)
    • low Risky intent intent-offensive-security skill-card.md:2
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Deploy an automated penetration testing pipeline with 4 agents. <br>
    • low Risky intent intent-offensive-security skill-card.md:14
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Developers and security engineers use this skill to configure a four-agent penetration testing workflow for reconnaissance, vulnerability scanning, exploit validation, and reporting. <br>
    • low Risky intent intent-offensive-security skill-card.md:20
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Risk: The skill configures persistent agent state for a penetration testing workflow. <br>
    • low Risky intent intent-offensive-security skill-card.md:21
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Mitigation: Install only for an approved pentest pipeline and keep a cleanup plan for ~/.pilot/setups/penetration-testing.json, handshakes, and installed role skills. <br>
    • low Risky intent intent-offensive-security SKILL.md:4
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Deploy an automated penetration testing pipeline with 4 agents.
    • low Risky intent intent-offensive-security SKILL.md:7
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      1. User wants to set up a penetration testing or security assessment pipeline
    • low Risky intent intent-offensive-security SKILL.md:9
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      3. User asks about recon, vulnerability scanning, exploit validation, or pentest reporting across agents
      detector
    • low Risky intent intent-offensive-security SKILL.md:18
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - pentest
    • low Risky intent intent-offensive-security SKILL.md:33
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # Penetration Testing Setup

    Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 1 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 4 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1906 tokens
    • 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
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 535: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 4 items
    • +4Has examples (9 code blocks)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    The skill is a coherent penetration-testing setup tool, but it configures persistent agent state and external reporting of sensitive findings without enough user-control safeguards.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026