How do I install the Knowledge Networking skill?

Run npx skillmds@latest add deankelly751/knowledge-networking in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Knowledge Networking safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Knowledge Networking?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Knowledge Networking free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Knowledge Networking?

DeanKelly751 (@deankelly751) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Knowledge Networking by deankelly751

Name: Knowledge Networking
Author: DeanKelly751

Knowledge Networking

Networking fundamentals for application developers covering DNS, load balancing, CDN, TLS, and service mesh. Decision framework for networking patterns. Use when designing distributed systems, troubleshooting connectivity, or choosing networking infrastructure.

DeanKelly751 Updated Sep 21, 2026

File contents

Networking

Purpose

Networking knowledge essential for application developers designing distributed systems.

DNS Essentials

Record	Purpose	Example use
A/AAAA	Domain → IP	Service endpoint
CNAME	Domain → domain	Alias to load balancer
SRV	Service discovery	Internal service lookup
TXT	Metadata	Domain verification, SPF

TTL decisions: Lower TTL = faster failover, more DNS load. Production: 60-300s. During migrations: reduce to 30-60s before cutover.

Load Balancing

Layer	Operates on	Use for
L4 (TCP/UDP)	IP + port	Raw throughput, protocol-agnostic
L7 (HTTP)	URL, headers, cookies	Path routing, header-based routing, TLS termination

Algorithm selection:

Round robin: Equal-capacity backends
Least connections: Variable request duration
Weighted: Heterogeneous capacity
Consistent hashing: Session affinity, caching

TLS

Terminate at edge (load balancer) for simplicity
mTLS for service-to-service in zero-trust networks
Certificate rotation: automated (ACME/cert-manager)
Minimum TLS 1.2, prefer 1.3

CDN Decision

Use a CDN when:

Static assets served to geographically distributed users
API responses that are cacheable and latency-sensitive
DDoS protection needed at edge

Skip CDN when:

All users in one region
All responses are personalized/uncacheable
Internal-only services

Related Skills

infrastructure/knowledge-cloud-architecture — networking in cloud context
security/knowledge-secure-by-design — network security principles
performance/knowledge-caching-patterns — CDN as cache layer

---name: knowledge-networkingdescription: Networking fundamentals for application developers covering DNS, load balancing, CDN, TLS, and service mesh. Decision framework for networking patterns. Use when designing distributed systems, troubleshooting connectivity, or choosing networking infrastructure.---# Networking## PurposeNetworking knowledge essential for application developers designing distributed systems.## DNS Essentials| Record | Purpose | Example use ||--------|---------|-------------|| A/AAAA | Domain → IP | Service endpoint || CNAME | Domain → domain | Alias to load balancer || SRV | Service discovery | Internal service lookup || TXT | Metadata | Domain verification, SPF |**TTL decisions**: Lower TTL = faster failover, more DNS load. Production: 60-300s. During migrations: reduce to 30-60s before cutover.## Load Balancing| Layer | Operates on | Use for ||-------|-------------|---------|| L4 (TCP/UDP) | IP + port | Raw throughput, protocol-agnostic || L7 (HTTP) | URL, headers, cookies | Path routing, header-based routing, TLS termination |**Algorithm selection**:- Round robin: Equal-capacity backends- Least connections: Variable request duration- Weighted: Heterogeneous capacity- Consistent hashing: Session affinity, caching## TLS- Terminate at edge (load balancer) for simplicity- mTLS for service-to-service in zero-trust networks- Certificate rotation: automated (ACME/cert-manager)- Minimum TLS 1.2, prefer 1.3## CDN DecisionUse a CDN when:- Static assets served to geographically distributed users- API responses that are cacheable and latency-sensitive- DDoS protection needed at edgeSkip CDN when:- All users in one region- All responses are personalized/uncacheable- Internal-only services## Related Skills- `infrastructure/knowledge-cloud-architecture` — networking in cloud context- `security/knowledge-secure-by-design` — network security principles- `performance/knowledge-caching-patterns` — CDN as cache layer

Frequently asked questions