Forward snapshot assurance, path search, app-aware path search, NQE, checks, vulnerabilities, diffs, configuration, lifecycle, collection, and topology workflows through the upstream forward-mcp server.
SkillScore82Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/17/2026
What it changes
Passed 16 of 19 test cases with the skill, and 3 of 19 without it.
Without skill14%
With skill82%
Checks it passed that the model alone missed
Specifies starting the execution with start_nqe_query
Specifies executing the query using run_nqe_query_by_id
Recommends starting collection with start_collection_task
and 20 more in the full report
15 fixed3 passed either way4 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+127%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/17/2026v118 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
Write a raw NQE query snippet to check which network devices and VRFs contain host routes matching target subnet 110.240.240.240/32 in their unicast table.
What was checked, without and with the skill
Checked
Without skill
With skill
Iterates over network.devices and vrf.afts.ipv4Unicast.ipEntries
Missed
Passed
Applies ipSubnet comparison checking prefix containment for 110.240.240.240/32
Missed
Passed
case-20 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
Use this skill for Forward snapshot assurance, collection, and analysis:
Discover Forward networks, snapshots, and devices
Verify paths and reachability
Discover and run NQE checks
Review predefined checks, failed checks, and vulnerability analysis
Compare NQE, snapshot, and config diffs
Search configurations
Analyze blast radius for a source location to destination IPv4 subnets
Review hardware and OS lifecycle support
Find missing devices inferred during collection
Support lab or real-network collection workflows
Startup
Start with get_default_settings to see configured defaults.
If no default network is set, use list_networks with a small limit and ask
the user which network to use.
Prefer explicit network_id and snapshot_id values for repeatable results.
Use bounded limits by default. Use all_results only when the user needs the
complete dataset.
In Forward SaaS, prefer FORWARD_API_BASE_URL=https://fwd.app and set
FORWARD_INSTANCE_ID for local cache partitioning when multiple SaaS orgs or
accounts are used on the same NetClaw host.