AGENT SKILL

network-change-verification

Pre/post verification checklist for network and routing changes. Use before and after any DNS, routing, tunnel, or proxy change, when exposing a new service externally, or when troubleshooting connectivity issues.

License 许可
MIT
所属仓库
muratovv/ai-hats
最近更新
2026-11-05
Stars
★ 3
Forks
1

01 前言 Front Matter

name
network-change-verification
license
MIT
description
Pre/post verification checklist for network and routing changes. Use before and after any DNS, routing, tunnel, or proxy change, when exposing a new service externally, or when troubleshooting connectivity issues.

03 SKILL.md 正文

Network Change Verification

Pre/post verification checklist for network and routing changes.

When to Use

Verifying connectivity around a change — the before/after probes for a DNS, route, tunnel, or proxy edit. Its sibling network-documentation owns the record of the resulting topology: verify the change works here, then update the source-of-truth there. Verification is the test; documentation is the artifact.

Before Change

  1. Source Check: Verify external DNS/Domain points to the correct IP.
  2. Path Check: Verify tunnels (WireGuard, etc.) are active.
  3. Destination Check: Run curl or nc on the target to confirm the service is listening.

After Change

  1. Summarize flow: Document the new traffic path (e.g., User → HTTPS (443) → Traefik → Tunnel → Service (8080)).
  2. Verify end-to-end: Confirm the full path works from the external entry point.
  3. Update docs: Ask the user to verify the documentation update.

Completion

  • Pre-change baseline captured
  • Post-change end-to-end connectivity verified
  • Traffic path documented and docs updated

Anti-Patterns

  • Skipping pre-change baseline — can't tell if the change broke something or it was already broken
  • Verifying only internal hops — must test from the external entry point
  • Forgetting doc update — next person won't know the new path

04 同仓库更多 Skills

muratovv
muratovv/ai-hats

tool-evaluation-protocol

Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML/LLM frameworks, testing approaches), or following up on a hype-driven recommendation.

★ 3
muratovv
muratovv/ai-hats

systematic-debugging

4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.

★ 3
muratovv
muratovv/ai-hats

skill-template

Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.

Skill与智能体开发
★ 3
muratovv
muratovv/ai-hats

skill-optimization

Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.

Skill与智能体开发
★ 3
muratovv
muratovv/ai-hats

silent-fallback-gate

PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.

★ 3
muratovv
muratovv/ai-hats

retro-to-framework

Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.

Skill与智能体开发
★ 3