[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78QVBAM8Z417K0EQTFRXY0A":3,"skill-same:01M78QVBAM8Z417K0EQTFRXY0A":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M78QVBAM8Z417K0EQTFRXY0A","implementing-kubernetes-pod-security-standards",null,"Pod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PS","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-kubernetes-pod-security-standards\ndescription: Pod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PS\ndomain: cybersecurity\nsubdomain: container-security\ntags: [containers, kubernetes, security, pod-security, PSA]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Implementing Kubernetes Pod Security Standards\n\n## Overview\n\nPod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PSA replaces the deprecated PodSecurityPolicy and provides namespace-level enforcement with three modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing kubernetes pod security standards capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Kubernetes cluster 1.25+ (PSA GA)\n- kubectl configured with cluster-admin access\n- Understanding of Linux capabilities and security contexts\n\n## Core Concepts\n\n### Three Security Profiles\n\n| Profile | Purpose | Restrictions |\n|---------|---------|-------------|\n| **Privileged** | Unrestricted, system workloads | None |\n| **Baseline** | Prevents known escalations | No hostNetwork, hostPID, hostIPC, privileged containers, dangerous capabilities |\n| **Restricted** | Hardened best practices | Non-root, drop ALL caps, seccomp required, read-only rootfs recommended |\n\n### Three Enforcement Modes\n\n| Mode | Behavior |\n|------|----------|\n| **enforce** | Rejects pods that violate the policy |\n| **audit** | Logs violations in audit log but allows pod |\n| **warn** | Returns warning to user but allows pod |\n\n## Workflow\n\n### Step 1: Label Namespaces for PSA\n\n```yaml\n# Restricted namespace - production workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Baseline namespace - general workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Privileged namespace - system components only\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n```\n\n### Step 2: Apply Labels to Existing Namespaces\n\n```bash\n# Apply restricted enforcement to production\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Apply baseline to staging with restricted warnings\nkubectl label namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Check labels on all namespaces\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n### Step 3: Create Compliant Pod Specs\n\n```yaml\n# Restricted-compliant deployment\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: secure-app\n  namespace: production\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: secure-app\n  template:\n    metadata:\n      labels:\n        app: secure-app\n    spec:\n      automountServiceAccountToken: false\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 65534\n        runAsGroup: 65534\n        fsGroup: 65534\n        seccompProfile:\n          type: RuntimeDefault\n      containers:\n        - name: app\n          image: myregistry.com\u002Fmyapp:v1.0.0@sha256:abc123\n          ports:\n            - containerPort: 8080\n              protocol: TCP\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop:\n                - ALL\n            runAsNonRoot: true\n            runAsUser: 65534\n          resources:\n            requests:\n              memory: \"64Mi\"\n              cpu: \"100m\"\n            limits:\n              memory: \"256Mi\"\n              cpu: \"500m\"\n          volumeMounts:\n            - name: tmp\n              mountPath: \u002Ftmp\n            - name: cache\n              mountPath: \u002Fvar\u002Fcache\n      volumes:\n        - name: tmp\n          emptyDir:\n            sizeLimit: 100Mi\n        - name: cache\n          emptyDir:\n            sizeLimit: 50Mi\n```\n\n### Step 4: Gradual Migration Strategy\n\n```bash\n# Phase 1: Audit mode - discover violations without blocking\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Check audit logs for violations\nkubectl logs -n kube-system -l component=kube-apiserver | grep \"pod-security\"\n\n# Phase 2: Enforce baseline, warn on restricted\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Phase 3: Full restricted enforcement\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  --overwrite\n```\n\n### Step 5: Dry-Run Enforcement Testing\n\n```bash\n# Test what would happen with restricted enforcement\nkubectl label --dry-run=server --overwrite namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Example output:\n# Warning: existing pods in namespace \"my-namespace\" violate the new\n# PodSecurity enforce level \"restricted:latest\"\n# Warning: nginx-xxx: allowPrivilegeEscalation != false,\n#   unrestricted capabilities, runAsNonRoot != true, seccompProfile\n```\n\n## Baseline Profile Restrictions\n\n| Control | Restricted | Requirement |\n|---------|-----------|-------------|\n| HostProcess | Must not set | Pods cannot use Windows HostProcess |\n| Host Namespaces | Must not set | No hostNetwork, hostPID, hostIPC |\n| Privileged | Must not set | No privileged: true |\n| Capabilities | Baseline list only | Only NET_BIND_SERVICE, drop ALL for restricted |\n| HostPath Volumes | Must not use | No hostPath volume mounts |\n| Host Ports | Must not use | No hostPort in container spec |\n| AppArmor | Default\u002Fruntime | Cannot set to unconfined |\n| SELinux | Limited types | Only container_t, container_init_t, container_kvm_t |\n| \u002Fproc Mount Type | Default only | Must use Default proc mount |\n| Seccomp | RuntimeDefault or Localhost | Must specify seccomp profile (restricted) |\n| Sysctls | Safe set only | Limited to safe sysctls |\n\n## Validation Commands\n\n```bash\n# Verify namespace labels\nkubectl get ns --show-labels | grep pod-security\n\n# Test pod creation against policy\nkubectl run test-pod --image=nginx --namespace=production --dry-run=server\n\n# Check for violations in audit logs\nkubectl get events --field-selector reason=FailedCreate -A\n\n# Scan with Kubescape for PSS compliance\nkubescape scan framework nsa --namespace production\n```\n\n## References\n\n- [Pod Security Standards - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n- [Pod Security Admission - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-admission\u002F)\n- [Migrate from PodSecurityPolicy](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fconfigure-pod-container\u002Fmigrate-from-psp\u002F)\n- [Kubescape PSS Scanner](https:\u002F\u002Fgithub.com\u002Fkubescape\u002Fkubescape)\n","# Implementing Kubernetes Pod Security Standards\n\n## Overview\n\nPod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PSA replaces the deprecated PodSecurityPolicy and provides namespace-level enforcement with three modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing kubernetes pod security standards capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Kubernetes cluster 1.25+ (PSA GA)\n- kubectl configured with cluster-admin access\n- Understanding of Linux capabilities and security contexts\n\n## Core Concepts\n\n### Three Security Profiles\n\n| Profile | Purpose | Restrictions |\n|---------|---------|-------------|\n| **Privileged** | Unrestricted, system workloads | None |\n| **Baseline** | Prevents known escalations | No hostNetwork, hostPID, hostIPC, privileged containers, dangerous capabilities |\n| **Restricted** | Hardened best practices | Non-root, drop ALL caps, seccomp required, read-only rootfs recommended |\n\n### Three Enforcement Modes\n\n| Mode | Behavior |\n|------|----------|\n| **enforce** | Rejects pods that violate the policy |\n| **audit** | Logs violations in audit log but allows pod |\n| **warn** | Returns warning to user but allows pod |\n\n## Workflow\n\n### Step 1: Label Namespaces for PSA\n\n```yaml\n# Restricted namespace - production workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Baseline namespace - general workloads\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: latest\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: latest\n```\n\n```yaml\n# Privileged namespace - system components only\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n    pod-security.kubernetes.io\u002Fenforce-version: latest\n```\n\n### Step 2: Apply Labels to Existing Namespaces\n\n```bash\n# Apply restricted enforcement to production\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Apply baseline to staging with restricted warnings\nkubectl label namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Check labels on all namespaces\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n### Step 3: Create Compliant Pod Specs\n\n```yaml\n# Restricted-compliant deployment\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: secure-app\n  namespace: production\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: secure-app\n  template:\n    metadata:\n      labels:\n        app: secure-app\n    spec:\n      automountServiceAccountToken: false\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 65534\n        runAsGroup: 65534\n        fsGroup: 65534\n        seccompProfile:\n          type: RuntimeDefault\n      containers:\n        - name: app\n          image: myregistry.com\u002Fmyapp:v1.0.0@sha256:abc123\n          ports:\n            - containerPort: 8080\n              protocol: TCP\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop:\n                - ALL\n            runAsNonRoot: true\n            runAsUser: 65534\n          resources:\n            requests:\n              memory: \"64Mi\"\n              cpu: \"100m\"\n            limits:\n              memory: \"256Mi\"\n              cpu: \"500m\"\n          volumeMounts:\n            - name: tmp\n              mountPath: \u002Ftmp\n            - name: cache\n              mountPath: \u002Fvar\u002Fcache\n      volumes:\n        - name: tmp\n          emptyDir:\n            sizeLimit: 100Mi\n        - name: cache\n          emptyDir:\n            sizeLimit: 50Mi\n```\n\n### Step 4: Gradual Migration Strategy\n\n```bash\n# Phase 1: Audit mode - discover violations without blocking\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Check audit logs for violations\nkubectl logs -n kube-system -l component=kube-apiserver | grep \"pod-security\"\n\n# Phase 2: Enforce baseline, warn on restricted\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=baseline \\\n  pod-security.kubernetes.io\u002Fwarn=restricted \\\n  --overwrite\n\n# Phase 3: Full restricted enforcement\nkubectl label namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  --overwrite\n```\n\n### Step 5: Dry-Run Enforcement Testing\n\n```bash\n# Test what would happen with restricted enforcement\nkubectl label --dry-run=server --overwrite namespace my-namespace \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Example output:\n# Warning: existing pods in namespace \"my-namespace\" violate the new\n# PodSecurity enforce level \"restricted:latest\"\n# Warning: nginx-xxx: allowPrivilegeEscalation != false,\n#   unrestricted capabilities, runAsNonRoot != true, seccompProfile\n```\n\n## Baseline Profile Restrictions\n\n| Control | Restricted | Requirement |\n|---------|-----------|-------------|\n| HostProcess | Must not set | Pods cannot use Windows HostProcess |\n| Host Namespaces | Must not set | No hostNetwork, hostPID, hostIPC |\n| Privileged | Must not set | No privileged: true |\n| Capabilities | Baseline list only | Only NET_BIND_SERVICE, drop ALL for restricted |\n| HostPath Volumes | Must not use | No hostPath volume mounts |\n| Host Ports | Must not use | No hostPort in container spec |\n| AppArmor | Default\u002Fruntime | Cannot set to unconfined |\n| SELinux | Limited types | Only container_t, container_init_t, container_kvm_t |\n| \u002Fproc Mount Type | Default only | Must use Default proc mount |\n| Seccomp | RuntimeDefault or Localhost | Must specify seccomp profile (restricted) |\n| Sysctls | Safe set only | Limited to safe sysctls |\n\n## Validation Commands\n\n```bash\n# Verify namespace labels\nkubectl get ns --show-labels | grep pod-security\n\n# Test pod creation against policy\nkubectl run test-pod --image=nginx --namespace=production --dry-run=server\n\n# Check for violations in audit logs\nkubectl get events --field-selector reason=FailedCreate -A\n\n# Scan with Kubescape for PSS compliance\nkubescape scan framework nsa --namespace production\n```\n\n## References\n\n- [Pod Security Standards - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-standards\u002F)\n- [Pod Security Admission - Kubernetes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Fconcepts\u002Fsecurity\u002Fpod-security-admission\u002F)\n- [Migrate from PodSecurityPolicy](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fconfigure-pod-container\u002Fmigrate-from-psp\u002F)\n- [Kubescape PSS Scanner](https:\u002F\u002Fgithub.com\u002Fkubescape\u002Fkubescape)\n",{"name":5,"tags":25,"author":31,"domain":32,"license":15,"version":33,"subdomain":34,"description":7},[26,27,28,29,30],"containers","kubernetes","security","pod-security","PSA","mahipal","cybersecurity","1.0","container-security","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fimplementing-kubernetes-pod-security-standards",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill implementing-kubernetes-pod-security-standards",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill implementing-kubernetes-pod-security-standards",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill implementing-kubernetes-pod-security-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FSKILL.md",true,[58,64,68,74,78,82,88],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Ftemplate.md","ASSET","资产文件",1681,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fassets\u002Ftemplate.md",{"path":65,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fapi-reference.md","REFERENCE","参考文档",1575,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fapi-reference.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fstandards.md",3276,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fstandards.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fworkflows.md",3701,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fworkflows.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fagent.py","SCRIPT","脚本",7680,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fscripts\u002Fagent.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fprocess.py",11335,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fscripts\u002Fprocess.py",[93,101,108,115,122,130],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]