disabled-wireless-policy

Governs wireless security assessment authorization and safety boundaries for RF-spectrum testing and audits.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill disabled-wireless-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disabled-wireless-policy
Source: https://github.com/salmanabdurrahman/pi-pentest-agent/tree/main/skills/disabled-wireless-policy
Command: npx skills add https://github.com/salmanabdurrahman/pi-pentest-agent --skill disabled-wireless-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents unauthorized or dangerous wireless testing by enforcing strict regulatory and safety boundaries, ensuring all RF-related activities are documented, authorized, and risk-assessed.

Core Features & Use Cases

  • Policy Enforcement: Provides a structured refusal and guidance framework for high-risk wireless requests.
  • Safe Alternatives: Redirects users toward non-disruptive security assessments like configuration audits and architecture reviews.
  • Use Case: When a user requests a wireless penetration test, this skill guides them through the necessary authorization gates and suggests safer, passive alternatives like WPA Enterprise configuration reviews.

Quick Start

Ask the pentest agent to explain the wireless testing policy and the required authorization steps for a new engagement.

Frequently Asked Questions about disabled-wireless-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What authorization is required for a wireless penetration test?

Wireless penetration testing requires strict regulatory compliance, documented per-engagement consent, and formal risk approval before any active RF-spectrum testing or infrastructure audit is permitted.

How do I get approval to start a wireless network security assessment?

To start a wireless network security assessment, you must pass through structured authorization gates by obtaining documented per-engagement consent and risk approval, ensuring regulatory compliance before active workflows begin.

Can I perform RF-spectrum testing without formal risk approval?

RF-spectrum testing without formal risk approval is refused by policy enforcement, which requires documented authorization to prevent unauthorized or dangerous wireless testing activities.

What are safe alternatives to active wireless penetration testing?

Safe alternatives to active wireless testing include non-disruptive security assessments like configuration audits, architecture reviews, and WPA Enterprise configuration reviews that bypass active RF-spectrum requirements.

When do I need documented consent for rogue access point investigations?

Documented consent for rogue access point investigations is required whenever active workflows are requested, ensuring per-engagement authorization and regulatory compliance before proceeding with the assessment.

Why does wireless security policy enforcement block my RF testing request?

Wireless security policy enforcement blocks RF testing requests lacking documented authorization, applying a structured refusal framework to prevent high-risk wireless activities until regulatory compliance and risk approval are verified.