Run any Skill in Manus with one click

network-reachability

Stars7

Forks0

UpdatedJuly 22, 2026 at 22:27

Use when a network probe, DNS lookup, HTTP fetch, or nmap scan reports the target host or the internet is unreachable. Stops further probing and reports a target-readiness blocker with useful diagnostics.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

justsml

justsml/ExploitHunter.app

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	network-reachability
description	Use when a network probe, DNS lookup, HTTP fetch, or nmap scan reports the target host or the internet is unreachable. Stops further probing and reports a target-readiness blocker with useful diagnostics.

Network Reachability & Circuit Breaker

Use this skill as an early circuit breaker when a network probe fails to reach the target host or the internet at large. A failed probe is a signal, not a reason to retry blindly.

When To Use

Trigger this procedure whenever a network-touching step reports the target host or the internet is unreachable:

DNS failure (ENOTFOUND, EAI_AGAIN, "name resolution failed", "Temporary failure in name resolution").
Connection refused (ECONNREFUSED, port closed).
No route to host (ENETUNREACH, "Network is unreachable", "No route to host").
Host seems down (nmap "Host seems down", no response to probes).
Fetch-level network errors (fetch failed, Failed to fetch, NetworkError).

Procedure

STOP further probing immediately. Do not retry automatically or escalate to a broader scan against the same unreachable host.
Classify the boundary correctly. This is a target-readiness, routing, or harness failure unless separate evidence proves otherwise; it is not a security finding about the target.
Report the failure in chat. Include the exact operation, normalized error, target, timestamp, and the workspace/network boundary from which it was attempted. Preserve raw output in expandable diagnostics.
Offer one practical recovery step. Ask the user to start the target, correct its address/network attachment, or retry the same bounded baseline after readiness is restored. Do not suspend the run with a menu of speculative scans.
Record the blocker so the research plan reflects reality and does not loop on the same unavailable target.

Guardrails

Stay within the approved network profile and target scope. Never bypass egress iptables rules to force reachability.
Do not auto-escalate from a failed probe to a heavier scan. A broader scan is a separate, evidence-backed decision after basic target readiness is restored.

More from this repository

same repository

audio-video-capture

justsml/ExploitHunter.app

Plan and use user-consented local camera and microphone observations for an explicitly authorized physical target. Use when a capture can establish a bounded physical-state observation such as whether a test fixture changed state, an instrument reading changed, or equipment noise changed relatively.

2026-07-227

exploitation-sandbox

justsml/ExploitHunter.app

Safely develop, verify, and document proof-of-concept exploits and payloads for authorized targets inside isolated Workspace Containers. Use when a Hypothesis is well-founded and the user has explicit authorization to test it, needs a minimal PoC, wants to verify impact, or needs to produce reproducible exploit Evidence for a report.

2026-07-217

proactive-security-strategy

justsml/ExploitHunter.app

Turn a specific vulnerability, patch, CVE, Version Diff, or Changelog Claim into a proactive security exploration plan. Use when the user wants research angles, lateral target discovery, patch/CVE strategy, new surface discovery, or hypothesis generation from vulnerability intelligence.

2026-07-217

network-recording

justsml/ExploitHunter.app

Use when explicitly authorized lab traffic must be captured, searched, or exported from the project's mitmproxy-backed Docker lab recorder.

2026-07-187

spec-implementation-review

justsml/ExploitHunter.app

Passive, citation-grounded review of security-relevant specifications, protocols, standards, APIs, and implementations. Use when a reviewer must trace external preconditions and invariants into source code without treating a cited claim as proof of a vulnerability.

2026-07-177

tune-model-evals

justsml/ExploitHunter.app

Scientific model and eval tuning loop for prompt/skill/system-prompt changes, model configuration, runtime options, and local/Ollama model sizing or environment variables. Use when tuning eval performance, comparing local or remote models, improving tool-use behavior, reducing timeouts/loops, or deciding whether an eval optimization is worth keeping.

2026-07-077

name	network-reachability
description	Use when a network probe, DNS lookup, HTTP fetch, or nmap scan reports the target host or the internet is unreachable. Stops further probing and reports a target-readiness blocker with useful diagnostics.

Network Reachability & Circuit Breaker

Use this skill as an early circuit breaker when a network probe fails to reach the target host or the internet at large. A failed probe is a signal, not a reason to retry blindly.

When To Use

Trigger this procedure whenever a network-touching step reports the target host or the internet is unreachable:

DNS failure (ENOTFOUND, EAI_AGAIN, "name resolution failed", "Temporary failure in name resolution").
Connection refused (ECONNREFUSED, port closed).
No route to host (ENETUNREACH, "Network is unreachable", "No route to host").
Host seems down (nmap "Host seems down", no response to probes).
Fetch-level network errors (fetch failed, Failed to fetch, NetworkError).

Procedure

STOP further probing immediately. Do not retry automatically or escalate to a broader scan against the same unreachable host.
Classify the boundary correctly. This is a target-readiness, routing, or harness failure unless separate evidence proves otherwise; it is not a security finding about the target.
Report the failure in chat. Include the exact operation, normalized error, target, timestamp, and the workspace/network boundary from which it was attempted. Preserve raw output in expandable diagnostics.
Offer one practical recovery step. Ask the user to start the target, correct its address/network attachment, or retry the same bounded baseline after readiness is restored. Do not suspend the run with a menu of speculative scans.
Record the blocker so the research plan reflects reality and does not loop on the same unavailable target.

Guardrails

Stay within the approved network profile and target scope. Never bypass egress iptables rules to force reachability.
Do not auto-escalate from a failed probe to a heavier scan. A broader scan is a separate, evidence-backed decision after basic target readiness is restored.