network-report-documents
Network Report Documents
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.
The rule that governs all four
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.