New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Configuring Zscaler Private Access For Ztna

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Configures Zscaler Private Access (ZPA) to replace traditional VPN with zero trust network access by deploying App Connectors, defining application segments, configuring identity- and…

Apache-2.0Auto-check: notesSecurity

Install Configuring Zscaler Private Access For Ztna

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill configuring-zscaler-private-access-for-ztna -a claude-code

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

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills configuring-zscaler-private-access-for-ztna --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/configuring-zscaler-private-access-for-ztna .claude/skills/configuring-zscaler-private-access-for-ztna && 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
configuring-zscaler-private-access-for-ztna
GitHub stars
34k
Token cost
~2.9k tokens
SKILL.md length
690 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Configures Zscaler Private Access (ZPA) to replace traditional VPN with zero trust network access by deploying App Connectors, defining application segments, configuring identity- and…

  • Works in 6 steps: Deploy App Connectors in Application… → Define Server Groups and Application… → Configure Access Policies → …
  • Replacing VPN concentrators with ZTNA
  • SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
  • Runs Python scripts from its folder; calls apt, yum and curl; reaches dist.private.zscaler.com and yum.private.zscaler.com

What it does

Configuring Zscaler Private Access For Ztna is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Configures Zscaler Private Access (ZPA) to replace traditional VPN with zero trust network access by deploying App Connectors, defining application segments, configuring identity- and device-posture-based access policies, and integrating with IdPs. Use when replacing VPN concentrators with ZTNA or providing remote users secure access to internal applications without network-level connectivity.

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

It sits in Security. It works with Linux. 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

  • Replacing VPN concentrators with ZTNA
  • Providing remote users secure access to internal applications without network-level connectivity

Example prompts

  • “Use the configuring-zscaler-private-access-for-ztna skill to configure Zscaler Private Access (ZPA) to replace traditional VPN with zero trust…”
  • “/configuring-zscaler-private-access-for-ztna”

Requirements

  • Python 3

Workflow steps

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

  1. Deploy App Connectors in Application Network
  2. Define Server Groups and Application Segments
  3. Configure Access Policies
  4. Configure Device Posture Profiles
  5. Enable Browser Access for Clientless ZTNA
  6. Configure Logging and Monitoring

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 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • apt
    • yum
    • curl

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • dist.private.zscaler.com
    • yum.private.zscaler.com

    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

Configuring Zscaler Private Access For Ztna loads about 2.9k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 690 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
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
~4.6k

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:68
    sudo yum install -y https://yum.private.zscaler.com/yum/el7/zpa-connector-latest.rpm
  • NoteRuns commands with sudoSKILL.md:71
    ist.private.zscaler.com/apt/pubkey.gpg | sudo apt-key add -
  • NoteRuns commands with sudoSKILL.md:72
    t.private.zscaler.com/apt stable main" | sudo tee /etc/apt/sources.list.d/zpa.list
  • NoteRuns commands with sudoSKILL.md:73
    sudo apt update && sudo apt install -y zpa-connector
  • NoteRuns commands with sudoSKILL.md:76
    sudo /opt/zscaler/bin/zpa-connector configure \
  • NoteRuns commands with sudoSKILL.md:80
    sudo systemctl enable zpa-connector
  • NoteRuns commands with sudoSKILL.md:81
    sudo systemctl start zpa-connector
  • NoteRuns commands with sudoSKILL.md:84
    sudo systemctl status zpa-connector
  • NoteRuns commands with sudoSKILL.md:85
    sudo /opt/zscaler/bin/zpa-connector status

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). 690 words, ~2,927 tokens.

Download SKILL.mdSave it as .claude/skills/configuring-zscaler-private-access-for-ztna/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
configuring-zscaler-private-access-for-ztna
description
Configures Zscaler Private Access (ZPA) to replace traditional VPN with zero trust network access by deploying App Connectors, defining application segments, configuring identity- and device-posture-based access policies, and integrating with IdPs. Use when replacing VPN concentrators with ZTNA or providing remote users secure access to internal applications without network-level connectivity.
domain
cybersecurity
subdomain
zero-trust-architecture
tags
zscaler, zpa, ztna, zero-trust, app-connector, access-policy, sase
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
PR.AA-01, PR.AA-05, PR.IR-01, GV.PO-01
mitre_attack
T1133, T1078, T1021, T1219, T1190

Configuring Zscaler Private Access for ZTNA

When to Use

  • When replacing traditional VPN concentrators with application-level zero trust access
  • When providing remote users secure access to internal applications without network-level connectivity
  • When implementing least-privilege access where users only see authorized applications
  • When needing to make internal applications invisible to unauthorized users and the internet
  • When integrating ZTNA with existing SASE architecture using Zscaler Internet Access (ZIA)

Do not use for applications requiring raw UDP access (ZPA primarily supports TCP), for providing full network-level access equivalent to site-to-site VPN (use ZPA AppProtection or branch connector instead), or when the organization requires on-premises-only access control without cloud dependency.

Prerequisites

  • Zscaler Private Access subscription (Business or Transformation edition)
  • Identity provider configured: Okta, Microsoft Entra ID, Ping Identity, or SAML 2.0 IdP
  • App Connector VM requirements: Linux VM (CentOS 7/8, RHEL 7/8, Ubuntu 18.04+, Amazon Linux 2) with 2 vCPU, 4GB RAM minimum
  • Outbound connectivity from App Connector to ZPA cloud on port 443 (no inbound ports required)
  • DNS resolution from App Connector to internal application FQDNs
  • Zscaler Client Connector deployed on user endpoints

Workflow

Step 1: Deploy App Connectors in Application Network

App Connectors establish outbound-only tunnels to the ZPA cloud, providing access to internal applications.

bash
# Download and install App Connector on Linux VM
# Obtain provisioning key from ZPA Admin Portal > Administration > App Connectors

# For RHEL/CentOS
sudo yum install -y https://yum.private.zscaler.com/yum/el7/zpa-connector-latest.rpm

# For Ubuntu/Debian
curl -sS https://dist.private.zscaler.com/apt/pubkey.gpg | sudo apt-key add -
echo "deb https://dist.private.zscaler.com/apt stable main" | sudo tee /etc/apt/sources.list.d/zpa.list
sudo apt update && sudo apt install -y zpa-connector

# Configure the connector with provisioning key
sudo /opt/zscaler/bin/zpa-connector configure \
  --provision-key "PROVISIONING_KEY_FROM_PORTAL"

# Start the connector service
sudo systemctl enable zpa-connector
sudo systemctl start zpa-connector

# Verify connector status
sudo systemctl status zpa-connector
sudo /opt/zscaler/bin/zpa-connector status

# Deploy second connector for HA (minimum 2 per site)
# Repeat on second VM with same App Connector Group provisioning key
Step 2: Define Server Groups and Application Segments

Map internal applications to server groups and create application segments.

text
ZPA Admin Portal Configuration:

1. Server Groups:
   Navigate to: Administration > App Connectors > Server Groups
   - Name: "DC-East-Servers"
   - App Connector Group: "DC-East-Connectors"
   - Servers:
     - hr-portal.internal.corp (10.1.1.50, TCP 443)
     - finance-app.internal.corp (10.1.1.51, TCP 443)
     - git.internal.corp (10.1.2.10, TCP 22, 443)

2. Application Segments:
   Navigate to: Resources > Application Segments > Add Application Segment
   - Name: "HR Applications"
   - Domain/URL: hr-portal.internal.corp
   - TCP Ports: 443
   - Server Group: DC-East-Servers
   - Health Reporting: Continuous
   - Bypass Type: Never (force all traffic through ZPA)

   - Name: "Engineering Tools"
   - Domain/URL: git.internal.corp, ci.internal.corp, wiki.internal.corp
   - TCP Ports: 22, 80, 443
   - Server Group: DC-East-Servers
   - Segment Group: "Engineering Segment Group"
Step 3: Configure Access Policies

Define who can access which application segments based on identity and device posture.

text
ZPA Admin Portal > Policies > Access Policy:

Rule 1: HR Team Access
  - Name: "HR Portal Access"
  - Action: ALLOW
  - Criteria:
    - User Groups: "HR-Department" (from IdP)
    - Application Segment: "HR Applications"
    - Device Posture Profile: "Corporate Managed Device"
    - Client Type: Zscaler Client Connector
  - Conditions:
    - SAML Attribute: department = "Human Resources"
    - Device Trust Level: "HIGH" (CrowdStrike ZTA score > 70)

Rule 2: Engineering Access
  - Name: "Engineering Tools Access"
  - Action: ALLOW
  - Criteria:
    - User Groups: "Engineering-Team", "DevOps-Team"
    - Application Segment: "Engineering Tools"
    - Device Posture Profile: "Developer Workstation"
  - Conditions:
    - Machine Group: "Engineering Laptops"

Rule 3: Contractor Limited Access
  - Name: "Contractor Wiki Access"
  - Action: ALLOW
  - Criteria:
    - User Groups: "External-Contractors"
    - Application Segment: "Wiki Only"
    - Client Type: Zscaler Client Connector OR Browser Access
  - Conditions:
    - Time Window: Mon-Fri 08:00-18:00 EST

Rule 4: Default Deny
  - Name: "Block All Other Access"
  - Action: DENY
  - Criteria: All Users, All Applications
  - Log: Enabled
Step 4: Configure Device Posture Profiles

Integrate device posture signals from endpoint security tools.

text
ZPA Admin Portal > Administration > Device Posture:

Profile 1: Corporate Managed Device
  - CrowdStrike Falcon: Running, ZTA Score >= 60
  - OS: Windows 10 21H2+, macOS 13+, Ubuntu 22.04+
  - Disk Encryption: Enabled (BitLocker/FileVault)
  - Firewall: Enabled
  - Screen Lock: Enabled

Profile 2: Developer Workstation
  - Inherits: Corporate Managed Device
  - CrowdStrike Falcon: ZTA Score >= 70
  - Patch Level: Within 30 days of latest
  - Certificate: Valid corporate certificate present

Profile 3: BYOD Device
  - OS: Latest minus 1 version
  - Browser: Chrome 120+ or Edge 120+
  - Antivirus: Any recognized AV running
Step 5: Enable Browser Access for Clientless ZTNA

Configure Browser Access for users without Zscaler Client Connector installed.

text
ZPA Admin Portal > Resources > Application Segments:

For "HR Applications" segment:
  - Enable Browser Access: Yes
  - Browser Access Type: HTTPS
  - Custom Domain: hr.access.company.com
  - Certificate: Upload TLS certificate for custom domain
  - Authentication: SAML via corporate IdP
  - Session Timeout: 4 hours
  - Clipboard Control: Disabled for sensitive apps
  - File Upload/Download: Restricted

For Browser Access Portal:
  - Portal URL: access.company.com
  - IdP: Microsoft Entra ID (SAML 2.0)
  - MFA: Required
  - Applications shown: Only authorized per user group
Step 6: Configure Logging and Monitoring

Set up log streaming for SIEM integration and continuous monitoring.

text
ZPA Admin Portal > Administration > Log Streaming Service:

Log Receiver Configuration:
  - Name: "Splunk-SIEM"
  - Type: Splunk (HEC)
  - Destination: https://splunk-hec.company.com:8088
  - HEC Token: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  - Log Types:
    - User Activity: Enabled
    - App Connector Status: Enabled
    - Audit Logs: Enabled
    - Browser Access: Enabled

# Splunk search for ZPA access anomalies
index=zscaler_zpa sourcetype=zpa:useractivity
| where action="denied"
| stats count by user, application, policy_name
| where count > 10
| sort -count

Key Concepts

TermDefinition
App ConnectorLightweight Linux service that creates outbound-only encrypted tunnels from internal networks to ZPA cloud, providing access to applications without inbound ports
Application SegmentLogical grouping of internal applications defined by FQDN/IP and ports, mapped to server groups for access policy enforcement
Server GroupCollection of application servers associated with App Connector groups that can serve requests for application segments
Access PolicyRules defining which users/groups can access which application segments under what conditions (device posture, time, location)
Zscaler Client ConnectorEndpoint agent installed on user devices that routes traffic to ZPA cloud for policy enforcement and application access
Browser AccessClientless ZTNA option allowing application access through a web browser without requiring Zscaler Client Connector installation
Show full SKILL.md (281 more words)Show less

Tools & Systems

  • Zscaler Private Access (ZPA): Cloud-native ZTNA platform replacing VPN with identity-based application access
  • Zscaler Client Connector: Cross-platform endpoint agent routing traffic through ZPA for policy enforcement
  • ZPA App Connector: Outbound-only tunnel endpoint deployed in application networks
  • ZPA Admin Portal: Web-based management console for policy, segment, and connector configuration
  • ZPA Log Streaming Service (LSS): Real-time log export to SIEM platforms (Splunk, Sentinel, QRadar)
  • CrowdStrike ZTA Integration: Device posture scoring for conditional access policy enforcement

Common Scenarios

Scenario: Migrating 500-User Organization from Cisco AnyConnect VPN to ZPA

Context: A financial services firm with 500 employees uses Cisco AnyConnect for remote access. VPN split-tunnel configuration creates security gaps, and full-tunnel mode causes performance issues. The firm needs application-level access control for SOX compliance.

Approach:

  1. Deploy 4 App Connectors (2 per data center) with HA configuration
  2. Define application segments for 20 internal applications grouped by business function
  3. Configure access policies mapping AD groups to application segments with device posture requirements
  4. Integrate CrowdStrike ZTA scores as device posture input (minimum score 60 for standard, 80 for financial apps)
  5. Enable Browser Access for contractors accessing the vendor portal
  6. Configure LSS to stream access logs to Splunk for SOX audit trail
  7. Run parallel operation for 3 weeks: VPN and ZPA side by side
  8. Phase out VPN connections after validating all application access through ZPA

Pitfalls: App Connector DNS must resolve all internal FQDNs used in application segments. Wildcard domain segments can cause performance issues if too broad. Browser Access does not support all web application frameworks (WebSocket-heavy apps may require Client Connector). CrowdStrike ZTA integration requires Falcon sensor deployment on all endpoints before enforcing posture policies.

Output Format

ZPA ZTNA Deployment Report
==================================================
Organization: FinanceCorp
Deployment Date: 2026-02-23

INFRASTRUCTURE:
  App Connectors: 4 (2x DC-East, 2x DC-West)
  Connector Status: All healthy
  Connector Version: 24.1.2

APPLICATION COVERAGE:
  Application Segments: 20
  Total Applications: 45
  Server Groups: 4
  Segment Groups: 6

ACCESS POLICIES:
  Total Rules: 12
  Allow Rules: 11
  Deny Rules: 1 (default deny)
  Device Posture Profiles: 3

USER ACCESS (last 30 days):
  Active Users: 487 / 500
  Total Sessions: 124,567
  Allowed Sessions: 123,890 (99.5%)
  Denied Sessions: 677 (0.5%)
  Browser Access Sessions: 2,341

VPN MIGRATION:
  Users migrated to ZPA: 487 / 500
  VPN decommission date: 2026-03-15

© 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 7 other files (scripts, references, assets) in skills/configuring-zscaler-private-access-for-ztna of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • assets/template.md
  • references/api-reference.md
  • references/standards.md
  • references/workflows.md
  • scripts/agent.py
  • scripts/process.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Configuring Zscaler Private Access For Ztna 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.

Configuring Zscaler Private Access For Ztna compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Configuring Zscaler Private Access For Ztna this skillmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: NotesApache-2.0
Write Cve Ruleevdenis/cvehound138—~2.5kAutomated safety check: PassGPL-3.0
Securitystatic-web-server/static-web-server2.4k—~2kAutomated safety check: NotesApache-2.0
User Managementsickn33/agentic-awesome-skills47k2 repos~2.8kAutomated safety check: NotesMIT
Memory Dumperptn1411/skill219—~945Automated safety check: NotesNone
Patt Fetchertransilienceai/communitytools563—~1.3kAutomated safety check: PassMIT

Similar skills

  • Write Cve Rule

    evdenis/cvehound

    Write, debug, or validate a CVEhound detection rule (.cocci or .grep) for a Linux kernel CVE.

    138 GitHub stars~2.5k tokensUpdated 2 days ago
    SecurityAuto-check passed

  • Security

    static-web-server/static-web-server

    Review or implement security-sensitive code in the Static Web Server (SWS) project — path traversal defenses, symlink and hidden-file policy, TLS, security headers, CORS, basic auth, untrusted input…

    2.4k GitHub stars~2k tokensUpdated yesterday
    SecurityAuto-check: notes

  • User Management

    sickn33/agentic-awesome-skills

    Manage users, groups, and permissions on Linux systems. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~2.8k tokens
    SecurityAuto-check: notes

  • Memory Dumper

    ptn1411/skill

    Dump process memory and scan for secrets, license keys, decryption keys, tokens, and crypto artifacts.

    219 GitHub stars~945 tokensUpdated 19 days ago
    SecurityAuto-check: notes

  • Patt Fetcher

    transilienceai/communitytools

    Fetches and extracts payloads from PayloadsAllTheThings on demand.

    563 GitHub stars~1.3k tokensUpdated 2 mo ago
    SecurityAuto-check passed

  • Re Ti

    dslsdzc/rev-skills

    威胁情报查询与关联：VT/Any.run/hybrid-analysis、MISP. An agent skill from dslsdzc/rev-skills.

    135 GitHub stars~1.4k tokensUpdated 6 days ago
    SecurityAuto-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

Works with

Categories

Questions about Configuring Zscaler Private Access For Ztna

What does Configuring Zscaler Private Access For Ztna do?

Configures Zscaler Private Access (ZPA) to replace traditional VPN with zero trust network access by deploying App Connectors, defining application segments, configuring identity- and…. Configuring Zscaler Private Access For Ztna is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Configures Zscaler Private Access (ZPA) to replace traditional VPN with zero trust network access by deploying App Connectors, defining application segments, configuring identity- and device-posture-based access policies, and integrating with IdPs.

When should I use Configuring Zscaler Private Access For Ztna?

Configuring Zscaler Private Access For Ztna fits situations like: replacing VPN concentrators with ZTNA; providing remote users secure access to internal applications without network-level connectivity.

How do I install Configuring Zscaler Private Access For Ztna in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill configuring-zscaler-private-access-for-ztna -a claude-code`. Or copy the skill folder (skills/configuring-zscaler-private-access-for-ztna in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/configuring-zscaler-private-access-for-ztna in your project. Claude Code loads it when a task matches its description.

How do I install Configuring Zscaler Private Access For Ztna in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill configuring-zscaler-private-access-for-ztna -a codex`. Or copy the skill folder (skills/configuring-zscaler-private-access-for-ztna in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/configuring-zscaler-private-access-for-ztna in your project. Codex loads it when a task matches its description.

Can I use Configuring Zscaler Private Access For Ztna 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 configuring-zscaler-private-access-for-ztna -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configuring-zscaler-private-access-for-ztna, .gemini/skills/configuring-zscaler-private-access-for-ztna, .github/skills/configuring-zscaler-private-access-for-ztna and .opencode/skills/configuring-zscaler-private-access-for-ztna in your project.

What does Configuring Zscaler Private Access For Ztna need to run?

Going by SKILL.md and its folder, Configuring Zscaler Private Access For Ztna needs Python for the scripts in its folder and the command-line tools its instructions call (apt, yum and curl). Our summary lists: Python 3.

Does Configuring Zscaler Private Access For Ztna access the network?

SKILL.md names 2 domains. In commands or code: dist.private.zscaler.com and yum.private.zscaler.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Configuring Zscaler Private Access For Ztna 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 Configuring Zscaler Private Access For Ztna use?

Configuring Zscaler Private Access For Ztna 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 Configuring Zscaler Private Access For Ztna 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 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Configuring Zscaler Private Access For Ztna?

Skills that share tags, products or a category with Configuring Zscaler Private Access For Ztna: Write Cve Rule (evdenis/cvehound, 138 stars), Security (static-web-server/static-web-server, 2.4k stars), User Management (sickn33/agentic-awesome-skills, 47k stars) and Memory Dumper (ptn1411/skill, 219 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Configuring Zscaler Private Access For Ztna?

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.