[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DCD015KM7K9ZKB8KH157YM":3,"skill-same:01M7DCD015KM7K9ZKB8KH157YM":106},{"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":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M7DCD015KM7K9ZKB8KH157YM","performing-kubernetes-etcd-security-assessment",null,"Assess the security posture of Kubernetes etcd clusters by evaluating encryption at rest, TLS transport configuration, access controls, backup encryption, and network isolation for the cluster's backing key-value store. Use when auditing or hardening a Kubernetes control plane, since etcd holds Secrets, RBAC policies, and ConfigMaps in plaintext by default and is a high-value target if left unassessed.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-kubernetes-etcd-security-assessment\ndescription: Assess the security posture of Kubernetes etcd clusters by evaluating\n  encryption at rest, TLS transport configuration, access controls, backup encryption,\n  and network isolation for the cluster's backing key-value store. Use when auditing\n  or hardening a Kubernetes control plane, since etcd holds Secrets, RBAC policies,\n  and ConfigMaps in plaintext by default and is a high-value target if left unassessed.\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","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill performing-kubernetes-etcd-security-assessment",{"tool":64,"command":65},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill performing-kubernetes-etcd-security-assessment",{"tool":67,"command":68},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill performing-kubernetes-etcd-security-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002FSKILL.md",true,[72,78,82,88,92,96,102],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ftemplate.md","ASSET","资产文件",566,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Fassets\u002Ftemplate.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fapi-reference.md","REFERENCE","参考文档",1855,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Freferences\u002Fapi-reference.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",930,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",737,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",8289,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Fscripts\u002Fagent.py",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fprocess.py",7589,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fperforming-kubernetes-etcd-security-assessment\u002Fscripts\u002Fprocess.py",[107,115,123,132,139,146],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","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\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","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\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\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":127,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\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":127,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]