Agent skill

Performing Ssl Tls Inspection Configuration

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying…

Apache-2.0Auto-check: notesSecurity

Install Performing Ssl Tls Inspection Configuration

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-ssl-tls-inspection-configuration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills performing-ssl-tls-inspection-configuration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/performing-ssl-tls-inspection-configuration .claude/skills/performing-ssl-tls-inspection-configuration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
performing-ssl-tls-inspection-configuration
GitHub stars
34k
Token cost
~2.9k tokens
SKILL.md length
509 words
Files
4 (incl. scripts, references)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying…

  • Works in 6 steps: Generate Internal CA for SSL Inspection → Deploy CA Certificate to Endpoints → Configure Palo Alto SSL Forward Proxy → …
  • Auditing TLS inspection on network security devices to close the encrypted-traffic blind spot
  • SKILL.md covers Overview, When to Use, Prerequisites and Core Concepts, plus 5 more sections
  • Runs Python scripts from its folder; calls openssl and curl

What it does

Performing Ssl Tls Inspection Configuration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying trusted CA certificates, managing exemptions for certificate-pinned apps, and privacy compliance. Use when setting up or auditing TLS inspection on network security devices to close the encrypted-traffic blind spot.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).

It sits in Security, covering Cryptography, Privacy and GDPR and Network security. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Auditing TLS inspection on network security devices to close the encrypted-traffic blind spot
  • Tasks that involve Cryptography
  • Tasks that involve Privacy and GDPR

Example prompts

  • “/performing-ssl-tls-inspection-configuration”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Generate Internal CA for SSL Inspection
  2. Deploy CA Certificate to Endpoints
  3. Configure Palo Alto SSL Forward Proxy
  4. Configure Exemptions
  5. Configure Inbound Inspection for Internal Servers
  6. Validate SSL Inspection

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • openssl
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.paloaltonetworks.com
    • cisco.com
    • csrc.nist.gov
    • cisa.gov

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Performing Ssl Tls Inspection Configuration loads about 2.9k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 509 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteRuns commands with sudoSKILL.md:157
    sudo security add-trusted-cert -d -r trustRoot \
  • NoteRuns commands with sudoSKILL.md:165
    sudo cp ssl-inspect-ca.crt /usr/local/share/ca-certificates/
  • NoteRuns commands with sudoSKILL.md:166
    sudo update-ca-certificates
  • NoteRuns commands with sudoSKILL.md:169
    sudo cp ssl-inspect-ca.crt /etc/pki/ca-trust/source/anchors/
  • NoteRuns commands with sudoSKILL.md:170
    sudo update-ca-trust

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 509 words, ~2,895 tokens.

Download SKILL.mdSave it as .claude/skills/performing-ssl-tls-inspection-configuration/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
performing-ssl-tls-inspection-configuration
description
Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying trusted CA certificates, managing exemptions for certificate-pinned apps, and privacy compliance. Use when setting up or auditing TLS inspection on network security devices to close the encrypted-traffic blind spot.
domain
cybersecurity
subdomain
network-security
tags
ssl-inspection, tls-decryption, https-inspection, certificate-management, proxy, man-in-the-middle, network-security, forward-proxy
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
PR.IR-01, DE.CM-01, ID.AM-03, PR.DS-02
mitre_attack
T1046, T1040, T1557, T1071, T1573

Performing SSL/TLS Inspection Configuration

Overview

SSL/TLS inspection (also called SSL decryption, HTTPS inspection, or TLS break-and-inspect) intercepts encrypted traffic between clients and servers to inspect the cleartext content for malware, data exfiltration, policy violations, and command-and-control communications. The inspection device acts as a trusted man-in-the-middle, terminating the TLS session from the client, inspecting the plaintext content, and establishing a new TLS session to the destination server. With over 95% of web traffic now encrypted, organizations without TLS inspection have a massive blind spot. This skill covers configuring TLS inspection on next-generation firewalls, deploying trusted CA certificates, managing exemptions for certificate-pinned applications, and ensuring compliance with privacy regulations.

When to Use

  • When conducting security assessments that involve performing ssl tls inspection configuration
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Next-generation firewall or secure web gateway with TLS inspection capability
  • Internal Certificate Authority (CA) for signing inspection certificates
  • Endpoint certificate management (GPO, MDM, or manual deployment)
  • Privacy and legal review for TLS inspection scope
  • Understanding of PKI, X.509 certificates, and TLS handshake

Core Concepts

SSL/TLS Inspection Modes
ModeDirectionDescription
SSL Forward ProxyOutboundIntercepts client-to-internet HTTPS connections
SSL Inbound InspectionInboundDecrypts traffic destined for internal servers
SSH ProxyBothInspects SSH tunneled traffic
Forward Proxy Process
Client                  Firewall/Proxy              Web Server
  │                         │                          │
  │──TLS ClientHello──────→│                          │
  │                         │──TLS ClientHello───────→│
  │                         │←─TLS ServerHello────────│
  │                         │  (real server cert)      │
  │                         │                          │
  │                         │  [Validates server cert]  │
  │                         │  [Generates proxy cert   │
  │                         │   signed by internal CA]  │
  │                         │                          │
  │←─TLS ServerHello───────│                          │
  │  (proxy-signed cert)    │                          │
  │                         │                          │
  │──Encrypted data────────→│  [Decrypt, Inspect]      │
  │                         │──Encrypted data────────→│
  │←─Encrypted data─────────│  [Decrypt, Inspect]      │
  │                         │←─Encrypted data─────────│
Certificate Trust Chain
Enterprise Root CA
  └── Subordinate CA (SSL Inspection)
        └── Dynamically Generated Server Certificates
             (CN matches requested server)

Workflow

Step 1: Generate Internal CA for SSL Inspection
bash
# Create private key for SSL Inspection CA
openssl genrsa -aes256 -out ssl-inspect-ca.key 4096

# Create CA certificate (5 year validity)
openssl req -new -x509 -key ssl-inspect-ca.key \
  -sha256 -days 1825 \
  -out ssl-inspect-ca.crt \
  -subj "/C=US/ST=California/O=Corp Inc/OU=Network Security/CN=Corp SSL Inspection CA" \
  -extensions v3_ca \
  -config <(cat <<EOF
[req]
distinguished_name = req_dn
x509_extensions = v3_ca

[req_dn]

[v3_ca]
basicConstraints = critical,CA:TRUE,pathlen:0
keyUsage = critical,digitalSignature,keyCertSign,cRLSign
subjectKeyIdentifier = hash
authorityKeyIdentifier = keyid:always
EOF
)

# Verify certificate
openssl x509 -in ssl-inspect-ca.crt -text -noout
Step 2: Deploy CA Certificate to Endpoints

Windows (Group Policy):

powershell
# Import CA cert to trusted root store via GPO
# Computer Configuration > Policies > Windows Settings >
# Security Settings > Public Key Policies > Trusted Root CAs

# Or deploy via PowerShell
Import-Certificate -FilePath "\\server\share\ssl-inspect-ca.crt" `
  -CertStoreLocation "Cert:\LocalMachine\Root"

# Verify deployment
Get-ChildItem Cert:\LocalMachine\Root | Where-Object {
    $_.Subject -like "*SSL Inspection CA*"
}

macOS (MDM profile or manual):

bash
# Install via command line
sudo security add-trusted-cert -d -r trustRoot \
  -k /Library/Keychains/System.keychain ssl-inspect-ca.crt

Linux:

bash
# Ubuntu/Debian
sudo cp ssl-inspect-ca.crt /usr/local/share/ca-certificates/
sudo update-ca-certificates

# RHEL/CentOS
sudo cp ssl-inspect-ca.crt /etc/pki/ca-trust/source/anchors/
sudo update-ca-trust
Step 3: Configure Palo Alto SSL Forward Proxy
# Import CA certificate to firewall
# Device > Certificate Management > Certificates > Import

# Set as Forward Trust CA
set shared certificate SSL-Inspect-CA forward-trust-certificate yes

# Create Decryption Profile
set profiles decryption Corporate-Decrypt ssl-forward-proxy block-expired-certificate yes
set profiles decryption Corporate-Decrypt ssl-forward-proxy block-untrusted-issuer yes
set profiles decryption Corporate-Decrypt ssl-forward-proxy block-unknown-cert yes
set profiles decryption Corporate-Decrypt ssl-forward-proxy restrict-cert-exts yes
set profiles decryption Corporate-Decrypt ssl-forward-proxy strip-alpn no

# Minimum TLS version
set profiles decryption Corporate-Decrypt ssl-protocol-settings min-version tls1-2
set profiles decryption Corporate-Decrypt ssl-protocol-settings max-version max

# Decryption policy - decrypt outbound HTTPS
set rulebase decryption rules Decrypt-Outbound from Trust to Untrust
set rulebase decryption rules Decrypt-Outbound source any
set rulebase decryption rules Decrypt-Outbound destination any
set rulebase decryption rules Decrypt-Outbound service any
set rulebase decryption rules Decrypt-Outbound action decrypt
set rulebase decryption rules Decrypt-Outbound type ssl-forward-proxy
set rulebase decryption rules Decrypt-Outbound profile Corporate-Decrypt
Step 4: Configure Exemptions

Certain applications and categories must be excluded from TLS inspection:

# Exempt certificate-pinned applications
set rulebase decryption rules No-Decrypt-Pinned from Trust to Untrust
set rulebase decryption rules No-Decrypt-Pinned application [ apple-update microsoft-update dropbox-base ]
set rulebase decryption rules No-Decrypt-Pinned action no-decrypt

# Exempt privacy-sensitive categories
set rulebase decryption rules No-Decrypt-Privacy from Trust to Untrust
set rulebase decryption rules No-Decrypt-Privacy category [ health-and-medicine financial-services ]
set rulebase decryption rules No-Decrypt-Privacy action no-decrypt

# Exempt specific high-trust domains
set rulebase decryption rules No-Decrypt-Trusted from Trust to Untrust
set rulebase decryption rules No-Decrypt-Trusted destination [ bank-of-america.com chase.com healthcare.gov ]
set rulebase decryption rules No-Decrypt-Trusted action no-decrypt
Step 5: Configure Inbound Inspection for Internal Servers
# Import server certificate and private key
# Device > Certificate Management > Certificates > Import

# Inbound inspection policy
set rulebase decryption rules Inspect-WebServers from Untrust to DMZ
set rulebase decryption rules Inspect-WebServers destination [ 10.0.20.10 10.0.20.11 ]
set rulebase decryption rules Inspect-WebServers service service-https
set rulebase decryption rules Inspect-WebServers action decrypt
set rulebase decryption rules Inspect-WebServers type ssl-inbound-inspection
set rulebase decryption rules Inspect-WebServers profile Corporate-Decrypt
Step 6: Validate SSL Inspection
bash
# Test from client - verify certificate issuer is internal CA
openssl s_client -connect www.google.com:443 -servername www.google.com 2>/dev/null | \
  openssl x509 -noout -issuer -subject

# Expected output (with inspection active):
# issuer= /C=US/O=Corp Inc/OU=Network Security/CN=Corp SSL Inspection CA
# subject= /CN=www.google.com

# Verify no certificate errors in browser
# Check firewall decryption logs for errors

# Test with curl
curl -v https://www.example.com 2>&1 | grep "issuer"

# Check decryption statistics on firewall
show system setting ssl-decrypt memory
show system setting ssl-decrypt certificate-cache
show counter global filter category ssl
Show full SKILL.md (222 more words)Show less

Performance Considerations

FactorImpactMitigation
CPU overhead50-80% increase per sessionHardware SSL acceleration, dedicated decrypt appliance
Throughput reduction40-60% typicalSize decryption hardware for peak encrypted traffic
Latency increase1-5ms additionalPlace inspection close to users
TLS 1.3 0-RTTCannot inspect 0-RTT dataBlock 0-RTT or accept risk
Certificate pinningInspection failsAdd to exemption list
QUIC/HTTP3Bypasses traditional proxyBlock QUIC, force HTTP/2

Compliance and Privacy

  • Employee Notice - Notify users that network traffic is subject to inspection
  • Privacy Exemptions - Exclude healthcare, financial, and legally privileged traffic
  • Data Handling - Inspected cleartext must not be logged or stored unnecessarily
  • GDPR Compliance - Document lawful basis for processing encrypted personal data
  • Certificate Pinning - Maintain exemption list for applications using HPKP or built-in pins

Best Practices

  • Start with Logging - Deploy in detect-only mode first to identify certificate-pinned applications
  • Maintain Exemption List - Keep a curated list of applications requiring decryption bypass
  • Block QUIC - Block UDP/443 to force HTTP/2 through TLS inspection
  • Monitor Certificate Errors - Track decryption errors in firewall logs
  • TLS 1.2 Minimum - Enforce TLS 1.2 as minimum version; block SSLv3 and TLS 1.0/1.1
  • Key Protection - Store inspection CA private key in HSM for production environments
  • Regular CA Rotation - Plan for CA certificate rotation before expiration

References

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/performing-ssl-tls-inspection-configuration of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Performing Ssl Tls Inspection Configuration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Performing Ssl Tls Inspection Configuration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Performing Ssl Tls Inspection Configuration this skillmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: NotesApache-2.0
Google Cloud Waf Securitygoogle/skills21k1 repos~4.2kAutomated safety check: PassApache-2.0
Clade Security Basicsjeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: NotesMIT
Deepgram Security Basicsjeremylongshore/tons-of-skills-marketplace2.8k—~2.2kAutomated safety check: PassMIT
Obsidian Security Basicsjeremylongshore/tons-of-skills-marketplace2.8k—~3.3kAutomated safety check: PassMIT
Azure Key VaultKilo-Org/kilo-marketplace1901 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Official

    Generates security-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Google Cloud Well-Architected Framework (WAF).

    21k GitHub starsUsed in 1 repo~4.2k tokens
    SecurityAuto-check passed
  • Clade Security Basics

    jeremylongshore/tons-of-skills-marketplace

    Secure your Anthropic integration — API key management, input validation, Use when working with security-basics patterns.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    SecurityAuto-check: notes
  • Deepgram Security Basics

    jeremylongshore/tons-of-skills-marketplace

    Apply Deepgram security best practices for API key management and data protection.

    2.8k GitHub stars~2.2k tokensUpdated yesterday
    SecurityAuto-check passed
  • Obsidian Security Basics

    jeremylongshore/tons-of-skills-marketplace

    Implement secure Obsidian plugin development practices. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~3.3k tokensUpdated yesterday
    SecurityAuto-check passed
  • Azure Key Vault

    Kilo-Org/kilo-marketplace

    Guidance for Azure Key Vault — securely storing and managing secrets, keys, and certificates with RBAC, network isolation, managed identity access, soft delete / purge protection, and rotation.

    190 GitHub starsUsed in 1 repo~1.9k tokens
    Backend & APIsAuto-check passed
  • Pseudonymization Risk

    mukul975/Privacy-Data-Protection-Skills

    Assessment of pseudonymization techniques and re-identification risk.

    301 GitHub stars~3.2k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Performing Ssl Tls Inspection Configuration

What does Performing Ssl Tls Inspection Configuration do?

Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying…. Performing Ssl Tls Inspection Configuration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying trusted CA certificates, managing exemptions for certificate-pinned apps, and privacy compliance.

When should I use Performing Ssl Tls Inspection Configuration?

Performing Ssl Tls Inspection Configuration fits situations like: auditing TLS inspection on network security devices to close the encrypted-traffic blind spot; tasks that involve Cryptography; tasks that involve Privacy and GDPR.

How do I install Performing Ssl Tls Inspection Configuration in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-ssl-tls-inspection-configuration -a claude-code`. Or copy the skill folder (skills/performing-ssl-tls-inspection-configuration in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/performing-ssl-tls-inspection-configuration in your project. Claude Code loads it when a task matches its description.

How do I install Performing Ssl Tls Inspection Configuration in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-ssl-tls-inspection-configuration -a codex`. Or copy the skill folder (skills/performing-ssl-tls-inspection-configuration in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/performing-ssl-tls-inspection-configuration in your project. Codex loads it when a task matches its description.

Can I use Performing Ssl Tls Inspection Configuration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-ssl-tls-inspection-configuration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performing-ssl-tls-inspection-configuration, .gemini/skills/performing-ssl-tls-inspection-configuration, .github/skills/performing-ssl-tls-inspection-configuration and .opencode/skills/performing-ssl-tls-inspection-configuration in your project.

What does Performing Ssl Tls Inspection Configuration need to run?

Going by SKILL.md and its folder, Performing Ssl Tls Inspection Configuration needs Python for the scripts in its folder and the command-line tools its instructions call (openssl and curl). Our summary lists: Python 3.

Does Performing Ssl Tls Inspection Configuration access the network?

SKILL.md names 4 domains. As links in the text: docs.paloaltonetworks.com, cisco.com, csrc.nist.gov and cisa.gov. This is read from the text; nothing was executed.

Is Performing Ssl Tls Inspection Configuration safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Performing Ssl Tls Inspection Configuration use?

Performing Ssl Tls Inspection Configuration is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Performing Ssl Tls Inspection Configuration use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 566 tokens, read only when the agent opens those files.

What are the alternatives to Performing Ssl Tls Inspection Configuration?

Skills that share tags, products or a category with Performing Ssl Tls Inspection Configuration: Google Cloud Waf Security (google/skills, 21k stars), Clade Security Basics (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Deepgram Security Basics (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Obsidian Security Basics (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Performing Ssl Tls Inspection Configuration?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.