[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EV8XYFNWBXP253GZ2C8EW3":3,"skill-same:01M6EV8XYFNWBXP253GZ2C8EW3":122},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":14,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":6,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6EV8XYFNWBXP253GZ2C8EW3","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","henriquescastilho\u002Fmy-claude","henriquescastilho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153296945?v=4","01M6ESH7EXPXTH9CVQ4K16SRG8","Henrique Scheer","01M6ESH7JHEK2PTNNH4HEH787Z",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"implementing kubernetes pod security standards","security standards","standards","kubernetes","security","PS","de","id","define","three","cm","container","cybersecurity","containers","PSA","baseline","pod-security","controller","container-security","pr","2026-11-10 10:12:30",false,"---\nname: implementing-kubernetes-pod-security-standards\ndescription: Pod Security Standards (PSS) define three levels of security policies\n  -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission\n  (PSA) controller built into Kubernetes 1.25+. PS\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- containers\n- kubernetes\n- security\n- pod-security\n- PSA\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\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":52,"author":53,"domain":39,"license":15,"version":54,"nist_csf":55,"subdomain":45,"description":7,"mitre_attack":60},[40,30,31,43,41],"mahipal","1.0",[56,57,58,59],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[61,62,63,64],"T1610","T1611","T1609","T1525","main","7925716f065257435fdb12e97f7e52842147d5ad",".claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude","https:\u002F\u002Fclaude.com\u002Fclaude-code","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho","Software · Applied AI · Quantitative Modeling · Building with Claude.","2026-06-10 12:24:46",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add henriquescastilho\u002Fmy-claude --skill implementing-kubernetes-pod-security-standards",{"tool":79,"command":80},"bunx","bunx skills add henriquescastilho\u002Fmy-claude --skill implementing-kubernetes-pod-security-standards",{"tool":82,"command":83},"pnpm","pnpm dlx skills add henriquescastilho\u002Fmy-claude --skill implementing-kubernetes-pod-security-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FSKILL.md",true,[87,93,98,104,108,112,118],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Ftemplate.md","ASSET","资产文件",1681,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fassets\u002Ftemplate.md",{"path":94,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002FLICENSE",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fapi-reference.md","REFERENCE","参考文档",1575,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fapi-reference.md",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fstandards.md",3276,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fstandards.md",{"path":109,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fworkflows.md",3701,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Freferences\u002Fworkflows.md",{"path":113,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Fagent.py","SCRIPT","脚本",7680,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fscripts\u002Fagent.py",{"path":119,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fprocess.py",11335,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-kubernetes-pod-security-standards\u002Fscripts\u002Fprocess.py",[123,164,173,182,204,230],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":144,"publishedAt":47},"01M6F0B6XPQ65AX2X0DWK8KT3E","markitdown","Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.","MIT","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[130,133,136,139],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[125,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163],"docx","PDF","pptx","xlsx","documents","csv","ocr","Audio","Bash","markdown","convert","read","write","edit","html","images","files","youtube","with",{"skillNo":165,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":172,"publishedAt":47},"01M6F06SBHR9F0SDWE282Y8075","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002Fscientific_writer\u002F.claude\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[168,169,170,171],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},[125,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163],{"skillNo":174,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":181,"publishedAt":47},"01M6F02D4R14EJAPBWVDF9J9VQ","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-writer\u002F.claude\u002Fskills\u002Fmarkitdown\u002FSKILL.md",[177,178,179,180],{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},[125,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":47},"01M6F000KS6YB4MKS774G4R8ND","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fzarr-python\u002FSKILL.md",[],[189,190,191,192,193,194,195,196,197,198,199,200,201,202,203],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":211,"publishedAt":47},"01M6EZZJWFXM1GR78KTW6J0DN8","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fwhat-if-oracle\u002FSKILL.md",[210],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[212,213,214,215,216,217,218,219,220,221,222,156,157,223,224,225,226,227,228,229],"oracle","what if oracle","go","run","ux","futures","analysis","explore","decision","branch","question","idea","exploration","options","stress-test","strategies","scenario","stress",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":246,"publishedAt":47},"01M6EZZCXAEB49RXGQCJX5E8GB","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.codex\u002Fvendor_imports\u002Fclaude\u002Fmarketplaces\u002Fclaude-scientific-skills\u002Fscientific-skills\u002Fvenue-templates\u002FSKILL.md",[236,239,242,243],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":240,"categoryName":241,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":244,"categoryName":245,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000036","内容创作者",[247,248,249,250,251,252,253,254,153,255,156,157,158,256,257,258,259,260,203,261],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","access","proposals","Academic","requirements","formatting","journal","chi"]