Skip to content
cccskills
FreePublished on GitHub

network-reachability

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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. See GLOSSARY.md for shared term definitions.

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

  1. STOP further probing immediately. Do not retry automatically or escalate to a broader scan against the same unreachable host.
  2. 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.
  3. 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 — the normalized summary supplements, never replaces, the exact bytes.
  4. 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. A retry is a new execution: confirm a currently valid target authorization and a fresh matching durable approval before re-running; never reuse or replay a consumed, expired, or denied decision.
  5. Record the blocker as a Research Observation via security-observation-intake, citing the raw probe output registered as an Artifact through the Evidence Interface (src/server/evidence/artifact-service.ts), 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.
  • Layer-2 discovery (arping, arp-scan) bypasses the IP-layer allowlist and is not a reachability workaround: it needs its own scope and durable approval.
  • 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

justsml/ExploitHunter.app14Updated Oct 17, 2026

Plan vulnerability research using conventional bug-hunting and pentest stage names, specialty playbooks, and a research-hypothesis-experiment loop. Use when designing a bug bounty workflow, selecting tools and strategies, building a decision tree, or turning a target/scope into a staged hunting plan.

The English summary is being prepared. Showing the original description.

justsml/ExploitHunter.app14Updated Oct 17, 2026

Passive code-review lane for authorized repositories, local checkouts, uploaded source archives, and diffs. Use when the security research agent needs deterministic candidate discovery before expensive AI investigation, scoped PR-style review, append-only evidence records, or independent revalidation of code findings.

The English summary is being prepared. Showing the original description.

justsml/ExploitHunter.app14Updated Oct 17, 2026

Run independent, task-matched expert attempts, select a base, and synthesize the strongest result.

The English summary is being prepared. Showing the original description.

justsml/ExploitHunter.app14Updated Oct 17, 2026

Select established CTF and security-research tools for authorized artifact triage, web inspection, reversing, crypto, forensics, networking, and exploit validation. Use when a user provides a CTF-style tool catalog, asks which tools to use, or needs safe usage instructions for common offensive/security tools.

The English summary is being prepared. Showing the original description.

justsml/ExploitHunter.app14Updated Oct 17, 2026

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

The English summary is being prepared. Showing the original description.

justsml/ExploitHunter.app14Updated Oct 17, 2026

See all skills by justsml

Report a problem with this skill