[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EVC9RB9XV1P6WDH4D7N41K":3,"skill-same:01M6EVC9RB9XV1P6WDH4D7N41K":120},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":14,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6EVC9RB9XV1P6WDH4D7N41K","implementing-pod-security-admission-controller",null,"Implement Kubernetes Pod Security Admission to enforce baseline and restricted security profiles at namespace level using built-in admission controller.","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-pod-security-admission-controller\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"security","controller","implementing pod security admission controller","de","kubernetes","id","enforce","standards","cm","container","PS","admission-controller","pod-security-standards","pod-security-admission","baseline","security-standards","container-security","pr","implement","cybersecurity","2026-11-10 10:12:30",false,"---\nname: implementing-pod-security-admission-controller\ndescription: Implement Kubernetes Pod Security Admission to enforce baseline and restricted\n  security profiles at namespace level using built-in admission controller.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- pod-security-admission\n- psa\n- pod-security-standards\n- admission-controller\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\n# Implementing Pod Security Admission Controller\n\n## Overview\n\nPod Security Admission (PSA) is a built-in Kubernetes admission controller (stable since v1.25) that enforces Pod Security Standards at the namespace level. It replaces the deprecated PodSecurityPolicy (PSP) and provides three security profiles: Privileged, Baseline, and Restricted, with three enforcement modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing pod security admission controller 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 v1.25+ (PSA is stable\u002FGA)\n- kubectl with cluster-admin access\n- No dependency on external tools - PSA is built into kube-apiserver\n\n## Pod Security Standards\n\n### Privileged Profile\n- **Unrestricted** - No restrictions applied\n- Use case: System-level pods (kube-system, monitoring)\n\n### Baseline Profile\n- **Minimally restrictive** - Prevents known privilege escalation\n- Blocks: privileged containers, hostPID, hostIPC, hostNetwork, hostPorts, certain volume types, adding capabilities beyond runtime defaults\n\n### Restricted Profile\n- **Heavily restricted** - Follows security best practices\n- Requires: non-root, drop ALL capabilities, seccomp RuntimeDefault, read-only root filesystem considerations\n- Blocks: Everything in Baseline plus running as root, privilege escalation, non-approved volume types\n\n## Enforcement Modes\n\n| Mode | Behavior | Use Case |\n|------|----------|----------|\n| enforce | Reject pods violating policy | Production enforcement |\n| audit | Log violations to audit log | Pre-enforcement assessment |\n| warn | Show warnings to user | Developer feedback |\n\n## Implementation\n\n### Apply to Namespace via Labels\n\n```yaml\n# Restricted enforcement with audit and warn\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Baseline enforcement for staging\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Privileged for system namespaces\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n```\n\n### Apply Labels with kubectl\n\n```bash\n# Set restricted enforcement\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Fenforce-version=v1.28 \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Set baseline enforcement\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\n# Check current labels\nkubectl get namespace production -o jsonpath='{.metadata.labels}' | jq .\n```\n\n## Dry-Run Testing\n\n```bash\n# Test what would happen with restricted policy on a namespace\nkubectl label --dry-run=server --overwrite namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Output shows existing pods that would violate the policy\n# Warning: existing pods in namespace \"staging\" violate the new PodSecurity enforce level \"restricted:latest\"\n```\n\n## Cluster-Wide Defaults (AdmissionConfiguration)\n\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: AdmissionConfiguration\nplugins:\n  - name: PodSecurity\n    configuration:\n      apiVersion: pod-security.admission.config.k8s.io\u002Fv1\n      kind: PodSecurityConfiguration\n      defaults:\n        enforce: baseline\n        enforce-version: latest\n        audit: restricted\n        audit-version: latest\n        warn: restricted\n        warn-version: latest\n      exemptions:\n        usernames: []\n        runtimeClasses: []\n        namespaces:\n          - kube-system\n          - kube-public\n          - kube-node-lease\n          - calico-system\n          - gatekeeper-system\n          - monitoring\n          - falco\n```\n\n### Apply to API Server\n\n```bash\n# Add to kube-apiserver manifests\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --admission-control-config-file=\u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n    volumeMounts:\n    - name: psa-config\n      mountPath: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      readOnly: true\n  volumes:\n  - name: psa-config\n    hostPath:\n      path: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      type: File\n```\n\n## Compliant Pod Examples\n\n### Restricted-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: restricted-pod\n  namespace: production\nspec:\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    runAsGroup: 3000\n    fsGroup: 2000\n    seccompProfile:\n      type: RuntimeDefault\n  automountServiceAccountToken: false\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n        requests:\n          cpu: 100m\n          memory: 128Mi\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n### Baseline-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: baseline-pod\n  namespace: staging\nspec:\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n```\n\n## Migration from PodSecurityPolicy\n\n### Step 1: Audit Current State\n```bash\n# Check existing PSPs\nkubectl get psp\n\n# Check which service accounts use which PSP\nkubectl get clusterrolebinding -o json | \\\n  jq '.items[] | select(.roleRef.name | startswith(\"psp-\")) | {name: .metadata.name, subjects: .subjects}'\n```\n\n### Step 2: Map PSP to PSA Profiles\n```bash\n# For each namespace, determine required PSA level\nfor ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}'); do\n  echo \"Namespace: $ns\"\n  kubectl label --dry-run=server namespace $ns \\\n    pod-security.kubernetes.io\u002Fenforce=restricted 2>&1 | head -5\ndone\n```\n\n### Step 3: Apply PSA Labels (Audit First)\n```bash\n# Start with audit mode\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n```\n\n### Step 4: Review and Fix Violations\n```bash\n# Check audit logs for violations\nkubectl get events --field-selector reason=FailedCreate -A\n```\n\n### Step 5: Enable Enforcement\n```bash\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n```\n\n## Monitoring\n\n```bash\n# Check PSA violations in events\nkubectl get events --all-namespaces --field-selector reason=FailedCreate\n\n# Check audit logs\nkubectl logs -n kube-system kube-apiserver-* | grep \"pod-security.kubernetes.io\"\n\n# List namespace PSA labels\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n## Best Practices\n\n1. **Start with audit+warn** before enforce to assess impact\n2. **Use dry-run** to test enforcement before applying\n3. **Exempt system namespaces** (kube-system, monitoring) in cluster defaults\n4. **Pin version** (enforce-version) for predictable behavior across upgrades\n5. **Set cluster-wide baseline** as default, then restrict specific namespaces\n6. **Combine with Gatekeeper** for additional custom policies beyond PSA\n7. **Use restricted profile** for all production workloads\n8. **Document exemptions** with clear justification\n","# Implementing Pod Security Admission Controller\n\n## Overview\n\nPod Security Admission (PSA) is a built-in Kubernetes admission controller (stable since v1.25) that enforces Pod Security Standards at the namespace level. It replaces the deprecated PodSecurityPolicy (PSP) and provides three security profiles: Privileged, Baseline, and Restricted, with three enforcement modes: enforce, audit, and warn.\n\n\n## When to Use\n\n- When deploying or configuring implementing pod security admission controller 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 v1.25+ (PSA is stable\u002FGA)\n- kubectl with cluster-admin access\n- No dependency on external tools - PSA is built into kube-apiserver\n\n## Pod Security Standards\n\n### Privileged Profile\n- **Unrestricted** - No restrictions applied\n- Use case: System-level pods (kube-system, monitoring)\n\n### Baseline Profile\n- **Minimally restrictive** - Prevents known privilege escalation\n- Blocks: privileged containers, hostPID, hostIPC, hostNetwork, hostPorts, certain volume types, adding capabilities beyond runtime defaults\n\n### Restricted Profile\n- **Heavily restricted** - Follows security best practices\n- Requires: non-root, drop ALL capabilities, seccomp RuntimeDefault, read-only root filesystem considerations\n- Blocks: Everything in Baseline plus running as root, privilege escalation, non-approved volume types\n\n## Enforcement Modes\n\n| Mode | Behavior | Use Case |\n|------|----------|----------|\n| enforce | Reject pods violating policy | Production enforcement |\n| audit | Log violations to audit log | Pre-enforcement assessment |\n| warn | Show warnings to user | Developer feedback |\n\n## Implementation\n\n### Apply to Namespace via Labels\n\n```yaml\n# Restricted enforcement with audit and warn\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: production\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: restricted\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Baseline enforcement for staging\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: staging\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: baseline\n    pod-security.kubernetes.io\u002Fenforce-version: v1.28\n    pod-security.kubernetes.io\u002Faudit: restricted\n    pod-security.kubernetes.io\u002Faudit-version: v1.28\n    pod-security.kubernetes.io\u002Fwarn: restricted\n    pod-security.kubernetes.io\u002Fwarn-version: v1.28\n```\n\n```yaml\n# Privileged for system namespaces\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: kube-system\n  labels:\n    pod-security.kubernetes.io\u002Fenforce: privileged\n```\n\n### Apply Labels with kubectl\n\n```bash\n# Set restricted enforcement\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted \\\n  pod-security.kubernetes.io\u002Fenforce-version=v1.28 \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n\n# Set baseline enforcement\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\n# Check current labels\nkubectl get namespace production -o jsonpath='{.metadata.labels}' | jq .\n```\n\n## Dry-Run Testing\n\n```bash\n# Test what would happen with restricted policy on a namespace\nkubectl label --dry-run=server --overwrite namespace staging \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n\n# Output shows existing pods that would violate the policy\n# Warning: existing pods in namespace \"staging\" violate the new PodSecurity enforce level \"restricted:latest\"\n```\n\n## Cluster-Wide Defaults (AdmissionConfiguration)\n\n```yaml\n# \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: AdmissionConfiguration\nplugins:\n  - name: PodSecurity\n    configuration:\n      apiVersion: pod-security.admission.config.k8s.io\u002Fv1\n      kind: PodSecurityConfiguration\n      defaults:\n        enforce: baseline\n        enforce-version: latest\n        audit: restricted\n        audit-version: latest\n        warn: restricted\n        warn-version: latest\n      exemptions:\n        usernames: []\n        runtimeClasses: []\n        namespaces:\n          - kube-system\n          - kube-public\n          - kube-node-lease\n          - calico-system\n          - gatekeeper-system\n          - monitoring\n          - falco\n```\n\n### Apply to API Server\n\n```bash\n# Add to kube-apiserver manifests\n# \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\nspec:\n  containers:\n  - command:\n    - kube-apiserver\n    - --admission-control-config-file=\u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n    volumeMounts:\n    - name: psa-config\n      mountPath: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      readOnly: true\n  volumes:\n  - name: psa-config\n    hostPath:\n      path: \u002Fetc\u002Fkubernetes\u002Fpsa-config.yaml\n      type: File\n```\n\n## Compliant Pod Examples\n\n### Restricted-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: restricted-pod\n  namespace: production\nspec:\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    runAsGroup: 3000\n    fsGroup: 2000\n    seccompProfile:\n      type: RuntimeDefault\n  automountServiceAccountToken: false\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n        requests:\n          cpu: 100m\n          memory: 128Mi\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n### Baseline-Compliant Pod\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: baseline-pod\n  namespace: staging\nspec:\n  containers:\n    - name: app\n      image: myregistry\u002Fmyapp:v1.0.0\n      securityContext:\n        allowPrivilegeEscalation: false\n      resources:\n        limits:\n          cpu: 500m\n          memory: 256Mi\n```\n\n## Migration from PodSecurityPolicy\n\n### Step 1: Audit Current State\n```bash\n# Check existing PSPs\nkubectl get psp\n\n# Check which service accounts use which PSP\nkubectl get clusterrolebinding -o json | \\\n  jq '.items[] | select(.roleRef.name | startswith(\"psp-\")) | {name: .metadata.name, subjects: .subjects}'\n```\n\n### Step 2: Map PSP to PSA Profiles\n```bash\n# For each namespace, determine required PSA level\nfor ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}'); do\n  echo \"Namespace: $ns\"\n  kubectl label --dry-run=server namespace $ns \\\n    pod-security.kubernetes.io\u002Fenforce=restricted 2>&1 | head -5\ndone\n```\n\n### Step 3: Apply PSA Labels (Audit First)\n```bash\n# Start with audit mode\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Faudit=restricted \\\n  pod-security.kubernetes.io\u002Fwarn=restricted\n```\n\n### Step 4: Review and Fix Violations\n```bash\n# Check audit logs for violations\nkubectl get events --field-selector reason=FailedCreate -A\n```\n\n### Step 5: Enable Enforcement\n```bash\nkubectl label namespace production \\\n  pod-security.kubernetes.io\u002Fenforce=restricted\n```\n\n## Monitoring\n\n```bash\n# Check PSA violations in events\nkubectl get events --all-namespaces --field-selector reason=FailedCreate\n\n# Check audit logs\nkubectl logs -n kube-system kube-apiserver-* | grep \"pod-security.kubernetes.io\"\n\n# List namespace PSA labels\nkubectl get namespaces -L pod-security.kubernetes.io\u002Fenforce\n```\n\n## Best Practices\n\n1. **Start with audit+warn** before enforce to assess impact\n2. **Use dry-run** to test enforcement before applying\n3. **Exempt system namespaces** (kube-system, monitoring) in cluster defaults\n4. **Pin version** (enforce-version) for predictable behavior across upgrades\n5. **Set cluster-wide baseline** as default, then restrict specific namespaces\n6. **Combine with Gatekeeper** for additional custom policies beyond PSA\n7. **Use restricted profile** for all production workloads\n8. **Document exemptions** with clear justification\n",{"name":5,"tags":49,"author":51,"domain":43,"license":15,"version":52,"nist_csf":53,"subdomain":40,"description":7,"mitre_attack":58},[28,37,50,36,35],"psa","mahipal","1.0",[54,55,56,57],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[59,60,61,62],"T1610","T1611","T1609","T1525","main","7925716f065257435fdb12e97f7e52842147d5ad",".claude\u002Fskills\u002Fimplementing-pod-security-admission-controller","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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add henriquescastilho\u002Fmy-claude --skill implementing-pod-security-admission-controller",{"tool":77,"command":78},"bunx","bunx skills add henriquescastilho\u002Fmy-claude --skill implementing-pod-security-admission-controller",{"tool":80,"command":81},"pnpm","pnpm dlx skills add henriquescastilho\u002Fmy-claude --skill implementing-pod-security-admission-controller","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FSKILL.md",true,[85,91,96,102,106,110,116],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Ftemplate.md","ASSET","资产文件",1290,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fassets\u002Ftemplate.md",{"path":92,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002FLICENSE",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fapi-reference.md","REFERENCE","参考文档",5229,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fapi-reference.md",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fstandards.md",1099,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fstandards.md",{"path":107,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fworkflows.md",1066,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Freferences\u002Fworkflows.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fagent.py","SCRIPT","脚本",11706,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fscripts\u002Fagent.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fprocess.py",5185,"https:\u002F\u002Fgithub.com\u002Fhenriquescastilho\u002Fmy-claude\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-pod-security-admission-controller\u002Fscripts\u002Fprocess.py",[121,162,171,180,202,230],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":142,"publishedAt":44},"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",[128,131,134,137],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[123,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161],"docx","PDF","pptx","xlsx","documents","csv","ocr","Audio","Bash","markdown","convert","read","write","edit","html","images","files","youtube","with",{"skillNo":163,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":170,"publishedAt":44},"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",[166,167,168,169],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},[123,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161],{"skillNo":172,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":179,"publishedAt":44},"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",[175,176,177,178],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},[123,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161],{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":44},"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",[],[187,188,189,190,191,192,193,194,195,196,197,198,199,200,201],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":211,"publishedAt":44},"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",[208],{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[212,213,214,215,216,217,218,219,220,221,222,154,155,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":125,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":246,"publishedAt":44},"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":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":244,"categoryName":245,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000036","内容创作者",[247,248,249,250,251,252,253,254,151,255,154,155,156,256,257,258,259,260,201,261],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","access","proposals","Academic","requirements","formatting","journal","chi"]