Individual skill

protocol-security

Transport security where the client establishes trust: TLS version floor, certificate chain and hostname verification, the trust store, connecting by IP, mTLS and workload identity as authentication, gRPC channel credentials, and SMTP STARTTLS. Use when generating HTTP, gRPC, or SMTP clients and servers, configuring TLS in code or platform config, wiring service-to-service authentication, or when tempted to disable certificate verification.

skills/protocol-security/SKILL.md

Read pinned source

Source commit eaba88102d91df65a9aa6397e8507c315c018f5e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
23
Repository last updated
Aug 14, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Protocol Security

## Rules (for AI agents)

### ALWAYS
- Default to **TLS 1.3**, and permit TLS 1.2 only where a peer genuinely requires it.
  Disable TLS 1.0, 1.1, and every SSL version. Cipher-suite selection is a
  consequence of the version floor rather than a separate decision —
  `references/tls-configuration.md` carries the suite lists and the per-platform
  config keys.
- Verify the full certificate chain on every connection: a trusted issuer, an
  unexpired validity window, and a hostname that matches a **`subjectAltName`
  dNSName** entry. The hostname is checked *against* the SAN — SAN is not an
  alternative place to look, and a `CN` match is not a fallback, because current