shimmy-tool-nmap

Maintain the Nmap Shimmy tool while preserving context-first workflows and explicit opt-ins.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-nmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shimmy-tool-nmap
Source: https://github.com/wadebee/shimmy/tree/main/tools/nmap/agent
Command: npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-nmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you use and maintain the context-first Nmap tool inside Shimmy without losing track of the required repository guidance, version-specific behavior, or safety opt-ins.

Core Features & Use Cases

  • Version-aware maintenance: Works with the Nmap tool’s own guide and version context so changes stay aligned with the intended runtime behavior.
  • Explicit opt-in handling: Preserves LAN, host-network, privilege, and capability opt-ins so network scans remain deliberate and controlled.
  • Repository navigation aid: Directs you to the shared and tool-specific context files needed to understand how Nmap is packaged and operated.

Quick Start

Use this skill to inspect and update the Nmap Shimmy tool while preserving the required context and explicit network and privilege opt-ins.

Frequently Asked Questions about shimmy-tool-nmap

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

FAQPage Schema
How do I run Nmap safely with explicit network and privilege opt-ins?

To run Nmap safely, you must preserve explicit LAN, host-network, privilege, and capability opt-ins by reading the shared repository and tool-specific context files, ensuring network scans remain deliberate and controlled.

What does context-first network scanning mean for tool maintenance?

Context-first network scanning means maintaining Nmap's runtime behavior by preserving its version-specific operating guidance and repository context, keeping scan configurations aligned with intended safety opt-ins.

Do I need to read repository context files before configuring an Nmap scan?

Yes, you must read the shared repository context and the Nmap tool context files to understand how Nmap is packaged and to keep LAN, host-network, privilege, and capability opt-ins intact.

How do I review Nmap scan configurations without losing version-specific guidance?

Review Nmap scan configurations by applying version-aware maintenance that works with the tool's own guide and version context, ensuring changes stay aligned with intended runtime behavior and explicit opt-ins.

When should I preserve privilege and capability opt-ins during Nmap repository updates?

You should always preserve privilege and capability opt-ins during repository updates to ensure network scans remain deliberate, controlled, and aligned with the context-first workflow.