Zero trust architect
Skill AtulPurohit/Antigravity-Awesome-Skills/plugins/security-pentester/skills/zero-trust-architect
Professional Zero Trust Architect skill. Implement enterprise-grade web application security controls and encryption standards.From its SKILL.md
npx -y skills add AtulPurohit/Antigravity-Awesome-Skills --skill zero-trust-architectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 209 tokens by cl100k_base, as published. Nobody here has run it
Zero Trust Architect
Purpose
Manage and implement Zero Trust Architect requirements efficiently within enterprise applications.
Core Concepts
Detailed operational framework for Zero Trust Architect:
1️⃣ Overview and Strategy
Understanding boundaries, rules, and best practices for the zero-trust-architect feature domain.
2️⃣ Code Implementation Reference
// Secure Password/Token verification
const crypto = require('crypto');
function verifyHash(payload, signature, secret) {
const expected = crypto.createHmac('sha256', secret).update(payload).digest('hex');
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}
3️⃣ Checklist & Validation Rules
- Integration validation checklist completed.
- Code conventions and naming rules followed.
- Strict type safety constraints verified.
- Security standards checked.
Outputs
- System integration pattern definitions.
- Code templates and examples.
- Test validation checklists.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most architecture codebase skills give in 209 tokens
Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07
- Ask the user which candidate to explorein 45 of 811, across 15 files
- Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
- Read any relevant architecture decision records firstin 31 of 811, across 8 files
- Use exact glossary terms in every suggestionin 30 of 811, across 10 files
- Accept dependencies instead of creating themin 24 of 811, across 5 files
- Include before and after visualisations for each candidatein 24 of 811, across 5 files
- Read the domain glossary before exploringin 24 of 811, across 6 files
- Return results instead of producing side effectsin 23 of 811, across 4 files
- Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
- Introduce seams only where things varyin 22 of 811, across 3 files
- Reduce the number of methodsin 21 of 811, across 2 files
- Design deep modules with small interfacesin 21 of 811, across 3 files
Said here and by no other author read
- use hmac sha256 for secure token verification
- verify signatures using timing safe comparison
- follow code conventions and naming rules
- enforce strict type safety constraints
- check security standards
- complete integration validation checklist
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.