The Script Catalog: A Searchable Shelf of Ready-to-Run Network Scripts
Skip the blank editor. Find a vetted script, set its parameters, and run.
Most automation never gets written because starting from nothing is the hardest part. The Script Catalog removes that barrier: a curated shelf of ready-to-run scripts, each one parameterised, documented, and wired into the platform's safe execution path.
What lives in the catalog
Each entry pairs a clear description with the inputs it needs and the vendors it supports. You see at a glance what a script does, whether it only reads state or changes it, and what parameters to supply — before you commit to running it.
- Task-aligned grouping — diagnostics, verification, provisioning, and backup.
- Typed parameters — the catalog renders the right form for each script.
- Safety class — read-only scripts run freely; mutating ones require confirmation.
- Previews — see a script's intent and sample output before executing.
Find, preview, run
- Search or filter to the task you have in mind.
- Open a script to read what it does and which parameters it expects.
- Fill in the parameters and run it through the platform's streaming execution.
Why a catalog beats a folder of files
Scripts in a shared drive rot: no parameters, no safety metadata, no idea who last ran one or what it touched. The catalog gives every script structure — typed inputs, a safety class, and an audited run path — so reuse is safe instead of risky.
Was this helpful?
Generate scripts for the task covered in this post
Describe what you need and NAPT writes production-ready automation in Netmiko, NAPALM, or Nornir.
Open Script Generator →Related posts
Compliance Without the Spreadsheet: Continuous Posture for Network Devices
The Compliance panel runs your hardening rule packs across the fleet, scores devices, and tracks drift so audits start with evidence, not promises.
Read →Inventory & IPAM: The Source of Truth Your Scripts Actually Trust
Upload a CSV, connect to NetBox, or generate an IP range — Inventory normalises every source into the same validated row shape for the platform.
Read →Runbooks: Living Documents That Run
Runbooks combine narrative, parameters, and executable scripts so on-call engineers stop choosing between reading the doc and fixing the problem.
Read →