[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JMMRN6PADHTDDPAPTN4MQN":3,"skill-same:01M6JMMRN6PADHTDDPAPTN4MQN":96},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6JMMRN6PADHTDDPAPTN4MQN","azure_kubernetes",null,"Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS environment, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS.","LongLeo287\u002FOmniClaw","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M6JK75GQ78TSP1ZPXNKK3MCH",9,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fazure_kubernetes\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"kubernetes","azure kubernetes","azure","production-ready","design","autoscaling","upgrade","options","selection","ready","choose","configure","plan","api","analysis","aks","server","create","secure","security","2026-11-10 10:12:30",false,"---\nname: azure_kubernetes\n\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"1.0.2\"\ndescription: \"Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS environment, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS.\"\n---\n\n# Azure Kubernetes Service\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This skill produces a **recommended AKS cluster configuration** based on user requirements, distinguishing **Day-0 decisions** (networking, API server — hard to change later) from **Day-1 features** (can enable post-creation). See [CLI reference](.\u002Freferences\u002Fcli-reference.md) for commands.\n\n## Quick Reference\n| Property | Value |\n|----------|-------|\n| Best for | AKS cluster planning and Day-0 decisions |\n| MCP Tools | `mcp_azure_mcp_aks` |\n| CLI | `az aks create`, `az aks show`, `kubectl get`, `kubectl describe` |\n| Related skills | azure-diagnostics (troubleshooting AKS), azure-validate (readiness checks) |\n\n## When to Use This Skill\nActivate this skill when user wants to:\n- Create a new AKS cluster\n- Plan AKS cluster configuration for production workloads\n- Design AKS networking (API server access, pod IP model, egress)\n- Set up AKS identity and secrets management\n- Configure AKS governance (Azure Policy, Deployment Safeguards)\n- Enable AKS observability (Container Insights, Managed Prometheus, Grafana)\n- Define AKS upgrade and patching strategy\n- Enable AKS cost visibility and analysis\n- Understand AKS Automatic vs Standard SKU differences\n- Get a Day-0 checklist for AKS cluster setup and configuration\n\n## Rules\n1. Start with the user's requirements for provisioning compute, networking, security, and other settings.\n2. Use the `azure` MCP server and select `mcp_azure_mcp_aks` first to discover the exact AKS-specific MCP tools surfaced by the client. Choose the smallest discovered AKS tool that fits the task, and fall back to Azure CLI (`az aks`) only when the needed functionality is not exposed through the AKS MCP surface.\n3. Determine if AKS Automatic or Standard SKU is more appropriate based on the user's need for control vs convenience. Default to AKS Automatic unless specific customizations are required.\n4. Document decisions and rationale for cluster configuration choices, especially for Day-0 decisions that are hard to change later (networking, API server access).\n\n\n## Required Inputs (Ask only what’s needed)\nIf the user is unsure, use safe defaults.\n- AKS environment type: dev\u002Ftest or production\n- Region(s), availability zones, preferred node VM sizes\n- Expected scale (node\u002Fcluster count, workload size)\n- Networking requirements (API server access, pod IP model, ingress\u002Fegress control)\n- Security and identity requirements, including image registry\n- Upgrade and observability preferences\n- Cost constraints\n\n## Workflow\n\n### 1. Cluster Type\n- **AKS Automatic** (default): Best for most production workloads, provides a curated experience with pre-configured best practices for security, reliability, and performance. Use unless you have specific custom requirements for networking, autoscaling, or node pool configurations not supported by Node Auto-Provisioning (NAP).\n- **AKS Standard**: Use if you need full control over environment configuration, which requires additional overhead to set up and manage.\n\n### 2. Networking (Pod IP, Egress, Ingress, Dataplane)\n\n**Pod IP Model** (Key Day-0 decision):\n- **Azure CNI Overlay** (recommended): pod IPs from private overlay range, not VNet-routable, scales to large environments and good for most workloads\n- **Azure CNI (VNet-routable)**: pod IPs directly from VNet (pod subnet or node subnet), use when pods must be directly addressable from VNet or on-prem\n  - Docs: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Faks\u002Fazure-cni-overlay\n\n**Dataplane & Network Policy**:\n- **Azure CNI powered by Cilium** (recommended): eBPF-based for high-performance packet processing, network policies, and observability\n\n**Egress**:\n- **Static Egress Gateway** for stable, predictable outbound IPs\n- For restricted egress: UDR + Azure Firewall or NVA\n\n**Ingress**:\n- **App Routing addon with Gateway API** — recommended default for HTTP\u002FHTTPS workloads\n- **Istio service mesh with Gateway API** - for advanced traffic management, mTLS, canary releases\n- **Application Gateway for Containers** — for L7 load balancing with WAF integration\n\n**DNS**:\n- Enable **LocalDNS** on all node pools for reliable, performant DNS resolution\n\n### 3. Security\n- Use **Microsoft Entra ID** everywhere (control plane, Workload Identity for pods, node access). Avoid static credentials.\n- Azure Key Vault via **Secrets Store CSI Driver** for secrets\n- Enable **Azure Policy** + **Deployment Safeguards**\n- Enable **Encryption at rest** for etcd\u002FAPI server; **in-transit** for node-to-node\n- Allow only signed, policy-approved images (Azure Policy + Ratify), prefer **Azure Container Registry**\n- **Isolation**: Use namespaces, network policies, scoped logging\n\n### 4. Observability\n- Use Managed Prometheus and Container Insights with Grafana for AKS observability (logs + metrics).\n- Enable Diagnostic Settings to collect control plane logs and audit logs in a Log Analytics workspace for security monitoring and troubleshooting.\n- For other monitoring and troubleshooting tools, use features like the Agentic CLI for AKS, Application Insights, Resource Health Center, AppLens detectors, and Azure Advisors.\n\n### 5. Upgrades & Patching\n- Configure **Maintenance Windows** for controlled upgrade timing\n- Enable **auto-upgrades** for control plane and node OS to stay up-to-date with security patches and Kubernetes versions\n- Consider **LTS versions** for enterprise stability (2-year support) by upgrading your AKS environment to the Premium tier\n- **Fleet upgrades**: Use **AKS Fleet Manager** for staged rollout across test to production environments\n\n### 6. Performance\n- Use **Ephemeral OS disks** (`--node-osdisk-type Ephemeral`) for faster node startup\n- Select **Azure Linux** as node OS (smaller footprint, faster boot)\n- Enable **KEDA** for event-driven autoscaling beyond HPA\n\n### 7. Node Pools & Compute\n- **Dedicated system node pool**: At least 2 nodes, tainted for system workloads only (`CriticalAddonsOnly`)\n- Enable **Node Auto Provisioning (NAP)** on all pools for cost savings and responsive scaling\n- Use **latest generation SKUs (v5\u002Fv6)** for host-level optimizations\n- **Avoid B-series VMs** — burstable SKUs cause performance\u002Freliability issues\n- Use SKUs with **at least 4 vCPUs** for production workloads\n- Set **topology spread constraints** to distribute pods across hosts\u002Fzones per SLO\n\n### 8. Reliability\n- Deploy across **3 Availability Zones** (`--zones 1 2 3`)\n- Use **Standard tier** for zone-redundant control plane + 99.95% SLA for API server availability\n- Enable **Microsoft Defender for Containers** for runtime protection\n- Configure **PodDisruptionBudgets** for all production workloads\n- Use **topology spread constraints** to ensure pod distribution across failure domains\n\n### 9. Cost Controls\n- Use **Spot node pools** for batch\u002Finterruptible workloads (up to 90% savings)\n- **Stop\u002FStart** dev\u002Ftest clusters: `az aks stop\u002Fstart`\n- Consider **Reserved Instances** or **Savings Plans** for steady-state workloads\n\n## Guardrails \u002F Safety\n- Do not request or output secrets (tokens, keys).\n- If requirements are ambiguous for day-0 critical decisions, ask the user clarifying questions. For day-1 enabled features, propose 2–3 safe options with tradeoffs and choose a conservative default.\n- Do not promise zero downtime; advise workload safeguards (PDBs, probes, replicas) and staged upgrades along with best practices for reliability and performance.\n\n## MCP Tools\n| Tool | Purpose | Key Parameters |\n|------|---------|----------------|\n| `mcp_azure_mcp_aks` | AKS MCP entry point used to discover the exact AKS-specific tools exposed by the client | Discover the callable AKS tool first, then use that tool's parameters |\n\n## Error Handling\n| Error \u002F Symptom | Likely Cause | Remediation |\n|-----------------|--------------|-------------|\n| MCP tool call fails or times out | Invalid credentials, subscription, or AKS context | Verify `az login`, confirm the active subscription context with `az account show`, and check the target resource group without echoing subscription identifiers back to the user |\n| Quota exceeded | Regional vCPU or resource limits | Request quota increase or select different region\u002FVM SKU |\n| Networking conflict (IP exhaustion) | Pod subnet too small for overlay\u002FCNI | Re-plan IP ranges; may require cluster recreation (Day-0) |\n| Workload Identity not working | Missing OIDC issuer or federated credential | Enable `--enable-oidc-issuer --enable-workload-identity`, configure federated identity |\n","# Azure Kubernetes Service\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This skill produces a **recommended AKS cluster configuration** based on user requirements, distinguishing **Day-0 decisions** (networking, API server — hard to change later) from **Day-1 features** (can enable post-creation). See [CLI reference](.\u002Freferences\u002Fcli-reference.md) for commands.\n\n## Quick Reference\n| Property | Value |\n|----------|-------|\n| Best for | AKS cluster planning and Day-0 decisions |\n| MCP Tools | `mcp_azure_mcp_aks` |\n| CLI | `az aks create`, `az aks show`, `kubectl get`, `kubectl describe` |\n| Related skills | azure-diagnostics (troubleshooting AKS), azure-validate (readiness checks) |\n\n## When to Use This Skill\nActivate this skill when user wants to:\n- Create a new AKS cluster\n- Plan AKS cluster configuration for production workloads\n- Design AKS networking (API server access, pod IP model, egress)\n- Set up AKS identity and secrets management\n- Configure AKS governance (Azure Policy, Deployment Safeguards)\n- Enable AKS observability (Container Insights, Managed Prometheus, Grafana)\n- Define AKS upgrade and patching strategy\n- Enable AKS cost visibility and analysis\n- Understand AKS Automatic vs Standard SKU differences\n- Get a Day-0 checklist for AKS cluster setup and configuration\n\n## Rules\n1. Start with the user's requirements for provisioning compute, networking, security, and other settings.\n2. Use the `azure` MCP server and select `mcp_azure_mcp_aks` first to discover the exact AKS-specific MCP tools surfaced by the client. Choose the smallest discovered AKS tool that fits the task, and fall back to Azure CLI (`az aks`) only when the needed functionality is not exposed through the AKS MCP surface.\n3. Determine if AKS Automatic or Standard SKU is more appropriate based on the user's need for control vs convenience. Default to AKS Automatic unless specific customizations are required.\n4. Document decisions and rationale for cluster configuration choices, especially for Day-0 decisions that are hard to change later (networking, API server access).\n\n\n## Required Inputs (Ask only what’s needed)\nIf the user is unsure, use safe defaults.\n- AKS environment type: dev\u002Ftest or production\n- Region(s), availability zones, preferred node VM sizes\n- Expected scale (node\u002Fcluster count, workload size)\n- Networking requirements (API server access, pod IP model, ingress\u002Fegress control)\n- Security and identity requirements, including image registry\n- Upgrade and observability preferences\n- Cost constraints\n\n## Workflow\n\n### 1. Cluster Type\n- **AKS Automatic** (default): Best for most production workloads, provides a curated experience with pre-configured best practices for security, reliability, and performance. Use unless you have specific custom requirements for networking, autoscaling, or node pool configurations not supported by Node Auto-Provisioning (NAP).\n- **AKS Standard**: Use if you need full control over environment configuration, which requires additional overhead to set up and manage.\n\n### 2. Networking (Pod IP, Egress, Ingress, Dataplane)\n\n**Pod IP Model** (Key Day-0 decision):\n- **Azure CNI Overlay** (recommended): pod IPs from private overlay range, not VNet-routable, scales to large environments and good for most workloads\n- **Azure CNI (VNet-routable)**: pod IPs directly from VNet (pod subnet or node subnet), use when pods must be directly addressable from VNet or on-prem\n  - Docs: https:\u002F\u002Flearn.microsoft.com\u002Fazure\u002Faks\u002Fazure-cni-overlay\n\n**Dataplane & Network Policy**:\n- **Azure CNI powered by Cilium** (recommended): eBPF-based for high-performance packet processing, network policies, and observability\n\n**Egress**:\n- **Static Egress Gateway** for stable, predictable outbound IPs\n- For restricted egress: UDR + Azure Firewall or NVA\n\n**Ingress**:\n- **App Routing addon with Gateway API** — recommended default for HTTP\u002FHTTPS workloads\n- **Istio service mesh with Gateway API** - for advanced traffic management, mTLS, canary releases\n- **Application Gateway for Containers** — for L7 load balancing with WAF integration\n\n**DNS**:\n- Enable **LocalDNS** on all node pools for reliable, performant DNS resolution\n\n### 3. Security\n- Use **Microsoft Entra ID** everywhere (control plane, Workload Identity for pods, node access). Avoid static credentials.\n- Azure Key Vault via **Secrets Store CSI Driver** for secrets\n- Enable **Azure Policy** + **Deployment Safeguards**\n- Enable **Encryption at rest** for etcd\u002FAPI server; **in-transit** for node-to-node\n- Allow only signed, policy-approved images (Azure Policy + Ratify), prefer **Azure Container Registry**\n- **Isolation**: Use namespaces, network policies, scoped logging\n\n### 4. Observability\n- Use Managed Prometheus and Container Insights with Grafana for AKS observability (logs + metrics).\n- Enable Diagnostic Settings to collect control plane logs and audit logs in a Log Analytics workspace for security monitoring and troubleshooting.\n- For other monitoring and troubleshooting tools, use features like the Agentic CLI for AKS, Application Insights, Resource Health Center, AppLens detectors, and Azure Advisors.\n\n### 5. Upgrades & Patching\n- Configure **Maintenance Windows** for controlled upgrade timing\n- Enable **auto-upgrades** for control plane and node OS to stay up-to-date with security patches and Kubernetes versions\n- Consider **LTS versions** for enterprise stability (2-year support) by upgrading your AKS environment to the Premium tier\n- **Fleet upgrades**: Use **AKS Fleet Manager** for staged rollout across test to production environments\n\n### 6. Performance\n- Use **Ephemeral OS disks** (`--node-osdisk-type Ephemeral`) for faster node startup\n- Select **Azure Linux** as node OS (smaller footprint, faster boot)\n- Enable **KEDA** for event-driven autoscaling beyond HPA\n\n### 7. Node Pools & Compute\n- **Dedicated system node pool**: At least 2 nodes, tainted for system workloads only (`CriticalAddonsOnly`)\n- Enable **Node Auto Provisioning (NAP)** on all pools for cost savings and responsive scaling\n- Use **latest generation SKUs (v5\u002Fv6)** for host-level optimizations\n- **Avoid B-series VMs** — burstable SKUs cause performance\u002Freliability issues\n- Use SKUs with **at least 4 vCPUs** for production workloads\n- Set **topology spread constraints** to distribute pods across hosts\u002Fzones per SLO\n\n### 8. Reliability\n- Deploy across **3 Availability Zones** (`--zones 1 2 3`)\n- Use **Standard tier** for zone-redundant control plane + 99.95% SLA for API server availability\n- Enable **Microsoft Defender for Containers** for runtime protection\n- Configure **PodDisruptionBudgets** for all production workloads\n- Use **topology spread constraints** to ensure pod distribution across failure domains\n\n### 9. Cost Controls\n- Use **Spot node pools** for batch\u002Finterruptible workloads (up to 90% savings)\n- **Stop\u002FStart** dev\u002Ftest clusters: `az aks stop\u002Fstart`\n- Consider **Reserved Instances** or **Savings Plans** for steady-state workloads\n\n## Guardrails \u002F Safety\n- Do not request or output secrets (tokens, keys).\n- If requirements are ambiguous for day-0 critical decisions, ask the user clarifying questions. For day-1 enabled features, propose 2–3 safe options with tradeoffs and choose a conservative default.\n- Do not promise zero downtime; advise workload safeguards (PDBs, probes, replicas) and staged upgrades along with best practices for reliability and performance.\n\n## MCP Tools\n| Tool | Purpose | Key Parameters |\n|------|---------|----------------|\n| `mcp_azure_mcp_aks` | AKS MCP entry point used to discover the exact AKS-specific tools exposed by the client | Discover the callable AKS tool first, then use that tool's parameters |\n\n## Error Handling\n| Error \u002F Symptom | Likely Cause | Remediation |\n|-----------------|--------------|-------------|\n| MCP tool call fails or times out | Invalid credentials, subscription, or AKS context | Verify `az login`, confirm the active subscription context with `az account show`, and check the target resource group without echoing subscription identifiers back to the user |\n| Quota exceeded | Regional vCPU or resource limits | Request quota increase or select different region\u002FVM SKU |\n| Networking conflict (IP exhaustion) | Pod subnet too small for overlay\u002FCNI | Re-plan IP ranges; may require cluster recreation (Day-0) |\n| Workload Identity not working | Missing OIDC issuer or federated credential | Enable `--enable-oidc-issuer --enable-workload-identity`, configure federated identity |\n",{"name":5,"license":15,"metadata":52,"description":7},{"author":53,"version":54},"Microsoft","1.0.2","main","c173cdffe08e788a99b91928a831b476b8434838","ecosystem\u002Fskills\u002Fazure_kubernetes",0,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw","https:\u002F\u002Fportfolio-longleo.vercel.app\u002Flabs\u002Fomniclaw.html","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-09-30 00:58:05",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add LongLeo287\u002FOmniClaw --skill azure_kubernetes",{"tool":70,"command":71},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill azure_kubernetes",{"tool":73,"command":74},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill azure_kubernetes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fazure_kubernetes\u002FSKILL.md",true,[78,84,88,92],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"_DIR_IDENTITY.md","REFERENCE","参考文档",154,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fazure_kubernetes\u002F_DIR_IDENTITY.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"README.md",467,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fazure_kubernetes\u002FREADME.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcli_reference.md",1188,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fazure_kubernetes\u002Freferences\u002Fcli_reference.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"schema.json",450,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fazure_kubernetes\u002Fschema.json",[97,134,156,183,199,226],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":115,"publishedAt":47},"01M6JR0KQP4MHT32TN40D9CBFX","UI-UX Pro Max","Advanced UI\u002FUX analysis and generation skills with data-driven patterns. Python scripts (core.py, search.py) for systematic UI pattern extraction, design system generation, and component search from curated data sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fui_ux_pro_max\u002FSKILL.md",[103,106,107,112],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":113,"categoryName":114,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000033","数据分析师",[116,117,118,119,120,121,31,122,123,41,124,125,126,127,128,129,130,131,132,133],"ux","ui","ui ux pro max","max","pro","ui ux","component","search","team","rd","ui-ux","active","systematic","scripts","pattern extraction","sources","advanced","data-driven",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":47},"01M6JR0EF5AEQHP2FSTB57H05P","shadcn-ui","Expert guidance for integrating and building applications with shadcn\u002Fui components, including component discovery, installation, customization, and best practices.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fshadcn_ui\u002FSKILL.md",[140],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},[142,117,143,144,122,145,146,147,148,124,149,150,151,127,152,153,154,155],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","with","for",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":165,"publishedAt":47},"01M6JR08F51BEN17RHFYX65WVE","zustand_store_ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand_store_ts\u002FSKILL.md",[162],{"categoryNo":163,"categoryName":164,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[166,167,168,169,170,171,44,172,173,174,175,176,177,178,179,180,154,181,182],"zustand store ts","zustand","store","typescript","microsoft","react","state management","state","react state management","management","global","use","patterns","separation","middleware","action","implementing",{"skillNo":184,"name":167,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":47},"01M6JR00TDMVAFFCZXZ04AN7Q7","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand\u002FSKILL.md",[],[167,189,172,190,173,191,192,175,193,177,194,195,196,168,154,197,198,181,182],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":209,"publishedAt":47},"01M6JQZSWV4KWJP112G6XHEP44","youtube_summarizer","Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_summarizer\u002FSKILL.md",[205,208],{"categoryNo":206,"categoryName":207,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":232,"publishedAt":47},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[210,233,234,216,235,236,237,238,239,240,241,242,243,244,245,246,247],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","read","write","clip","总结","工具","文案","sonnet"]