network-report-documents

Generates change-record Word documents, audit workbooks, executive decks, and filled PDF forms from real network data.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill network-report-documents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: network-report-documents
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/network-report-documents
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill network-report-documents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Network operators need audit-ready deliverables — change records, interface audit spreadsheets, executive decks, and filled PDF forms — but assembling them by hand risks fabricated or stale values reaching change advisory boards and auditors. This Skill composes those four document types strictly from real, tagged device and ticket data, marking gaps explicitly instead of inventing figures.

Core Features & Use Cases

  • Change Record Documents (.docx): Builds a change record from a real ServiceNow CR plus live device state, with every value tagged to its source and a hard stop if the CR does not exist or is unapproved.
  • Interface/Config Audit Workbooks (.xlsx): Produces spreadsheets with separate administrative and operational state columns, and records failed devices as marked rows rather than silently omitting them.
  • Executive Summary Decks (.pptx): Assembles findings, figures, and an existing topology diagram into slides with visible source attribution and detail references.
  • PDF Form Filling: Inspects a PDF's real field names first, fills only fields with genuine data, and reports unfilled and unmatched fields to the operator.
  • Use Case: An operator asks for a change record for CHG0012345 with the current state of fgt-01; the Skill pulls the CR from ServiceNow and device state from FortiGate queries, then renders a sourced Word document.

Quick Start

Ask the agent to generate a change record document for a specific ServiceNow change request including the current state of a named device.

Frequently Asked Questions about network-report-documents

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

FAQPage Schema
How do I generate a change record document from a ServiceNow CR?

Provide the change request number and target device; the Skill reads the CR via servicenow-change-workflow and device state via FortiGate, multivendor CLI, or pyATS queries, then renders a tagged .docx. If the CR does not exist or is unapproved, it stops rather than producing a placeholder document.

How do I build an interface audit spreadsheet for network devices?

Ask for an interface audit workbook and the Skill queries devices with fgt_list_interfaces, multivendor-device-query, or pyATS, then writes an .xlsx with separate administrative and operational state columns. Devices that fail to respond appear as marked failed rows, never silently omitted.

Can the Skill fill a PDF form automatically?

Yes, but it always runs pdf_inspect_form first to get the real field names, then maps tagged values onto those exact names. Fields with no data are left genuinely empty, and the operator is told which fields remain unfilled and which values matched nothing.

What happens when a device does not respond during document generation?

The Skill sends an explicit unavailable marker instead of inventing a value, so the document states the device did not answer. In workbooks, failed devices appear as marked rows with attempted, returned, and failed counts in a banner.

Does this Skill create or update ServiceNow change tickets?

No. It reads change records in read-only fashion to render documents and never creates, updates, or closes tickets. Ticket modifications belong to the servicenow-change-workflow skill, and sending finished documents belongs to the Slack or WebEx delivery skills.

Can it draw the topology diagram for an executive deck?

No. Diagrams must be produced first by a dedicated diagram skill such as drawio-diagram, markmap-viz, uml-diagram, or threejs-network-viz. This Skill only embeds the existing diagram file, and paths outside the workspace output directory are refused.