SKILLEMALL.ai

CC performing-physical-intrusion-assessment

Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deployment, and security-guard procedure testing. Use as part of a full-scope red team engagement to evaluate physical security controls and their path to network access, always under signed client authorization.

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

Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing…

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

AnalyzerSecurityAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
93
Quality 40%
75
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 · 7

    ✓ No critical or high findings

    Medium and low: 7
    • low Risky intent intent-offensive-security references/standards.md:21
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **ISACA Physical Penetration Testing** white paper (2023)
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      description: Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deploymen
    • low Risky intent intent-offensive-security SKILL.md:13
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - physical-pentest
    • low Risky intent intent-offensive-security SKILL.md:39
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      Physical intrusion assessment evaluates an organization's physical security controls by attempting to gain unauthorized access to facilities, server rooms, and restricted areas. This includes tailgati
      detector
    • low Risky intent intent-offensive-security SKILL.md:151
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # Provides SSH reverse tunnel back to C2 server
    • low Risky intent intent-offensive-security SKILL.md:218
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - ISACA Physical Penetration Testing White Paper (2023)

    A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

    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"

    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. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 56 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1828 tokens
    • low 13 top-level sections: this looks like several domains in one skill

    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 390: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 56 items
    • +4Has examples (3 code blocks)
    • +1License stated

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