Agent skill · laurigates
docs-verify-machine-facts
Verify machine-read values (scutil, route, ifconfig, local config) against the authoritative IaC before publishing. Use when org docs quote DNS names, IPs, endpoints, or versions read off this host.
What it needs
About 3k tokens when loaded.
What this skill does
Verify Machine-Read Facts Against the Org Source-of-Truth Before Publishing When documenting infrastructure from values read off your own machine — ifconfig, scutil --dns, route get, netstat -rn, defaults read, a local config file — those readings can carry personal or host-specific artifacts that are not org facts. Publishing them to shared documentation silently passes off your home network (or a stale local override, or another VPN) as the organization's configuration. The failure mode A diagnostic session reads the live state of a tool on your laptop, the output looks authoritative, and environment-specific lines get lifted verbatim into an org doc: 1. You run scutil --dns / route get to investigate a VPN/tunnel. 2. The output interleaves multiple resolvers and routes — the org tunnel's and your home network's, your other VPN's, a local /etc/hosts override. 3. You document the interesting values without separating "this is the org's" from "this is mine." 4. The doc now tells every reader that the org's internal DNS domain is intra.lakuz.com with resolvers 100.95.0.251–.254 — which was the author's home LAN, not the org's anything. The tell: the value is specific and plausible, so reviewers don't question it — it reads as researched fact. The leak surfaces only when someone who knows the real environment says "that's not ours." Canonical break (2026-06): an FVH Twingate troubleshooting DevGuide published intra.lakuz.com + 100.95.0.x as the org's internal DNS. Both were the author's home network, picked up from a scutil --dns dump where the home resolver sat in resolver #1 above the Twingate overlay. The real FVH resource domains (.dataportal.fi, .fvh.io, .cluster.local) live in twingate/resources.tf. Corrected in a follow-up commit after the user caught it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills laurigates/docs-verify-machine-facts