Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/network-report-documents
The four standard NetClaw document compositions — a change-record Word document from a real ServiceNow CR plus device state, an interface/config audit workbook from real device queries, an executive summary deck with an embedded topology diagram, and a required PDF form filled from real data.
Passed 20 of 23 test cases with the skill, and 6 of 23 without it.
and 16 more in the full report
15 fixed5 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
Send the output report file `/tmp/reports/chg0012345_record.docx` to the `#network-ops` channel in Slack.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to send the document to Slack. | Missed | Passed |
The instructions your model reads when the skill loads.
Four compositions built on document-mcp. This skill owns what goes in the document; the server owns
writing it. Read document-generation for the tool surface, the tagged
value shapes, and the stated limits.
A document must never fabricate to fill a blank.
Never infer, estimate, interpolate, or carry forward a stale value to complete a document. The server structurally cannot fabricate — it only renders tagged values — but you can, by inventing a plausible figure while assembling the request. That half of the discipline lives here and nowhere else.
If a device did not answer, send {"unavailable": "device did not answer"}. A change record that says
"NOT AVAILABLE — device did not answer" is useful. One with a confident wrong number is worse than none,
because a change advisory board will act on it and nobody will re-derive it.
.docx)"Generate a change record for CHG0012345 with the current state of fgt-01."
Feed it from: servicenow-change-workflow for the CR (read-only — this composition never creates or
updates a ticket), plus fortigate-ops / multivendor-cli / pyats for device state.
Shape:
| Section | Block | Notes |
|---|---|---|
| Change details | keyvalue | CR number, state, requester, window, risk — each tagged with src: servicenow_get_change |
| Pre-change state | keyvalue + table | Real device output, tagged per device |
| Topology | image | Only if a diagram skill already produced one |
| Rollback | paragraph | Narrative — put no figures here |
If the CR does not exist or is not approved, say so and stop. Do not produce a document with an invented CR — the document would outlive the conversation that knew it was a placeholder.
If ServiceNow is not configured, you may still produce the device half, but state in the response that the CR half was hand-supplied and unverified.
test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.