[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73ED1XQ3EM4KBYG9P9GF4MA":3,"skill-same:01M73ED1XQ3EM4KBYG9P9GF4MA":107},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M73ED1XQ3EM4KBYG9P9GF4MA","performing-container-image-hardening",null,"This skill covers hardening container images by minimizing attack surface, removing unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure production-ready images.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: performing-container-image-hardening\ndescription: 'This skill covers hardening container images by minimizing attack surface,\n  removing unnecessary packages, implementing multi-stage builds, configuring non-root\n  users, and applying CIS Docker Benchmark recommendations to produce secure production-ready\n  images.\n\n  '\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- devsecops\n- cicd\n- container-hardening\n- docker\n- cis-benchmark\n- secure-sdlc\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195\n- T1554\n- T1059.004\n- T1610\n- T1611\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n\n# Performing Container Image Hardening\n\n## When to Use\n\n- When building production container images that need minimal attack surface\n- When compliance requires CIS Docker Benchmark adherence for container configurations\n- When reducing image size to minimize vulnerability exposure from unused packages\n- When implementing defense-in-depth for containerized workloads\n- When migrating from fat base images to distroless or minimal images\n\n**Do not use** for runtime container security monitoring (use Falco), for host-level Docker daemon hardening (use CIS Docker Benchmark host checks), or for container orchestration security (use Kubernetes security scanning).\n\n## Prerequisites\n\n- Docker or BuildKit for multi-stage builds\n- Base image options: distroless, Alpine, slim, or scratch\n- Container scanning tool (Trivy) for validation\n- CIS Docker Benchmark reference\n\n## Workflow\n\n### Step 1: Use Multi-Stage Builds to Minimize Image Size\n\n```dockerfile\n# Build stage with all dependencies\nFROM python:3.12-bookworm AS builder\nWORKDIR \u002Fbuild\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --prefix=\u002Finstall -r requirements.txt\nCOPY src\u002F .\u002Fsrc\u002F\nRUN python -m compileall src\u002F\n\n# Production stage with minimal base\nFROM python:3.12-slim-bookworm AS production\nRUN apt-get update && \\\n    apt-get install -y --no-install-recommends libpq5 && \\\n    rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F* && \\\n    apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false\n\nCOPY --from=builder \u002Finstall \u002Fusr\u002Flocal\nCOPY --from=builder \u002Fbuild\u002Fsrc \u002Fapp\u002Fsrc\n\nRUN groupadd -r appuser && useradd -r -g appuser -d \u002Fapp -s \u002Fsbin\u002Fnologin appuser\nRUN chown -R appuser:appuser \u002Fapp\n\nUSER appuser\nWORKDIR \u002Fapp\n\nHEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \\\n  CMD python -c \"import urllib.request; urllib.request.urlopen('http:\u002F\u002Flocalhost:8080\u002Fhealth')\" || exit 1\n\nEXPOSE 8080\nENTRYPOINT [\"python\", \"-m\", \"src.main\"]\n```\n\n### Step 2: Use Distroless Base Images\n\n```dockerfile\n# Go application with distroless\nFROM golang:1.22 AS builder\nWORKDIR \u002Fapp\nCOPY go.* .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 GOOS=linux go build -ldflags=\"-w -s\" -o \u002Fserver .\n\nFROM gcr.io\u002Fdistroless\u002Fstatic-debian12:nonroot\nCOPY --from=builder \u002Fserver \u002Fserver\nUSER nonroot:nonroot\nENTRYPOINT [\"\u002Fserver\"]\n```\n\n### Step 3: Remove Unnecessary Components\n\n```dockerfile\n# Hardened image checklist\nFROM ubuntu:24.04 AS base\n\nRUN apt-get update && \\\n    apt-get install -y --no-install-recommends \\\n      ca-certificates \\\n      libssl3 && \\\n    # Remove package manager to prevent runtime package installation\n    apt-get purge -y --auto-remove apt dpkg && \\\n    rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F* \\\n           \u002Fvar\u002Fcache\u002Fapt\u002F* \\\n           \u002Ftmp\u002F* \\\n           \u002Fvar\u002Ftmp\u002F* \\\n           \u002Fusr\u002Fshare\u002Fdoc\u002F* \\\n           \u002Fusr\u002Fshare\u002Fman\u002F* \\\n           \u002Fusr\u002Fshare\u002Finfo\u002F* \\\n           \u002Froot\u002F.cache\n\n# Remove shells if not needed\nRUN rm -f \u002Fbin\u002Fsh \u002Fbin\u002Fbash \u002Fusr\u002Fbin\u002Fsh 2>\u002Fdev\u002Fnull || true\n\n# Remove setuid\u002Fsetgid binaries\nRUN find \u002F -perm \u002F6000 -type f -exec chmod a-s {} + 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 4: Configure Read-Only Filesystem\n\n```yaml\n# Kubernetes deployment with read-only root filesystem\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: hardened-app\nspec:\n  template:\n    spec:\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 65534\n        fsGroup: 65534\n        seccompProfile:\n          type: RuntimeDefault\n      containers:\n        - name: app\n          image: app:hardened\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop: [\"ALL\"]\n          volumeMounts:\n            - name: tmp\n              mountPath: \u002Ftmp\n            - name: cache\n              mountPath: \u002Fapp\u002Fcache\n      volumes:\n        - name: tmp\n          emptyDir:\n            sizeLimit: 100Mi\n        - name: cache\n          emptyDir:\n            sizeLimit: 50Mi\n```\n\n### Step 5: Pin Base Image by Digest\n\n```dockerfile\n# Pin to exact image digest for reproducibility\nFROM python:3.12-slim-bookworm@sha256:abcdef1234567890 AS production\n# This ensures the exact same base image is used every time\n```\n\n### Step 6: Validate Hardening with Automated Scanning\n\n```bash\n# Scan hardened image with Trivy\ntrivy image --severity HIGH,CRITICAL hardened-app:latest\n\n# Check CIS Docker Benchmark compliance\ndocker run --rm -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock \\\n  aquasec\u002Fdocker-bench-security\n\n# Verify no root processes\ndocker run --rm hardened-app:latest whoami\n# Expected: appuser (NOT root)\n\n# Verify read-only filesystem\ndocker run --rm hardened-app:latest touch \u002Ftest 2>&1\n# Expected: Read-only file system error\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Multi-Stage Build | Docker build technique using multiple FROM stages to separate build and runtime, reducing final image size |\n| Distroless | Google-maintained minimal container images containing only the application and runtime dependencies |\n| Non-Root User | Running container processes as unprivileged user to limit impact of container escape exploits |\n| Read-Only Root | Mounting the container root filesystem as read-only to prevent runtime modification |\n| Image Digest | SHA256 hash uniquely identifying an exact image version, more precise than mutable tags |\n| Scratch Image | Empty Docker base image used for statically compiled binaries requiring no OS |\n| Security Context | Kubernetes pod\u002Fcontainer-level security settings controlling privileges, filesystem, and capabilities |\n\n## Tools & Systems\n\n- **Docker BuildKit**: Advanced Docker build engine supporting multi-stage builds and build secrets\n- **Distroless Images**: Google's minimal container base images (static, base, java, python, nodejs)\n- **docker-bench-security**: Script checking CIS Docker Benchmark compliance\n- **Trivy**: Container image vulnerability and misconfiguration scanner\n- **Hadolint**: Dockerfile linter enforcing best practices\n\n## Common Scenarios\n\n### Scenario: Reducing a 1.2GB Python Image to Under 150MB\n\n**Context**: A data science team uses `python:3.12` as base image (1.2GB) with scientific computing packages. The image has 200+ known CVEs from unnecessary system packages.\n\n**Approach**:\n1. Switch to `python:3.12-slim-bookworm` as base (150MB) and install only required system libraries\n2. Use multi-stage build: compile C extensions in builder stage, copy wheels to production\n3. Pin numpy, pandas, and scipy to pre-built wheels to avoid build dependencies in production\n4. Remove pip, setuptools, and wheel from the final image\n5. Create non-root user and set filesystem permissions\n6. Validate with Trivy: expect CVE count to drop from 200+ to under 20\n\n**Pitfalls**: Some Python packages require shared libraries at runtime (libgomp, libstdc++). Test the application thoroughly after removing system packages. Alpine-based images use musl libc which can cause compatibility issues with numpy and pandas.\n\n## Output Format\n\n```\nContainer Image Hardening Report\n==================================\nImage: app:hardened\nBase: python:3.12-slim-bookworm\nDate: 2026-02-23\n\nSIZE COMPARISON:\n  Before hardening: 1,247 MB (python:3.12)\n  After hardening:  143 MB  (python:3.12-slim + multi-stage)\n  Reduction: 88.5%\n\nSECURITY CHECKS:\n  [PASS] Non-root user configured (appuser:1000)\n  [PASS] HEALTHCHECK instruction present\n  [PASS] No setuid\u002Fsetgid binaries found\n  [PASS] Package manager removed\n  [PASS] Base image pinned by digest\n  [PASS] No shell access (\u002Fbin\u002Fsh removed)\n  [WARN] \u002Ftmp writable (emptyDir mounted)\n\nVULNERABILITY COMPARISON:\n  Before: 234 CVEs (12 Critical, 45 High)\n  After:  18 CVEs (0 Critical, 3 High)\n  Reduction: 92.3%\n```\n","# Performing Container Image Hardening\n\n## When to Use\n\n- When building production container images that need minimal attack surface\n- When compliance requires CIS Docker Benchmark adherence for container configurations\n- When reducing image size to minimize vulnerability exposure from unused packages\n- When implementing defense-in-depth for containerized workloads\n- When migrating from fat base images to distroless or minimal images\n\n**Do not use** for runtime container security monitoring (use Falco), for host-level Docker daemon hardening (use CIS Docker Benchmark host checks), or for container orchestration security (use Kubernetes security scanning).\n\n## Prerequisites\n\n- Docker or BuildKit for multi-stage builds\n- Base image options: distroless, Alpine, slim, or scratch\n- Container scanning tool (Trivy) for validation\n- CIS Docker Benchmark reference\n\n## Workflow\n\n### Step 1: Use Multi-Stage Builds to Minimize Image Size\n\n```dockerfile\n# Build stage with all dependencies\nFROM python:3.12-bookworm AS builder\nWORKDIR \u002Fbuild\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --prefix=\u002Finstall -r requirements.txt\nCOPY src\u002F .\u002Fsrc\u002F\nRUN python -m compileall src\u002F\n\n# Production stage with minimal base\nFROM python:3.12-slim-bookworm AS production\nRUN apt-get update && \\\n    apt-get install -y --no-install-recommends libpq5 && \\\n    rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F* && \\\n    apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false\n\nCOPY --from=builder \u002Finstall \u002Fusr\u002Flocal\nCOPY --from=builder \u002Fbuild\u002Fsrc \u002Fapp\u002Fsrc\n\nRUN groupadd -r appuser && useradd -r -g appuser -d \u002Fapp -s \u002Fsbin\u002Fnologin appuser\nRUN chown -R appuser:appuser \u002Fapp\n\nUSER appuser\nWORKDIR \u002Fapp\n\nHEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \\\n  CMD python -c \"import urllib.request; urllib.request.urlopen('http:\u002F\u002Flocalhost:8080\u002Fhealth')\" || exit 1\n\nEXPOSE 8080\nENTRYPOINT [\"python\", \"-m\", \"src.main\"]\n```\n\n### Step 2: Use Distroless Base Images\n\n```dockerfile\n# Go application with distroless\nFROM golang:1.22 AS builder\nWORKDIR \u002Fapp\nCOPY go.* .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 GOOS=linux go build -ldflags=\"-w -s\" -o \u002Fserver .\n\nFROM gcr.io\u002Fdistroless\u002Fstatic-debian12:nonroot\nCOPY --from=builder \u002Fserver \u002Fserver\nUSER nonroot:nonroot\nENTRYPOINT [\"\u002Fserver\"]\n```\n\n### Step 3: Remove Unnecessary Components\n\n```dockerfile\n# Hardened image checklist\nFROM ubuntu:24.04 AS base\n\nRUN apt-get update && \\\n    apt-get install -y --no-install-recommends \\\n      ca-certificates \\\n      libssl3 && \\\n    # Remove package manager to prevent runtime package installation\n    apt-get purge -y --auto-remove apt dpkg && \\\n    rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F* \\\n           \u002Fvar\u002Fcache\u002Fapt\u002F* \\\n           \u002Ftmp\u002F* \\\n           \u002Fvar\u002Ftmp\u002F* \\\n           \u002Fusr\u002Fshare\u002Fdoc\u002F* \\\n           \u002Fusr\u002Fshare\u002Fman\u002F* \\\n           \u002Fusr\u002Fshare\u002Finfo\u002F* \\\n           \u002Froot\u002F.cache\n\n# Remove shells if not needed\nRUN rm -f \u002Fbin\u002Fsh \u002Fbin\u002Fbash \u002Fusr\u002Fbin\u002Fsh 2>\u002Fdev\u002Fnull || true\n\n# Remove setuid\u002Fsetgid binaries\nRUN find \u002F -perm \u002F6000 -type f -exec chmod a-s {} + 2>\u002Fdev\u002Fnull || true\n```\n\n### Step 4: Configure Read-Only Filesystem\n\n```yaml\n# Kubernetes deployment with read-only root filesystem\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: hardened-app\nspec:\n  template:\n    spec:\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 65534\n        fsGroup: 65534\n        seccompProfile:\n          type: RuntimeDefault\n      containers:\n        - name: app\n          image: app:hardened\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop: [\"ALL\"]\n          volumeMounts:\n            - name: tmp\n              mountPath: \u002Ftmp\n            - name: cache\n              mountPath: \u002Fapp\u002Fcache\n      volumes:\n        - name: tmp\n          emptyDir:\n            sizeLimit: 100Mi\n        - name: cache\n          emptyDir:\n            sizeLimit: 50Mi\n```\n\n### Step 5: Pin Base Image by Digest\n\n```dockerfile\n# Pin to exact image digest for reproducibility\nFROM python:3.12-slim-bookworm@sha256:abcdef1234567890 AS production\n# This ensures the exact same base image is used every time\n```\n\n### Step 6: Validate Hardening with Automated Scanning\n\n```bash\n# Scan hardened image with Trivy\ntrivy image --severity HIGH,CRITICAL hardened-app:latest\n\n# Check CIS Docker Benchmark compliance\ndocker run --rm -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock \\\n  aquasec\u002Fdocker-bench-security\n\n# Verify no root processes\ndocker run --rm hardened-app:latest whoami\n# Expected: appuser (NOT root)\n\n# Verify read-only filesystem\ndocker run --rm hardened-app:latest touch \u002Ftest 2>&1\n# Expected: Read-only file system error\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| Multi-Stage Build | Docker build technique using multiple FROM stages to separate build and runtime, reducing final image size |\n| Distroless | Google-maintained minimal container images containing only the application and runtime dependencies |\n| Non-Root User | Running container processes as unprivileged user to limit impact of container escape exploits |\n| Read-Only Root | Mounting the container root filesystem as read-only to prevent runtime modification |\n| Image Digest | SHA256 hash uniquely identifying an exact image version, more precise than mutable tags |\n| Scratch Image | Empty Docker base image used for statically compiled binaries requiring no OS |\n| Security Context | Kubernetes pod\u002Fcontainer-level security settings controlling privileges, filesystem, and capabilities |\n\n## Tools & Systems\n\n- **Docker BuildKit**: Advanced Docker build engine supporting multi-stage builds and build secrets\n- **Distroless Images**: Google's minimal container base images (static, base, java, python, nodejs)\n- **docker-bench-security**: Script checking CIS Docker Benchmark compliance\n- **Trivy**: Container image vulnerability and misconfiguration scanner\n- **Hadolint**: Dockerfile linter enforcing best practices\n\n## Common Scenarios\n\n### Scenario: Reducing a 1.2GB Python Image to Under 150MB\n\n**Context**: A data science team uses `python:3.12` as base image (1.2GB) with scientific computing packages. The image has 200+ known CVEs from unnecessary system packages.\n\n**Approach**:\n1. Switch to `python:3.12-slim-bookworm` as base (150MB) and install only required system libraries\n2. Use multi-stage build: compile C extensions in builder stage, copy wheels to production\n3. Pin numpy, pandas, and scipy to pre-built wheels to avoid build dependencies in production\n4. Remove pip, setuptools, and wheel from the final image\n5. Create non-root user and set filesystem permissions\n6. Validate with Trivy: expect CVE count to drop from 200+ to under 20\n\n**Pitfalls**: Some Python packages require shared libraries at runtime (libgomp, libstdc++). Test the application thoroughly after removing system packages. Alpine-based images use musl libc which can cause compatibility issues with numpy and pandas.\n\n## Output Format\n\n```\nContainer Image Hardening Report\n==================================\nImage: app:hardened\nBase: python:3.12-slim-bookworm\nDate: 2026-02-23\n\nSIZE COMPARISON:\n  Before hardening: 1,247 MB (python:3.12)\n  After hardening:  143 MB  (python:3.12-slim + multi-stage)\n  Reduction: 88.5%\n\nSECURITY CHECKS:\n  [PASS] Non-root user configured (appuser:1000)\n  [PASS] HEALTHCHECK instruction present\n  [PASS] No setuid\u002Fsetgid binaries found\n  [PASS] Package manager removed\n  [PASS] Base image pinned by digest\n  [PASS] No shell access (\u002Fbin\u002Fsh removed)\n  [WARN] \u002Ftmp writable (emptyDir mounted)\n\nVULNERABILITY COMPARISON:\n  Before: 234 CVEs (12 Critical, 45 High)\n  After:  18 CVEs (0 Critical, 3 High)\n  Reduction: 92.3%\n```\n",{"name":5,"tags":25,"author":32,"domain":33,"source":34,"license":15,"version":35,"nist_csf":36,"subdomain":26,"description":41,"mitre_attack":42,"source_commit":48},[26,27,28,29,30,31],"devsecops","cicd","container-hardening","docker","cis-benchmark","secure-sdlc","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0.0",[37,38,39,40],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04","This skill covers hardening container images by minimizing attack surface, removing unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure production-ready images.\n",[43,44,45,46,47],"T1195","T1554","T1059.004","T1610","T1611","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fperforming-container-image-hardening",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill performing-container-image-hardening",{"tool":65,"command":66},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill performing-container-image-hardening",{"tool":68,"command":69},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill performing-container-image-hardening","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002FSKILL.md",true,[73,79,83,89,93,97,103],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Ftemplate.md","ASSET","资产文件",1391,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002Fassets\u002Ftemplate.md",{"path":80,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fapi-reference.md","REFERENCE","参考文档",5250,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002Freferences\u002Fapi-reference.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstandards.md",953,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002Freferences\u002Fstandards.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fworkflows.md",1827,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002Freferences\u002Fworkflows.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fagent.py","SCRIPT","脚本",11579,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002Fscripts\u002Fagent.py",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fprocess.py",7102,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-container-image-hardening\u002Fscripts\u002Fprocess.py",[108,116,123,131,139,147],{"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":112,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]