[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DAM5JEW4D5YYZXJ4RE75JC":3,"skill-same:01M7DAM5JEW4D5YYZXJ4RE75JC":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":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M7DAM5JEW4D5YYZXJ4RE75JC","implementing-rbac-hardening-for-kubernetes",null,"Harden Kubernetes RBAC by implementing least-privilege Roles and ClusterRoles, auditing RoleBindings, eliminating cluster-admin sprawl, separating service accounts, and integrating external identity providers (OIDC). Use when reviewing or tightening Kubernetes access control, removing excessive ClusterRoleBindings, or hardening service-account permissions against privilege escalation and lateral movement.","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\u002Fimplementing-rbac-hardening-for-kubernetes\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-rbac-hardening-for-kubernetes\ndescription: Harden Kubernetes RBAC by implementing least-privilege Roles and ClusterRoles,\n  auditing RoleBindings, eliminating cluster-admin sprawl, separating service accounts,\n  and integrating external identity providers (OIDC). Use when reviewing or tightening\n  Kubernetes access control, removing excessive ClusterRoleBindings, or hardening\n  service-account permissions against privilege escalation and lateral movement.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- rbac\n- access-control\n- least-privilege\n- security-hardening\n- iam\n- oidc\n- service-accounts\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 RBAC Hardening for Kubernetes\n\n## Overview\n\nKubernetes RBAC regulates access to cluster resources based on roles assigned to users, groups, and service accounts. Default configurations often grant excessive permissions, and without active hardening, RBAC becomes a primary attack vector for privilege escalation, lateral movement, and data exfiltration. Hardening requires implementing least-privilege principles, eliminating unnecessary ClusterRole bindings, separating service accounts, integrating external identity providers, and continuous auditing.\n\n\n## When to Use\n\n- When deploying or configuring implementing rbac hardening for kubernetes capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Kubernetes cluster v1.24+ with RBAC enabled (default since v1.6)\n- kubectl access with cluster-admin for initial audit\n- External identity provider (OIDC) for user authentication\n- Audit logging enabled on the API server\n\n## Core Hardening Principles\n\n### 1. Eliminate cluster-admin Sprawl\n\nAudit and remove unnecessary cluster-admin bindings:\n\n```bash\n# List all cluster-admin bindings\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\") |\n  \"\\(.metadata.name) -> \\(.subjects[]? | \"\\(.kind)\u002F\\(.name) (\\(.namespace \u002F\u002F \"cluster\"))\")\"\n'\n```\n\n### 2. Namespace-Scoped Roles Over ClusterRoles\n\nUse Role and RoleBinding instead of ClusterRole and ClusterRoleBinding:\n\n```yaml\n# Good: Namespace-scoped role\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  namespace: application\n  name: app-developer\nrules:\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\"]\n    verbs: [\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\"]\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"pods\u002Flog\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\"]\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  namespace: application\n  name: app-developer-binding\nsubjects:\n  - kind: Group\n    name: dev-team\n    apiGroup: rbac.authorization.k8s.io\nroleRef:\n  kind: Role\n  name: app-developer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n### 3. Dedicated Service Accounts Per Workload\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: payment-processor\n  namespace: payments\nautomountServiceAccountToken: false  # Disable auto-mount\n---\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: payment-processor\n  namespace: payments\nspec:\n  template:\n    spec:\n      serviceAccountName: payment-processor\n      automountServiceAccountToken: true  # Only mount when explicitly needed\n      containers:\n        - name: processor\n          image: payments\u002Fprocessor:v2.1@sha256:abc...\n```\n\n### 4. Restrict Dangerous Permissions\n\nBlock permissions that enable privilege escalation:\n\n```yaml\n# Dangerous verbs\u002Fresources to restrict:\n# - secrets: get, list, watch (exposes all secrets in namespace)\n# - pods\u002Fexec: create (enables command execution in pods)\n# - pods: create with privileged securityContext\n# - serviceaccounts\u002Ftoken: create (generates new tokens)\n# - clusterroles\u002Fclusterrolebindings: create, update (self-escalation)\n# - nodes\u002Fproxy: create (bypasses API server authorization)\n\n# Safe read-only role example\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: ClusterRole\nmetadata:\n  name: security-viewer\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"services\", \"namespaces\", \"nodes\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"networking.k8s.io\"]\n    resources: [\"networkpolicies\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n```\n\n### 5. OIDC Integration for User Authentication\n\n```yaml\n# API server flags for OIDC integration\napiVersion: v1\nkind: Pod\nmetadata:\n  name: kube-apiserver\nspec:\n  containers:\n    - name: kube-apiserver\n      command:\n        - kube-apiserver\n        - --oidc-issuer-url=https:\u002F\u002Fidp.company.com\n        - --oidc-client-id=kubernetes\n        - --oidc-username-claim=email\n        - --oidc-groups-claim=groups\n        - --oidc-ca-file=\u002Fetc\u002Fkubernetes\u002Fpki\u002Foidc-ca.crt\n```\n\n## RBAC Audit Process\n\n### Step 1: Enumerate All Bindings\n\n```bash\n# All ClusterRoleBindings with subjects\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n\n# All RoleBindings across namespaces\nkubectl get rolebindings --all-namespaces -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.namespace) | \\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n```\n\n### Step 2: Identify Overprivileged Service Accounts\n\n```bash\n# Find service accounts with cluster-admin or admin roles\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\" or .roleRef.name == \"admin\") |\n  select(.subjects[]?.kind == \"ServiceAccount\") |\n  \"\\(.subjects[] | select(.kind == \"ServiceAccount\") | \"\\(.namespace)\u002F\\(.name)\")\"\n'\n```\n\n### Step 3: Check Default Service Account Usage\n\n```bash\n# Find pods using the default service account\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.serviceAccountName == \"default\" or .spec.serviceAccountName == null) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name)\"\n'\n```\n\n### Step 4: Verify Token Auto-Mount\n\n```bash\n# Find pods with auto-mounted service account tokens\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.automountServiceAccountToken != false) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name) sa=\\(.spec.serviceAccountName \u002F\u002F \"default\")\"\n'\n```\n\n## Tooling\n\n### rbac-lookup\n\n```bash\n# Install rbac-lookup\nkubectl krew install rbac-lookup\n\n# View RBAC for a specific user\nkubectl rbac-lookup developer@company.com\n\n# View all RBAC bindings wide format\nkubectl rbac-lookup --kind user -o wide\n```\n\n### rakkess (Review Access)\n\n```bash\n# Install rakkess\nkubectl krew install access-matrix\n\n# Show access matrix for current user\nkubectl access-matrix\n\n# Show access for a specific service account\nkubectl access-matrix --sa payments:payment-processor\n```\n\n## References\n\n- [Kubernetes RBAC Documentation](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Freference\u002Faccess-authn-authz\u002Frbac\u002F)\n- [CIS Kubernetes Benchmark - RBAC Controls](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Security Hardening Guide 2025](https:\u002F\u002Fsealos.io\u002Fblog\u002Fa-practical-guide-to-kubernetes-security-hardening-your-cluster-in-2025\u002F)\n- [OWASP Kubernetes Security Cheat Sheet](https:\u002F\u002Fcheatsheetseries.owasp.org\u002Fcheatsheets\u002FKubernetes_Security_Cheat_Sheet.html)\n","# Implementing RBAC Hardening for Kubernetes\n\n## Overview\n\nKubernetes RBAC regulates access to cluster resources based on roles assigned to users, groups, and service accounts. Default configurations often grant excessive permissions, and without active hardening, RBAC becomes a primary attack vector for privilege escalation, lateral movement, and data exfiltration. Hardening requires implementing least-privilege principles, eliminating unnecessary ClusterRole bindings, separating service accounts, integrating external identity providers, and continuous auditing.\n\n\n## When to Use\n\n- When deploying or configuring implementing rbac hardening for kubernetes capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Kubernetes cluster v1.24+ with RBAC enabled (default since v1.6)\n- kubectl access with cluster-admin for initial audit\n- External identity provider (OIDC) for user authentication\n- Audit logging enabled on the API server\n\n## Core Hardening Principles\n\n### 1. Eliminate cluster-admin Sprawl\n\nAudit and remove unnecessary cluster-admin bindings:\n\n```bash\n# List all cluster-admin bindings\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\") |\n  \"\\(.metadata.name) -> \\(.subjects[]? | \"\\(.kind)\u002F\\(.name) (\\(.namespace \u002F\u002F \"cluster\"))\")\"\n'\n```\n\n### 2. Namespace-Scoped Roles Over ClusterRoles\n\nUse Role and RoleBinding instead of ClusterRole and ClusterRoleBinding:\n\n```yaml\n# Good: Namespace-scoped role\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  namespace: application\n  name: app-developer\nrules:\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\"]\n    verbs: [\"get\", \"list\", \"watch\", \"create\", \"update\", \"patch\"]\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"pods\u002Flog\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\"]\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  namespace: application\n  name: app-developer-binding\nsubjects:\n  - kind: Group\n    name: dev-team\n    apiGroup: rbac.authorization.k8s.io\nroleRef:\n  kind: Role\n  name: app-developer\n  apiGroup: rbac.authorization.k8s.io\n```\n\n### 3. Dedicated Service Accounts Per Workload\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: payment-processor\n  namespace: payments\nautomountServiceAccountToken: false  # Disable auto-mount\n---\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: payment-processor\n  namespace: payments\nspec:\n  template:\n    spec:\n      serviceAccountName: payment-processor\n      automountServiceAccountToken: true  # Only mount when explicitly needed\n      containers:\n        - name: processor\n          image: payments\u002Fprocessor:v2.1@sha256:abc...\n```\n\n### 4. Restrict Dangerous Permissions\n\nBlock permissions that enable privilege escalation:\n\n```yaml\n# Dangerous verbs\u002Fresources to restrict:\n# - secrets: get, list, watch (exposes all secrets in namespace)\n# - pods\u002Fexec: create (enables command execution in pods)\n# - pods: create with privileged securityContext\n# - serviceaccounts\u002Ftoken: create (generates new tokens)\n# - clusterroles\u002Fclusterrolebindings: create, update (self-escalation)\n# - nodes\u002Fproxy: create (bypasses API server authorization)\n\n# Safe read-only role example\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: ClusterRole\nmetadata:\n  name: security-viewer\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"pods\", \"services\", \"namespaces\", \"nodes\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"apps\"]\n    resources: [\"deployments\", \"daemonsets\", \"statefulsets\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n  - apiGroups: [\"networking.k8s.io\"]\n    resources: [\"networkpolicies\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n```\n\n### 5. OIDC Integration for User Authentication\n\n```yaml\n# API server flags for OIDC integration\napiVersion: v1\nkind: Pod\nmetadata:\n  name: kube-apiserver\nspec:\n  containers:\n    - name: kube-apiserver\n      command:\n        - kube-apiserver\n        - --oidc-issuer-url=https:\u002F\u002Fidp.company.com\n        - --oidc-client-id=kubernetes\n        - --oidc-username-claim=email\n        - --oidc-groups-claim=groups\n        - --oidc-ca-file=\u002Fetc\u002Fkubernetes\u002Fpki\u002Foidc-ca.crt\n```\n\n## RBAC Audit Process\n\n### Step 1: Enumerate All Bindings\n\n```bash\n# All ClusterRoleBindings with subjects\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n\n# All RoleBindings across namespaces\nkubectl get rolebindings --all-namespaces -o json | jq -r '\n  .items[] | select(.subjects != null) |\n  .subjects[] as $s |\n  \"\\(.metadata.namespace) | \\(.metadata.name) | \\(.roleRef.name) | \\($s.kind)\u002F\\($s.name)\"\n' | sort | column -t -s '|'\n```\n\n### Step 2: Identify Overprivileged Service Accounts\n\n```bash\n# Find service accounts with cluster-admin or admin roles\nkubectl get clusterrolebindings -o json | jq -r '\n  .items[] |\n  select(.roleRef.name == \"cluster-admin\" or .roleRef.name == \"admin\") |\n  select(.subjects[]?.kind == \"ServiceAccount\") |\n  \"\\(.subjects[] | select(.kind == \"ServiceAccount\") | \"\\(.namespace)\u002F\\(.name)\")\"\n'\n```\n\n### Step 3: Check Default Service Account Usage\n\n```bash\n# Find pods using the default service account\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.serviceAccountName == \"default\" or .spec.serviceAccountName == null) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name)\"\n'\n```\n\n### Step 4: Verify Token Auto-Mount\n\n```bash\n# Find pods with auto-mounted service account tokens\nkubectl get pods --all-namespaces -o json | jq -r '\n  .items[] |\n  select(.spec.automountServiceAccountToken != false) |\n  \"\\(.metadata.namespace)\u002F\\(.metadata.name) sa=\\(.spec.serviceAccountName \u002F\u002F \"default\")\"\n'\n```\n\n## Tooling\n\n### rbac-lookup\n\n```bash\n# Install rbac-lookup\nkubectl krew install rbac-lookup\n\n# View RBAC for a specific user\nkubectl rbac-lookup developer@company.com\n\n# View all RBAC bindings wide format\nkubectl rbac-lookup --kind user -o wide\n```\n\n### rakkess (Review Access)\n\n```bash\n# Install rakkess\nkubectl krew install access-matrix\n\n# Show access matrix for current user\nkubectl access-matrix\n\n# Show access for a specific service account\nkubectl access-matrix --sa payments:payment-processor\n```\n\n## References\n\n- [Kubernetes RBAC Documentation](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Freference\u002Faccess-authn-authz\u002Frbac\u002F)\n- [CIS Kubernetes Benchmark - RBAC Controls](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes)\n- [Kubernetes Security Hardening Guide 2025](https:\u002F\u002Fsealos.io\u002Fblog\u002Fa-practical-guide-to-kubernetes-security-hardening-your-cluster-in-2025\u002F)\n- [OWASP Kubernetes Security Cheat Sheet](https:\u002F\u002Fcheatsheetseries.owasp.org\u002Fcheatsheets\u002FKubernetes_Security_Cheat_Sheet.html)\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","rbac","access-control","least-privilege","security-hardening","iam","oidc","service-accounts","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],"T1610","T1611","T1609","T1525","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill implementing-rbac-hardening-for-kubernetes",{"tool":63,"command":64},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill implementing-rbac-hardening-for-kubernetes",{"tool":66,"command":67},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill implementing-rbac-hardening-for-kubernetes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\u002FSKILL.md",true,[71,77,81,87,91,95,101],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Ftemplate.md","ASSET","资产文件",741,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\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","参考文档",6262,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\u002Freferences\u002Fapi-reference.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fstandards.md",766,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\u002Freferences\u002Fstandards.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fworkflows.md",708,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\u002Freferences\u002Fworkflows.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fagent.py","SCRIPT","脚本",9923,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\u002Fscripts\u002Fagent.py",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fprocess.py",7020,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fimplementing-rbac-hardening-for-kubernetes\u002Fscripts\u002Fprocess.py",[106,114,122,131,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":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"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":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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",[],[]]