Defense-in-depth Kubernetes security through network policies, pod security standards, RBAC, and admission control.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add wshobson/agents --skill k8s-security-policiesCompatible with
Supported agents
Covers three pod security levels (Privileged, Baseline, Restricted) enforced via namespace labels for graduated security posture
Provides NetworkPolicy templates for default-deny, service-to-service communication, and DNS egress patterns
Includes RBAC configuration examples for roles, cluster roles, and bindings to implement least-privilege access
Demonstrates OPA Ga
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionk8s-security-policiesExecute the skills CLI command in your project's root directory to begin installation:
epx add wshobson/agents --skill k8s-security-policiesFetches k8s-security-policies from wshobson/agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/k8s-security-policies
Restart Cursor to activate k8s-security-policies. Access via /k8s-security-policiesin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
python-code-style
wshobson/agents · Backend · same repo
python-design-patterns
wshobson/agents · Frontend · same repo
python-performance-optimization
wshobson/agents · Backend · same repo
monorepo-management
wshobson/agents · Productivity · same repo
react-native-design
wshobson/agents · Frontend · same repo
postgresql-table-design
wshobson/agents · Frontend · same repo
Registry listing for k8s-security-policies matched our evaluation — installs cleanly and behaves as described in the markdown.
k8s-security-policies has been reliable in day-to-day use. Documentation quality is above average for community skills.
k8s-security-policies reduced setup friction for our internal harness; good balance of opinion and flexibility.
k8s-security-policies is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
k8s-security-policies has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: k8s-security-policies is the kind of skill you can hand to a new teammate without a long onboarding doc.
k8s-security-policies reduced setup friction for our internal harness; good balance of opinion and flexibility.
k8s-security-policies fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend k8s-security-policies for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added k8s-security-policies from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 53