agentsclimarketplace

Network security playbook

Skill maxwellokumu/okaudit-claude-skills/network-security/network-security-playbook

Claude-ready IT audit skills for identity, compliance, appsec, privacy, network, logging, vendor risk, and audit leadership workflows

Install
npx -y skills add maxwellokumu/okaudit-claude-skills --skill network-security-playbook

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Guide Claude through a structured network security audit covering asset discovery, firewall review, segmentation validation, threat correlation, scanning, and reporting.

SKILL.md

1.6 KB, 271 tokens by cl100k_base, as published. Nobody here has run it

Network Security Playbook

Use this skill when the user needs a step-by-step network security audit approach, wants help sequencing review activities, or needs a practical methodology for assessing network controls.

Goal

Help Claude act like a network security audit lead by breaking the review into manageable phases and keeping the work focused on exposure, segmentation, detection, and reporting quality.

Workflow

  1. Identify the environment, audit objective, and current stage of the network review.
  2. Select the relevant playbook step such as discovery, firewall review, segmentation, threat correlation, scanning, or reporting.
  3. Outline the activities, evidence, and stakeholders needed for that stage.
  4. Highlight common blind spots such as incomplete inventories, overly broad rules, weak zone definitions, or poor evidence quality.
  5. Return a concise next-step plan the user can apply immediately.

Inputs

Expected inputs from the bundled tool metadata:

  • step: Optional playbook step or phase to focus on.

Bundled Files

  • main.py contains the executable playbook helper.
  • README.md provides narrative guidance and examples.
  • skill.yaml captures the repo-native metadata for this skill.
  • sample_input may contain example prompts or stage definitions.

Guidance

Stay practical and risk-based. Keep attention on the network exposures that matter most, and connect technical findings to audit evidence and reporting needs.

What ships with it: 3 files

16.6 KB alongside SKILL.md, 1 of them executable

Gives 0 of the 12 instructions most security skills give in 271 tokens

Counted across 648 of the 828 authors here whose files we hold, read 2026-08-07

  • Parameterize all database queriesin 68 of 648, across 51 files
  • Hash passwords using bcrypt, scrypt, or argon2in 49 of 648, across 36 files
  • Apply rate limiting to authentication endpointsin 48 of 648, across 24 files
  • Configure security headersin 35 of 648, across 19 files
  • Validate all inputsin 32 of 648, across 24 files
  • Validate all external input at the system boundaryin 29 of 648, across 19 files
  • Run containers as a non-root userin 28 of 648, across 15 files
  • Use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
  • Run dependency audits before every releasein 21 of 648, across 10 files
  • Encode output to prevent cross-site scriptingin 21 of 648, across 11 files
  • Copy dependencies before source codein 20 of 648, across 9 files
  • Store secrets in environment variablesin 20 of 648, across 18 files

Said here and by no other author read

  • identify environment, objective, and review stage
  • select relevant playbook step
  • outline activities, evidence, and stakeholders
  • highlight common blind spots
  • return a concise next-step plan
  • stay practical and risk-based

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.