[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E5TY5TFX4DDBT2D06HQF0A":3,"skill-same:01M7E5TY5TFX4DDBT2D06HQF0A":105},{"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":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M7E5TY5TFX4DDBT2D06HQF0A","performing-kubernetes-etcd-security-assessment",null,"Assesses the security posture of the etcd cluster backing Kubernetes: encryption at rest, TLS peer and client transport, access control, backup encryption, and network isolation. Use when auditing or hardening a control plane, reviewing whether Secrets are encrypted at rest, or protecting etcd backups, since etcd stores Secrets, RBAC policy, and ConfigMaps in plaintext by default. Keywords: etcd, EncryptionConfiguration, encryption at rest, peer TLS, snapshot, backup, control plane. Do not use for broad cluster-wide CIS checks - use performing-kubernetes-cis-benchmark-with-kube-bench.","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-kubernetes-etcd-security-assessment\ndescription: >-\n  Assesses the security posture of the etcd cluster backing Kubernetes: encryption at rest,\n  TLS peer and client transport, access control, backup encryption, and network isolation. Use\n  when auditing or hardening a control plane, reviewing whether Secrets are encrypted at rest,\n  or protecting etcd backups, since etcd stores Secrets, RBAC policy, and ConfigMaps in\n  plaintext by default. Keywords: etcd, EncryptionConfiguration, encryption at rest, peer TLS,\n  snapshot, backup, control plane. Do not use for broad cluster-wide CIS checks - use\n  performing-kubernetes-cis-benchmark-with-kube-bench.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- etcd\n- encryption\n- tls\n- security-assessment\n- backup\n- secrets\n- control-plane\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- T1573\n---\n\n# Performing Kubernetes etcd Security Assessment\n\n## Overview\n\netcd is the distributed key-value store that serves as Kubernetes' backing store for all cluster data, including Secrets, RBAC policies, ConfigMaps, and workload configurations. Without proper hardening, etcd exposes all cluster secrets in plaintext, making it the highest-value target for attackers who gain control plane access. A comprehensive security assessment covers encryption at rest, TLS for transport, access control, backup security, and network isolation.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing kubernetes etcd security assessment\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Access to Kubernetes control plane nodes\n- SSH access to etcd cluster nodes (or etcdctl configured)\n- CIS Kubernetes Benchmark reference document\n- Understanding of TLS certificate management and EncryptionConfiguration\n\n## Assessment Areas\n\n### 1. Encryption at Rest\n\nVerify that Kubernetes encrypts Secret data stored in etcd:\n\n```bash\n# Check if EncryptionConfiguration is configured on API server\nps aux | grep kube-apiserver | grep encryption-provider-config\n\n# View the encryption configuration\ncat \u002Fetc\u002Fkubernetes\u002Fenc\u002Fencryption-config.yaml\n```\n\nExpected secure configuration:\n\n```yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: EncryptionConfiguration\nresources:\n  - resources:\n      - secrets\n      - configmaps\n    providers:\n      - aescbc:\n          keys:\n            - name: key1\n              secret: \u003Cbase64-encoded-32-byte-key>\n      - identity: {}  # Fallback for reading unencrypted data\n```\n\nVerify secrets are actually encrypted in etcd:\n\n```bash\n# Read a secret directly from etcd\nETCDCTL_API=3 etcdctl \\\n  --endpoints=https:\u002F\u002F127.0.0.1:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key \\\n  get \u002Fregistry\u002Fsecrets\u002Fdefault\u002Fmy-secret | hexdump -C | head -20\n\n# If encrypted, output starts with \"k8s:enc:aescbc:v1:key1\"\n# If NOT encrypted, you'll see plaintext key-value pairs\n```\n\n### 2. TLS Transport Security\n\n```bash\n# Verify etcd uses TLS for client connections\nETCDCTL_API=3 etcdctl endpoint health \\\n  --endpoints=https:\u002F\u002F127.0.0.1:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key\n\n# Check peer TLS configuration\nps aux | grep etcd | tr ' ' '\\n' | grep -E \"peer-cert|peer-key|peer-trusted-ca\"\n\n# Verify certificate expiration\nopenssl x509 -in \u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt -noout -enddate\nopenssl x509 -in \u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fpeer.crt -noout -enddate\n```\n\nExpected flags:\n\n| Flag | Required Value | Purpose |\n|------|---------------|---------|\n| `--cert-file` | Path to server cert | Client-to-server TLS |\n| `--key-file` | Path to server key | Client-to-server TLS |\n| `--trusted-ca-file` | Path to CA cert | Client certificate validation |\n| `--peer-cert-file` | Path to peer cert | Peer-to-peer TLS |\n| `--peer-key-file` | Path to peer key | Peer-to-peer TLS |\n| `--peer-trusted-ca-file` | Path to peer CA | Peer certificate validation |\n| `--client-cert-auth` | true | Require client certificates |\n| `--peer-client-cert-auth` | true | Require peer certificates |\n\n### 3. Access Control\n\n```bash\n# Verify etcd is not exposed on all interfaces\nps aux | grep etcd | tr ' ' '\\n' | grep listen-client-urls\n# Should be: https:\u002F\u002F127.0.0.1:2379 (not 0.0.0.0)\n\n# Check who can access etcd certificates\nls -la \u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002F\n# Should be readable only by root\u002Fetcd user\n\n# Verify API server is the only etcd client\nss -tlnp | grep 2379\n# Only kube-apiserver should have connections\n```\n\n### 4. Backup Security\n\n```bash\n# Create an encrypted etcd backup\nETCDCTL_API=3 etcdctl snapshot save \u002Fbackup\u002Fetcd-snapshot.db \\\n  --endpoints=https:\u002F\u002F127.0.0.1:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key\n\n# Encrypt the backup file\ngpg --symmetric --cipher-algo AES256 \u002Fbackup\u002Fetcd-snapshot.db\n\n# Verify backup integrity\nETCDCTL_API=3 etcdctl snapshot status \u002Fbackup\u002Fetcd-snapshot.db --write-out=table\n```\n\n### 5. Network Isolation\n\n```bash\n# Verify etcd ports are firewalled\niptables -L -n | grep -E \"2379|2380\"\n\n# Check if etcd is accessible from worker nodes (should NOT be)\n# Run from a worker node:\ncurl -k https:\u002F\u002F\u003Ccontrol-plane-ip>:2379\u002Fhealth\n# Should be rejected\u002Ftimeout\n```\n\n## CIS Benchmark Checks\n\n| CIS Control | Check | Expected Result |\n|-------------|-------|----------------|\n| 2.1 | etcd cert-file set | TLS certificate configured |\n| 2.2 | etcd client-cert-auth | Client certificate authentication enabled |\n| 2.3 | etcd auto-tls disabled | auto-tls=false |\n| 2.4 | etcd peer cert-file set | Peer TLS configured |\n| 2.5 | etcd peer client-cert-auth | Peer authentication enabled |\n| 2.6 | etcd peer auto-tls disabled | peer-auto-tls=false |\n| 2.7 | etcd unique CA | Separate CA for etcd (not shared with cluster) |\n\n## Key Rotation Procedure\n\n```bash\n# 1. Generate new encryption key\nNEW_KEY=$(head -c 32 \u002Fdev\u002Furandom | base64)\n\n# 2. Update EncryptionConfiguration with new key first\ncat > \u002Fetc\u002Fkubernetes\u002Fenc\u002Fencryption-config.yaml \u003C\u003CEOF\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: EncryptionConfiguration\nresources:\n  - resources:\n      - secrets\n    providers:\n      - aescbc:\n          keys:\n            - name: key2\n              secret: ${NEW_KEY}\n            - name: key1\n              secret: \u003Cold-key>\n      - identity: {}\nEOF\n\n# 3. Restart API server to pick up new config\n# 4. Re-encrypt all secrets with new key\nkubectl get secrets --all-namespaces -o json | \\\n  kubectl replace -f -\n\n# 5. Remove old key from EncryptionConfiguration\n# 6. Restart API server again\n```\n\n## References\n\n- [Kubernetes etcd Encryption Documentation](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fadminister-cluster\u002Fencrypt-data\u002F)\n- [CIS Kubernetes Benchmark - etcd Controls](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Securing etcd - K8s Security Guide](https:\u002F\u002Fk8s-security.geek-kb.com\u002Fdocs\u002Fbest_practices\u002Fcluster_setup_and_hardening\u002Fcontrol_plane_security\u002Fetcd_security_mitigation\u002F)\n- [Infosec: Encryption and etcd](https:\u002F\u002Fwww.infosecinstitute.com\u002Fresources\u002Fcryptography\u002Fencryption-and-etcd-the-key-to-securing-kubernetes\u002F)\n","# Performing Kubernetes etcd Security Assessment\n\n## Overview\n\netcd is the distributed key-value store that serves as Kubernetes' backing store for all cluster data, including Secrets, RBAC policies, ConfigMaps, and workload configurations. Without proper hardening, etcd exposes all cluster secrets in plaintext, making it the highest-value target for attackers who gain control plane access. A comprehensive security assessment covers encryption at rest, TLS for transport, access control, backup security, and network isolation.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing kubernetes etcd security assessment\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Access to Kubernetes control plane nodes\n- SSH access to etcd cluster nodes (or etcdctl configured)\n- CIS Kubernetes Benchmark reference document\n- Understanding of TLS certificate management and EncryptionConfiguration\n\n## Assessment Areas\n\n### 1. Encryption at Rest\n\nVerify that Kubernetes encrypts Secret data stored in etcd:\n\n```bash\n# Check if EncryptionConfiguration is configured on API server\nps aux | grep kube-apiserver | grep encryption-provider-config\n\n# View the encryption configuration\ncat \u002Fetc\u002Fkubernetes\u002Fenc\u002Fencryption-config.yaml\n```\n\nExpected secure configuration:\n\n```yaml\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: EncryptionConfiguration\nresources:\n  - resources:\n      - secrets\n      - configmaps\n    providers:\n      - aescbc:\n          keys:\n            - name: key1\n              secret: \u003Cbase64-encoded-32-byte-key>\n      - identity: {}  # Fallback for reading unencrypted data\n```\n\nVerify secrets are actually encrypted in etcd:\n\n```bash\n# Read a secret directly from etcd\nETCDCTL_API=3 etcdctl \\\n  --endpoints=https:\u002F\u002F127.0.0.1:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key \\\n  get \u002Fregistry\u002Fsecrets\u002Fdefault\u002Fmy-secret | hexdump -C | head -20\n\n# If encrypted, output starts with \"k8s:enc:aescbc:v1:key1\"\n# If NOT encrypted, you'll see plaintext key-value pairs\n```\n\n### 2. TLS Transport Security\n\n```bash\n# Verify etcd uses TLS for client connections\nETCDCTL_API=3 etcdctl endpoint health \\\n  --endpoints=https:\u002F\u002F127.0.0.1:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key\n\n# Check peer TLS configuration\nps aux | grep etcd | tr ' ' '\\n' | grep -E \"peer-cert|peer-key|peer-trusted-ca\"\n\n# Verify certificate expiration\nopenssl x509 -in \u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt -noout -enddate\nopenssl x509 -in \u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fpeer.crt -noout -enddate\n```\n\nExpected flags:\n\n| Flag | Required Value | Purpose |\n|------|---------------|---------|\n| `--cert-file` | Path to server cert | Client-to-server TLS |\n| `--key-file` | Path to server key | Client-to-server TLS |\n| `--trusted-ca-file` | Path to CA cert | Client certificate validation |\n| `--peer-cert-file` | Path to peer cert | Peer-to-peer TLS |\n| `--peer-key-file` | Path to peer key | Peer-to-peer TLS |\n| `--peer-trusted-ca-file` | Path to peer CA | Peer certificate validation |\n| `--client-cert-auth` | true | Require client certificates |\n| `--peer-client-cert-auth` | true | Require peer certificates |\n\n### 3. Access Control\n\n```bash\n# Verify etcd is not exposed on all interfaces\nps aux | grep etcd | tr ' ' '\\n' | grep listen-client-urls\n# Should be: https:\u002F\u002F127.0.0.1:2379 (not 0.0.0.0)\n\n# Check who can access etcd certificates\nls -la \u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002F\n# Should be readable only by root\u002Fetcd user\n\n# Verify API server is the only etcd client\nss -tlnp | grep 2379\n# Only kube-apiserver should have connections\n```\n\n### 4. Backup Security\n\n```bash\n# Create an encrypted etcd backup\nETCDCTL_API=3 etcdctl snapshot save \u002Fbackup\u002Fetcd-snapshot.db \\\n  --endpoints=https:\u002F\u002F127.0.0.1:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key\n\n# Encrypt the backup file\ngpg --symmetric --cipher-algo AES256 \u002Fbackup\u002Fetcd-snapshot.db\n\n# Verify backup integrity\nETCDCTL_API=3 etcdctl snapshot status \u002Fbackup\u002Fetcd-snapshot.db --write-out=table\n```\n\n### 5. Network Isolation\n\n```bash\n# Verify etcd ports are firewalled\niptables -L -n | grep -E \"2379|2380\"\n\n# Check if etcd is accessible from worker nodes (should NOT be)\n# Run from a worker node:\ncurl -k https:\u002F\u002F\u003Ccontrol-plane-ip>:2379\u002Fhealth\n# Should be rejected\u002Ftimeout\n```\n\n## CIS Benchmark Checks\n\n| CIS Control | Check | Expected Result |\n|-------------|-------|----------------|\n| 2.1 | etcd cert-file set | TLS certificate configured |\n| 2.2 | etcd client-cert-auth | Client certificate authentication enabled |\n| 2.3 | etcd auto-tls disabled | auto-tls=false |\n| 2.4 | etcd peer cert-file set | Peer TLS configured |\n| 2.5 | etcd peer client-cert-auth | Peer authentication enabled |\n| 2.6 | etcd peer auto-tls disabled | peer-auto-tls=false |\n| 2.7 | etcd unique CA | Separate CA for etcd (not shared with cluster) |\n\n## Key Rotation Procedure\n\n```bash\n# 1. Generate new encryption key\nNEW_KEY=$(head -c 32 \u002Fdev\u002Furandom | base64)\n\n# 2. Update EncryptionConfiguration with new key first\ncat > \u002Fetc\u002Fkubernetes\u002Fenc\u002Fencryption-config.yaml \u003C\u003CEOF\napiVersion: apiserver.config.k8s.io\u002Fv1\nkind: EncryptionConfiguration\nresources:\n  - resources:\n      - secrets\n    providers:\n      - aescbc:\n          keys:\n            - name: key2\n              secret: ${NEW_KEY}\n            - name: key1\n              secret: \u003Cold-key>\n      - identity: {}\nEOF\n\n# 3. Restart API server to pick up new config\n# 4. Re-encrypt all secrets with new key\nkubectl get secrets --all-namespaces -o json | \\\n  kubectl replace -f -\n\n# 5. Remove old key from EncryptionConfiguration\n# 6. Restart API server again\n```\n\n## References\n\n- [Kubernetes etcd Encryption Documentation](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fadminister-cluster\u002Fencrypt-data\u002F)\n- [CIS Kubernetes Benchmark - etcd Controls](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Securing etcd - K8s Security Guide](https:\u002F\u002Fk8s-security.geek-kb.com\u002Fdocs\u002Fbest_practices\u002Fcluster_setup_and_hardening\u002Fcontrol_plane_security\u002Fetcd_security_mitigation\u002F)\n- [Infosec: Encryption and etcd](https:\u002F\u002Fwww.infosecinstitute.com\u002Fresources\u002Fcryptography\u002Fencryption-and-etcd-the-key-to-securing-kubernetes\u002F)\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":7,"mitre_attack":43},[26,27,28,29,30,31,32,33],"kubernetes","etcd","encryption","tls","security-assessment","backup","secrets","control-plane","mahipal","cybersecurity","1.0",[38,39,40,41],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[44,45,46,47,48],"T1610","T1611","T1609","T1525","T1573","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill performing-kubernetes-etcd-security-assessment",{"tool":63,"command":64},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill performing-kubernetes-etcd-security-assessment",{"tool":66,"command":67},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill performing-kubernetes-etcd-security-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002FSKILL.md",true,[71,77,81,87,91,95,101],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Ftemplate.md","ASSET","资产文件",566,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Fassets\u002Ftemplate.md",{"path":78,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi-reference.md","REFERENCE","参考文档",1855,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Freferences\u002Fapi-reference.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fstandards.md",930,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Freferences\u002Fstandards.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fworkflows.md",737,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Freferences\u002Fworkflows.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fagent.py","SCRIPT","脚本",8289,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Fscripts\u002Fagent.py",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fprocess.py",7589,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fcybersecurity-skills\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Fscripts\u002Fprocess.py",[106,114,122,130,138,145],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\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":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\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":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":20},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]