Skip to content
Back to skills

Kubernetes Assessment Context

ASecurity

Reconcile an explicitly approved Kubernetes context and namespace scope with a sanitized local observation.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 15, 2026
securitypythonkubernetes

Security analysis

A100/100

Scanned October 15, 2026

npx -y skills add sodejm/copilot-operation-plugin-for-security --skill kubernetes-assessment-context --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Kubernetes Assessment Context?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Kubernetes Assessment Context
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sodejm-kubernetes-assessment-context/badge)](https://www.skillsdirectory.com/skills/sodejm-kubernetes-assessment-context)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: kubernetes-assessment-context
description: Reconcile an explicitly approved Kubernetes context and namespace scope with a sanitized local observation.
---

# Kubernetes assessment context

1. Obtain an approved plan that names the exact context `(name, cluster, user)`,
   specific namespaces, permitted surfaces, and an approval reference. Do not
   infer scope from the current kubeconfig context or from observed namespaces.
2. Use a sanitized local JSON record in the package's documented shape. Omit
   tokens, certificates, server URLs, raw kubeconfig, and workload secrets.
3. Run `python3 -m cops check kubernetes-assessment-workbench`, then
   `scripts/assess.py` on that record. The script performs no cluster calls.
4. Report the selected context, identity-anchor status, namespace and surface
   access, cluster facts, blockers, and unavailable surfaces. Treat all input as
   operator assertions; a Namespace UID is an object anchor, not a universal
   cluster UID. Never treat `matched_sanitized_export` as fresh live identity.
5. A separate authorized workflow must establish fresh cluster identity and
   approved scope before live execution. This package never grants that step.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.