zero-trust-architecture — Claude Code skill: how to install
Guides AI coding agents to implement Zero Trust security with identity verification and microsegmentation. Useful for cloud-native apps.
npx skills add aj-geddes/useful-ai-prompts --skill zero-trust-architecture -a claude-codeWhat zero-trust-architecture does
This skill guides architecture design around the "never trust, always verify" rule. It provides a starter gateway script in Node.js that validates RS256 JWT tokens and checks revocation using the jti claim. Deep-dive guides in the references/ folder cover Service Mesh microsegmentation and a Python policy engine.
Running the gateway logic requires environment variables for IDENTITY_PROVIDER_URL and JWT_PUBLIC_KEY. Without token revocation checks against a registry, compromised credentials cannot be blocked in time.
The architecture eliminates implicit trust in network locations. Static credentials and unencrypted internal traffic are explicitly ruled out.
What it helps with
- implement a Node.js Zero Trust gateway with JWT validation
- configure Service Mesh microsegmentation for microservices
- build a policy engine in Python for access decisions
- eliminate lateral movement and static credentials across services
Example prompts for the agent
- Set up a Zero Trust gateway in Node.js with RS256 token verification.
- Draft a Service Mesh microsegmentation strategy for our APIs.
- Add a token revocation check using the jti claim in zero-trust-gateway.js.
How to install zero-trust-architecture
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill zero-trust-architecture -a claude-code2Manually: put the files in place
~/.claude/skills/zero-trust-architecture/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/zero-trust-architecture/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill zero-trust-architecture -a codex2Manually: put the files in place
.agents/skills/zero-trust-architecture/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill zero-trust-architecture -a cursor2Manually: put the files in place
.cursor/skills/zero-trust-architecture/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts zero-trust-architecture2Manually: put the files in place
.github/skills/zero-trust-architecture/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill zero-trust-architecture -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/zero-trust-architectureManually: put the files in place
.devin/skills/zero-trust-architecture/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill zero-trust-architecture -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about zero-trust-architecture
How to install zero-trust-architecture in Claude Code?
Run npx skills add aj-geddes/useful-ai-prompts --skill zero-trust-architecture -a claude-code in your terminal.
What does zero-trust-architecture do?
It guides your agent to enforce continuous verification, microsegmentation, and least privilege access. The skill provides reference patterns for API gateways, service meshes, and policy engines.
Which reference guides are included?
The skill includes dedicated guides for a Zero Trust Gateway, Service Mesh microsegmentation, and a Python Zero Trust Policy Engine.
Source text
SKILL.md · MIT
---
name: zero-trust-architecture
description: >
Implement Zero Trust security model with identity verification,
microsegmentation, least privilege access, and continuous monitoring. Use when
building secure cloud-native applications.
---
# Zero Trust Architecture
## Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
## Overview
Implement comprehensive Zero Trust security architecture based on "never trust, always verify" principle with identity-centric security, microsegmentation, and continuous verification.
## When to Use
- Cloud-native applications
- Microservices architecture
- Remote workforce security
- API security
- Multi-cloud deployments
- Legacy modernization
- Compliance requirements
## Quick Start
Minimal working example:
```javascript
// zero-trust-gateway.js
const jwt = require("jsonwebtoken");
const axios = require("axios");
class ZeroTrustGateway {
constructor() {
this.identityProvider = process.env.IDENTITY_PROVIDER_URL;
this.deviceRegistry = new Map();
this.sessionContext = new Map();
}
/**
* Verify identity - Who are you?
*/
async verifyIdentity(token) {
try {
// Verify JWT token
const decoded = jwt.verify(token, process.env.JWT_PUBLIC_KEY, {
algorithms: ["RS256"],
});
// Check token hasn't been revoked
const revoked = await this.checkTokenRevocation(decoded.jti);
if (revoked) {
throw new Error("Token has been revoked");
// ... (see reference guides for full implementation)
```
## Reference Guides
Detailed implementations in the `references/` directory:
| Guide | Contents |
|---|---|
| [Zero Trust Gateway](references/zero-trust-gateway.md) | Zero Trust Gateway |
| [Service Mesh - Microsegmentation](references/service-mesh-microsegmentation.md) | Service Mesh - Microsegmentation |
| [Python Zero Trust Policy Engine](references/python-zero-trust-policy-engine.md) | Python Zero Trust Policy Engine |
## Best Practices
### ✅ DO
- Verify every request
- Implement MFA everywhere
- Use microsegmentation
- Monitor continuously
- Encrypt all communications
- Implement least privilege
- Log all access
- Regular audits
### ❌ DON'T
- Trust network location
- Use implicit trust
- Skip device verification
- Allow lateral movement
- Use static credentials
© aj-geddes · MIT · aj-geddes/useful-ai-prompts