[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753KV3XQ4RC5TVHFS669NMP":3,"skill-same:01M753KV3XQ4RC5TVHFS669NMP":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M753KV3XQ4RC5TVHFS669NMP","kubernetes-specialist",null,"Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies, NetworkPolicies, storage configuration, performance optimization, GitOps pipelines, and multi-cluster management.","haryelramalho\u002Fskills","haryelramalho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38708454?v=4","01M753ESC6XNS6GXGV5X9YMKGA","Haryel Ramalho","01M753ESCSPRNDTEJRVRYY1VJ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: kubernetes-specialist\ndescription: Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies, NetworkPolicies, storage configuration, performance optimization, GitOps pipelines, and multi-cluster management.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: infrastructure\n  triggers: Kubernetes, K8s, kubectl, Helm, container orchestration, pod deployment, RBAC, NetworkPolicy, Ingress, StatefulSet, Operator, CRD, CustomResourceDefinition, ArgoCD, Flux, GitOps, Istio, Linkerd, service mesh, multi-cluster, cost optimization, VPA, spot instances\n  role: specialist\n  scope: infrastructure\n  output-format: manifests\n  related-skills: devops-engineer, cloud-architect, sre-engineer\n---\n\n# Kubernetes Specialist\n\n## When to Use This Skill\n\n- Deploying workloads (Deployments, StatefulSets, DaemonSets, Jobs)\n- Configuring networking (Services, Ingress, NetworkPolicies)\n- Managing configuration (ConfigMaps, Secrets, environment variables)\n- Setting up persistent storage (PV, PVC, StorageClasses)\n- Creating Helm charts for application packaging\n- Troubleshooting cluster and workload issues\n- Implementing security best practices\n\n## Core Workflow\n\n1. **Analyze requirements** — Understand workload characteristics, scaling needs, security requirements\n2. **Design architecture** — Choose workload types, networking patterns, storage solutions\n3. **Implement manifests** — Create declarative YAML with proper resource limits, health checks\n4. **Secure** — Apply RBAC, NetworkPolicies, Pod Security Standards, least privilege\n5. **Validate** — Run `kubectl rollout status`, `kubectl get pods -w`, and `kubectl describe pod \u003Cname>` to confirm health; roll back with `kubectl rollout undo` if needed\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic             | Reference                         | Load When                                                        |\n| ----------------- | --------------------------------- | ---------------------------------------------------------------- |\n| Workloads         | `references\u002Fworkloads.md`         | Deployments, StatefulSets, DaemonSets, Jobs, CronJobs            |\n| Networking        | `references\u002Fnetworking.md`        | Services, Ingress, NetworkPolicies, DNS                          |\n| Configuration     | `references\u002Fconfiguration.md`     | ConfigMaps, Secrets, environment variables                       |\n| Storage           | `references\u002Fstorage.md`           | PV, PVC, StorageClasses, CSI drivers                             |\n| Helm Charts       | `references\u002Fhelm-charts.md`       | Chart structure, values, templates, hooks, testing, repositories |\n| Troubleshooting   | `references\u002Ftroubleshooting.md`   | kubectl debug, logs, events, common issues                       |\n| Custom Operators  | `references\u002Fcustom-operators.md`  | CRD, Operator SDK, controller-runtime, reconciliation            |\n| Service Mesh      | `references\u002Fservice-mesh.md`      | Istio, Linkerd, traffic management, mTLS, canary                 |\n| GitOps            | `references\u002Fgitops.md`            | ArgoCD, Flux, progressive delivery, sealed secrets               |\n| Cost Optimization | `references\u002Fcost-optimization.md` | VPA, HPA tuning, spot instances, quotas, right-sizing            |\n| Multi-Cluster     | `references\u002Fmulti-cluster.md`     | Cluster API, federation, cross-cluster networking, DR            |\n\n## Constraints\n\n### MUST DO\n\n- Use declarative YAML manifests (avoid imperative kubectl commands)\n- Set resource requests and limits on all containers\n- Include liveness and readiness probes\n- Use secrets for sensitive data (never hardcode credentials)\n- Apply least privilege RBAC permissions\n- Implement NetworkPolicies for network segmentation\n- Use namespaces for logical isolation\n- Label resources consistently for organization\n- Document configuration decisions in annotations\n\n### MUST NOT DO\n\n- Deploy to production without resource limits\n- Store secrets in ConfigMaps or as plain environment variables\n- Use default ServiceAccount for application pods\n- Allow unrestricted network access (default allow-all)\n- Run containers as root without justification\n- Skip health checks (liveness\u002Freadiness probes)\n- Use latest tag for production images\n- Expose unnecessary ports or services\n\n## Common YAML Patterns\n\n### Deployment with resource limits, probes, and security context\n\n```yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: my-app\n  namespace: my-namespace\n  labels:\n    app: my-app\n    version: \"1.2.3\"\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: my-app\n  template:\n    metadata:\n      labels:\n        app: my-app\n        version: \"1.2.3\"\n    spec:\n      serviceAccountName: my-app-sa # never use default SA\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 1000\n        fsGroup: 2000\n      containers:\n        - name: my-app\n          image: my-registry\u002Fmy-app:1.2.3 # never use latest\n          ports:\n            - containerPort: 8080\n          resources:\n            requests:\n              cpu: \"100m\"\n              memory: \"128Mi\"\n            limits:\n              cpu: \"500m\"\n              memory: \"512Mi\"\n          livenessProbe:\n            httpGet:\n              path: \u002Fhealthz\n              port: 8080\n            initialDelaySeconds: 15\n            periodSeconds: 20\n          readinessProbe:\n            httpGet:\n              path: \u002Fready\n              port: 8080\n            initialDelaySeconds: 5\n            periodSeconds: 10\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop: [\"ALL\"]\n          envFrom:\n            - secretRef:\n                name: my-app-secret # pull credentials from Secret, not ConfigMap\n```\n\n### Minimal RBAC (least privilege)\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: my-app-sa\n  namespace: my-namespace\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  name: my-app-role\n  namespace: my-namespace\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\"] # grant only what is needed\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  name: my-app-rolebinding\n  namespace: my-namespace\nsubjects:\n  - kind: ServiceAccount\n    name: my-app-sa\n    namespace: my-namespace\nroleRef:\n  kind: Role\n  name: my-app-role\n  apiGroup: rbac.authorization.k8s.io\n```\n\n### NetworkPolicy (default-deny + explicit allow)\n\n```yaml\n# Deny all ingress and egress by default\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: default-deny-all\n  namespace: my-namespace\nspec:\n  podSelector: {}\n  policyTypes: [\"Ingress\", \"Egress\"]\n---\n# Allow only specific traffic\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-my-app\n  namespace: my-namespace\nspec:\n  podSelector:\n    matchLabels:\n      app: my-app\n  policyTypes: [\"Ingress\"]\n  ingress:\n    - from:\n        - podSelector:\n            matchLabels:\n              app: frontend\n      ports:\n        - protocol: TCP\n          port: 8080\n```\n\n## Validation Commands\n\nAfter deploying, verify health and security posture:\n\n```bash\n# Watch rollout complete\nkubectl rollout status deployment\u002Fmy-app -n my-namespace\n\n# Stream pod events to catch crash loops or image pull errors\nkubectl get pods -n my-namespace -w\n\n# Inspect a specific pod for failures\nkubectl describe pod \u003Cpod-name> -n my-namespace\n\n# Check container logs\nkubectl logs \u003Cpod-name> -n my-namespace --previous   # use --previous for crashed containers\n\n# Verify resource usage vs. limits\nkubectl top pods -n my-namespace\n\n# Audit RBAC permissions for a service account\nkubectl auth can-i --list --as=system:serviceaccount:my-namespace:my-app-sa\n\n# Roll back a failed deployment\nkubectl rollout undo deployment\u002Fmy-app -n my-namespace\n```\n\n## Output Templates\n\nWhen implementing Kubernetes resources, provide:\n\n1. Complete YAML manifests with proper structure\n2. RBAC configuration if needed (ServiceAccount, Role, RoleBinding)\n3. NetworkPolicy for network isolation\n4. Brief explanation of design decisions and security considerations\n","# Kubernetes Specialist\n\n## When to Use This Skill\n\n- Deploying workloads (Deployments, StatefulSets, DaemonSets, Jobs)\n- Configuring networking (Services, Ingress, NetworkPolicies)\n- Managing configuration (ConfigMaps, Secrets, environment variables)\n- Setting up persistent storage (PV, PVC, StorageClasses)\n- Creating Helm charts for application packaging\n- Troubleshooting cluster and workload issues\n- Implementing security best practices\n\n## Core Workflow\n\n1. **Analyze requirements** — Understand workload characteristics, scaling needs, security requirements\n2. **Design architecture** — Choose workload types, networking patterns, storage solutions\n3. **Implement manifests** — Create declarative YAML with proper resource limits, health checks\n4. **Secure** — Apply RBAC, NetworkPolicies, Pod Security Standards, least privilege\n5. **Validate** — Run `kubectl rollout status`, `kubectl get pods -w`, and `kubectl describe pod \u003Cname>` to confirm health; roll back with `kubectl rollout undo` if needed\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic             | Reference                         | Load When                                                        |\n| ----------------- | --------------------------------- | ---------------------------------------------------------------- |\n| Workloads         | `references\u002Fworkloads.md`         | Deployments, StatefulSets, DaemonSets, Jobs, CronJobs            |\n| Networking        | `references\u002Fnetworking.md`        | Services, Ingress, NetworkPolicies, DNS                          |\n| Configuration     | `references\u002Fconfiguration.md`     | ConfigMaps, Secrets, environment variables                       |\n| Storage           | `references\u002Fstorage.md`           | PV, PVC, StorageClasses, CSI drivers                             |\n| Helm Charts       | `references\u002Fhelm-charts.md`       | Chart structure, values, templates, hooks, testing, repositories |\n| Troubleshooting   | `references\u002Ftroubleshooting.md`   | kubectl debug, logs, events, common issues                       |\n| Custom Operators  | `references\u002Fcustom-operators.md`  | CRD, Operator SDK, controller-runtime, reconciliation            |\n| Service Mesh      | `references\u002Fservice-mesh.md`      | Istio, Linkerd, traffic management, mTLS, canary                 |\n| GitOps            | `references\u002Fgitops.md`            | ArgoCD, Flux, progressive delivery, sealed secrets               |\n| Cost Optimization | `references\u002Fcost-optimization.md` | VPA, HPA tuning, spot instances, quotas, right-sizing            |\n| Multi-Cluster     | `references\u002Fmulti-cluster.md`     | Cluster API, federation, cross-cluster networking, DR            |\n\n## Constraints\n\n### MUST DO\n\n- Use declarative YAML manifests (avoid imperative kubectl commands)\n- Set resource requests and limits on all containers\n- Include liveness and readiness probes\n- Use secrets for sensitive data (never hardcode credentials)\n- Apply least privilege RBAC permissions\n- Implement NetworkPolicies for network segmentation\n- Use namespaces for logical isolation\n- Label resources consistently for organization\n- Document configuration decisions in annotations\n\n### MUST NOT DO\n\n- Deploy to production without resource limits\n- Store secrets in ConfigMaps or as plain environment variables\n- Use default ServiceAccount for application pods\n- Allow unrestricted network access (default allow-all)\n- Run containers as root without justification\n- Skip health checks (liveness\u002Freadiness probes)\n- Use latest tag for production images\n- Expose unnecessary ports or services\n\n## Common YAML Patterns\n\n### Deployment with resource limits, probes, and security context\n\n```yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: my-app\n  namespace: my-namespace\n  labels:\n    app: my-app\n    version: \"1.2.3\"\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: my-app\n  template:\n    metadata:\n      labels:\n        app: my-app\n        version: \"1.2.3\"\n    spec:\n      serviceAccountName: my-app-sa # never use default SA\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 1000\n        fsGroup: 2000\n      containers:\n        - name: my-app\n          image: my-registry\u002Fmy-app:1.2.3 # never use latest\n          ports:\n            - containerPort: 8080\n          resources:\n            requests:\n              cpu: \"100m\"\n              memory: \"128Mi\"\n            limits:\n              cpu: \"500m\"\n              memory: \"512Mi\"\n          livenessProbe:\n            httpGet:\n              path: \u002Fhealthz\n              port: 8080\n            initialDelaySeconds: 15\n            periodSeconds: 20\n          readinessProbe:\n            httpGet:\n              path: \u002Fready\n              port: 8080\n            initialDelaySeconds: 5\n            periodSeconds: 10\n          securityContext:\n            allowPrivilegeEscalation: false\n            readOnlyRootFilesystem: true\n            capabilities:\n              drop: [\"ALL\"]\n          envFrom:\n            - secretRef:\n                name: my-app-secret # pull credentials from Secret, not ConfigMap\n```\n\n### Minimal RBAC (least privilege)\n\n```yaml\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: my-app-sa\n  namespace: my-namespace\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: Role\nmetadata:\n  name: my-app-role\n  namespace: my-namespace\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\"] # grant only what is needed\n---\napiVersion: rbac.authorization.k8s.io\u002Fv1\nkind: RoleBinding\nmetadata:\n  name: my-app-rolebinding\n  namespace: my-namespace\nsubjects:\n  - kind: ServiceAccount\n    name: my-app-sa\n    namespace: my-namespace\nroleRef:\n  kind: Role\n  name: my-app-role\n  apiGroup: rbac.authorization.k8s.io\n```\n\n### NetworkPolicy (default-deny + explicit allow)\n\n```yaml\n# Deny all ingress and egress by default\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: default-deny-all\n  namespace: my-namespace\nspec:\n  podSelector: {}\n  policyTypes: [\"Ingress\", \"Egress\"]\n---\n# Allow only specific traffic\napiVersion: networking.k8s.io\u002Fv1\nkind: NetworkPolicy\nmetadata:\n  name: allow-my-app\n  namespace: my-namespace\nspec:\n  podSelector:\n    matchLabels:\n      app: my-app\n  policyTypes: [\"Ingress\"]\n  ingress:\n    - from:\n        - podSelector:\n            matchLabels:\n              app: frontend\n      ports:\n        - protocol: TCP\n          port: 8080\n```\n\n## Validation Commands\n\nAfter deploying, verify health and security posture:\n\n```bash\n# Watch rollout complete\nkubectl rollout status deployment\u002Fmy-app -n my-namespace\n\n# Stream pod events to catch crash loops or image pull errors\nkubectl get pods -n my-namespace -w\n\n# Inspect a specific pod for failures\nkubectl describe pod \u003Cpod-name> -n my-namespace\n\n# Check container logs\nkubectl logs \u003Cpod-name> -n my-namespace --previous   # use --previous for crashed containers\n\n# Verify resource usage vs. limits\nkubectl top pods -n my-namespace\n\n# Audit RBAC permissions for a service account\nkubectl auth can-i --list --as=system:serviceaccount:my-namespace:my-app-sa\n\n# Roll back a failed deployment\nkubectl rollout undo deployment\u002Fmy-app -n my-namespace\n```\n\n## Output Templates\n\nWhen implementing Kubernetes resources, provide:\n\n1. Complete YAML manifests with proper structure\n2. RBAC configuration if needed (ServiceAccount, Role, RoleBinding)\n3. NetworkPolicy for network isolation\n4. Brief explanation of design decisions and security considerations\n",{"name":5,"license":15,"metadata":24,"description":7},{"role":25,"scope":26,"author":27,"domain":26,"version":28,"triggers":29,"output-format":30,"related-skills":31},"specialist","infrastructure","https:\u002F\u002Fgithub.com\u002FJeffallan","1.1.0","Kubernetes, K8s, kubectl, Helm, container orchestration, pod deployment, RBAC, NetworkPolicy, Ingress, StatefulSet, Operator, CRD, CustomResourceDefinition, ArgoCD, Flux, GitOps, Istio, Linkerd, service mesh, multi-cluster, cost optimization, VPA, spot instances","manifests","devops-engineer, cloud-architect, sre-engineer","main","a5b533be2d244bbf3e5606e851742f0e0ba99423","skills\u002Fcommunity\u002Fkubernetes-specialist","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills","https:\u002F\u002Fgithub.com\u002Fharyelramalho","linkedin.com\u002Fin\u002Fharyelramalho\u002F","Software Engineer @ SKORR •  Former Vice President of the Junior Computer Association - TecnoJr","2026-07-16 01:34:58",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add haryelramalho\u002Fskills --skill kubernetes-specialist",{"tool":46,"command":47},"bunx","bunx skills add haryelramalho\u002Fskills --skill kubernetes-specialist",{"tool":49,"command":50},"pnpm","pnpm dlx skills add haryelramalho\u002Fskills --skill kubernetes-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002FSKILL.md",true,[54,60,64,68,72,76,80,84,88,92,96],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fconfiguration.md","REFERENCE","参考文档",9523,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fconfiguration.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcost-optimization.md",9866,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fcost-optimization.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcustom-operators.md",15917,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fcustom-operators.md",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fgitops.md",11327,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fgitops.md",{"path":73,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fhelm-charts.md",20141,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fhelm-charts.md",{"path":77,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fmulti-cluster.md",11254,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fmulti-cluster.md",{"path":81,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fnetworking.md",8534,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fnetworking.md",{"path":85,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fservice-mesh.md",9728,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fservice-mesh.md",{"path":89,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstorage.md",10186,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fstorage.md",{"path":93,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Ftroubleshooting.md",11186,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Ftroubleshooting.md",{"path":97,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fworkloads.md",9301,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fkubernetes-specialist\u002Freferences\u002Fworkloads.md",[101,108,115,122,129,136],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M753YDMKSDB7320THEQ2CVW5","to-prompt-opus","Use when preparing or rewriting prompts for Claude Opus 4.8, Anthropic API agents, XML-structured prompts, long-context document work, coding agents, research synthesis, frontend\u002Fdesign tasks, or model-specific prompt optimization. Do not use for GPT\u002FOpenAI prompts or raw context packaging without Opus-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-opus\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M753YAP95W4K2MCEAEEAV6YA","to-prompt-gpt","Use when preparing or rewriting prompts for GPT-5.5, OpenAI API agents, Responses workflows, coding agents, research synthesis, support assistants, or model-specific prompt optimization. Do not use for Claude\u002FOpus prompts or raw context packaging without GPT-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-gpt\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":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M753Y700AZ0GVJDNW9Q1Q54F","plan-refactor-qa","Plans and runs qa-report before executing Compozy refactor tasks. Use when the user provides a refactor or issue slug and wants Codex to inspect the matching .compozy\u002Ftasks directory, related PRD\u002FTechSpec\u002FADR\u002Ftask artifacts, affected code, and existing tests, then invoke $qa-report with a repository-grounded prompt. Do not use to run tests, execute qa-execution, implement code, or perform post-refactor verification.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fplan-refactor-qa\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":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M753XZENG0Z8S2ET75EM8CGB","multi-tool-branch-review","Orchestrates a multi-tool branch review of the current git branch against a base branch. By default it runs two independent thermo-nuclear maintainability audits, one on Codex GPT-5.5 xhigh and one on Claude Opus xhigh, then consolidates the findings into a single remediation plan via writing-plans. If the user explicitly asks for native reviews, it can add the Claude native review pass, the Codex native review pass, or both. Use when the user wants a deep cross-model review of a branch or PR before merge, or asks to review this branch with multiple tools or models. Encodes known infra failure modes and their fixes (missing Claude ACP adapter, Codex MCP auth hangs, false-positive report files, long jobs orphaned inside subagents). Do not use for reviewing a single uncommitted snippet, for non-git work, for running only one reviewer, or when the user only wants a quick lint or test run.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fmulti-tool-branch-review\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M753XQM40XCK55BH5WPA88EW","create-pr-with-template","Create a GitHub Pull Request with gh CLI and prefer repository PR templates automatically. Use this whenever the user asks to open\u002Fcreate a PR, especially when template compliance is needed. If multiple templates exist, ask the user which template to use.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fcreate-pr-with-template\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":19},"01M753XJMBJ8VFPRCDCC1JJ9G4","ui-craft","Provides guardrails for user-facing UI work: usability heuristics, accessibility floors, design-system discipline, component states, microcopy, motion, dark mode, responsive behavior, and human-AI UX. Use when designing, generating, reviewing, or refactoring visible product surfaces such as components, pages, dashboards, forms, dialogs, loading\u002Fempty\u002Ferror states, or AI interfaces. Do not use for backend-only work, infrastructure, CLI\u002FTUI design, or pure documentation editing.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fui-craft\u002FSKILL.md",[],[]]